From: Richard Earnshaw <Richard.Earnshaw@foss.arm.com>
To: William Gregorio <wmg665@gmail.com>, gcc-help@gcc.gnu.org
Subject: Re: GCC cross-compiler errors
Date: Mon, 28 Sep 2020 17:46:17 +0100 [thread overview]
Message-ID: <a1c5d37e-ab38-6beb-d9ae-33b6f38857d5@foss.arm.com> (raw)
In-Reply-To: <CACuxKPQLi7hLciYGbCzmwev8+bkvFRmTKA2=vEdcbhRR=KhDng@mail.gmail.com>
On 25/09/2020 14:12, William Gregorio via Gcc-help wrote:
> Hi,
>
> I'm trying to build a gcc cross-compiler from source, and whenever I invoke
> make it results in an error. I'd appreciate any help! Feel free to request
> any more details needed.
>
> Ubuntu 18.04.3 LTS
> gcc-7.5.0
> autoconf-2.69
>
>
> ./configure options
> --target=arm-none-eabi
> --prefix=/usr/bin/crossbuild
> --without-headers
> --enable-multilib
> --with-multilib=armv7e-m
> --with-gnu-as
> --with-gnu-ld
> --with-dwarf2
> --with-newlib
> --with-system-zlib
> --without-libffi
> --disable-decimal-float
> --disable-nls
> --enable-languages="c,c++"
> --enable-interwork
> --disable-libstdcxx-pch
> --with-newlib
>
>
> make all
> configure: WARNING: No native atomic operations are provided for this platform.
> configure: WARNING: They cannot be faked when thread support is disabled.
> configure: WARNING: Thread-safety of certain classes is not guaranteed.
> .
> .
> .
> 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
> Makefile:10307: recipe for target 'configure-target-libstdc++-v3' failed
> make[1]: *** [configure-target-libstdc++-v3] Error 1
> make[1]: Leaving directory '/home/metaw1ll/crossbuild/tivac/gcc'
> Makefile:889: recipe for target 'all' failed
> make: *** [all] Error 2
>
Use a separate build area from your sources. Building inside the source
tree is not supported.
R.
next prev parent reply other threads:[~2020-09-28 16:46 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-09-25 13:12 William Gregorio
2020-09-28 16:46 ` Richard Earnshaw [this message]
2020-09-29 7:04 ` Kai Ruottu
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=a1c5d37e-ab38-6beb-d9ae-33b6f38857d5@foss.arm.com \
--to=richard.earnshaw@foss.arm.com \
--cc=gcc-help@gcc.gnu.org \
--cc=wmg665@gmail.com \
/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).