From: Jonathan Wakely <jwakely.gcc@gmail.com>
To: Thomas Sobczynski <tsobczynski@werfen.com>
Cc: Xi Ruoyao <xry111@mengyan1223.wang>,
"gcc-help@gcc.gnu.org" <gcc-help@gcc.gnu.org>
Subject: Re: [EXTERNAL] Re: Compiling GCC 11 for Windows targeting ARM on Linux
Date: Wed, 12 Jan 2022 19:09:25 +0000 [thread overview]
Message-ID: <CAH6eHdTDoZU1ubRz7UesbBr6Acg9rdFjvXszMAmUB-K6AKFi0Q@mail.gmail.com> (raw)
In-Reply-To: <VI1PR0402MB38530909A3F09C7AFB77D413CD529@VI1PR0402MB3853.eurprd04.prod.outlook.com>
On Wed, 12 Jan 2022 at 18:39, Thomas Sobczynski <tsobczynski@werfen.com> wrote:
>
> Thanks much for the pointers thus far. I am now trying to take this in three chunks: build native GCC11 on GNU/Linux, then use that to build GCC11 on/for GNU/Linux targeting ARM, then use the previous two to build GCC11 on GNU/Linux for Windows targeting ARM.
>
> The first step completes, so I have an installed GCC 11 native toolchain for Linux.
>
> The second step doesn't finish; getting hung up on configuring libstdc++.
>
> The tail of the build output leading up to the error:
>
>
>
> checking for ISO C99 support to TR1 in <stdint.h>... no
> checking for ISO C99 support to TR1 in <math.h>... no
> no
> no
> checking stdbool.h usability... no
> checking stdbool.h presence... yes
> configure: WARNING: stdbool.h: present but cannot be compiled
> configure: WARNING: stdbool.h: check for missing prerequisite headers?
> configure: WARNING: stdbool.h: see the Autoconf documentation
> configure: WARNING: stdbool.h: section "Present But Cannot Be Compiled"
> configure: WARNING: stdbool.h: proceeding with the compiler's result
> checking for stdbool.h... no
> checking stdalign.h usability... no
> checking stdalign.h presence... yes
> configure: WARNING: stdalign.h: present but cannot be compiled
> configure: WARNING: stdalign.h: check for missing prerequisite headers?
> configure: WARNING: stdalign.h: see the Autoconf documentation
> configure: WARNING: stdalign.h: section "Present But Cannot Be Compiled"
> configure: WARNING: stdalign.h: proceeding with the compiler's result
> checking for stdalign.h... no
> checking for the value of EOF... configure: error: computing EOF failed
> make[2]: *** [Makefile:13316: configure-target-libstdc++-v3] Error 1
> make[2]: Leaving directory '/home/tsobczynski/Compiler/build-linux-cross'
> make[1]: *** [Makefile:968: all] Error 2
> make[1]: Leaving directory '/home/tsobczynski/Compiler/build-linux-cross'
This is fixed by the patch for PR 103866 that I already referred you
to. Either build the Git master branch, or backport the fix to gcc-11.
But I'm repeating myself now.
next prev parent reply other threads:[~2022-01-12 19:09 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-01-10 16:47 Thomas Sobczynski
2022-01-10 17:16 ` Xi Ruoyao
2022-01-11 2:49 ` [EXTERNAL] " Thomas Sobczynski
2022-01-11 3:44 ` Thomas Sobczynski
2022-01-11 6:53 ` Xi Ruoyao
2022-01-11 11:19 ` Jonathan Wakely
2022-01-11 11:14 ` Jonathan Wakely
2022-01-12 18:39 ` Thomas Sobczynski
2022-01-12 19:09 ` Jonathan Wakely [this message]
2022-01-11 11:09 ` Jonathan Wakely
2022-01-10 17:24 ` Jonathan Wakely
2022-01-11 0:27 ` [EXTERNAL] " Thomas Sobczynski
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=CAH6eHdTDoZU1ubRz7UesbBr6Acg9rdFjvXszMAmUB-K6AKFi0Q@mail.gmail.com \
--to=jwakely.gcc@gmail.com \
--cc=gcc-help@gcc.gnu.org \
--cc=tsobczynski@werfen.com \
--cc=xry111@mengyan1223.wang \
/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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).