From: Simon Marchi <simon.marchi@polymtl.ca>
To: Bill Morgan <arthurwilliammorgan@gmail.com>
Cc: gdb@sourceware.org
Subject: Re: elf-attrs.c compliation errors
Date: Wed, 01 Aug 2018 12:45:00 -0000 [thread overview]
Message-ID: <34635b11cf35c120572f8452ff415e05@polymtl.ca> (raw)
In-Reply-To: <CAM4wpo8p6ah9dNgJ1+U_qAZ12Hy5C5J5jN4H6Nn5UjesPFTfjw@mail.gmail.com>
On 2018-07-31 20:44, Bill Morgan wrote:
> Hello,
>
> I'm building this commit: 33633d9f5b138a211405d482436db2f7661b190e
>
> With this configuration:
>
> ./configure \
> --build=x86_64-w64-mingw64 \
> --host=x86_64-w64-mingw64 \
> --target=arm-none-eabi \
> --with-python \
> --without-tcl \
> --without-tk \
> --without-guile \
> --with-expat \
> --with-lzma \
> --with-system-readline \
> --with-zlib \
> --enable-tui
>
> I am getting the compilation errors below:
>
[snip]
I also get this error when trying to build on Windows. I installed
mingw-w64 using the installer found here:
http://mingw-w64.org/doku.php/download/mingw-builds
I just noticed that the host gets auto-detected as "x86_64-pc-mingw64"
(same as you specified explicitly). I see that when building on mingw,
-Wno-format should be added, specifically ignoring these warnings:
https://sourceware.org/git/gitweb.cgi?p=binutils-gdb.git;a=blob;f=bfd/warning.m4;h=5a7f92d61622c6a0934aa950f8aaa6bf55677d43;hb=HEAD#l75
However, it's only done when the host string contains "mingw32", not
"mingw64". Maybe this needs to be adjusted to "*-*-mingw*"? If you
grep, you'll find a bunch of other things conditionally done if the
triplet is "*-*-mingw32*", maybe they need to be adjusted too?
Simon
next prev parent reply other threads:[~2018-08-01 12:45 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-08-01 0:44 Bill Morgan
2018-08-01 12:45 ` Simon Marchi [this message]
2018-08-01 14:24 ` Bill Morgan
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=34635b11cf35c120572f8452ff415e05@polymtl.ca \
--to=simon.marchi@polymtl.ca \
--cc=arthurwilliammorgan@gmail.com \
--cc=gdb@sourceware.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox