From: Jonathan Yong <10walls@gmail.com>
To: gcc-help@gcc.gnu.org
Subject: Re: Failed to compile gcc cross toolchain.
Date: Mon, 2 Aug 2021 06:16:07 +0000 [thread overview]
Message-ID: <7269d8dc-4f9c-ff0f-e86c-934217f47b1f@gmail.com> (raw)
In-Reply-To: <21dc227d.2029.17b04d5ecc4.Coremail.bootmgr@163.com>
On 8/2/21 3:08 AM, bootmgr--- via Gcc-help wrote:
> I'm failed to compile libstdc++.
> Configured by ../gcc-11.2.0/configure --disable-multilib --disable-nls --enable-graphite --enable-languages=c,c++,lto --enable-mingw-wildcard --enable-threads=mcf --enable-version-specific-runtime-libs --disable-libstdcxx-pch --enable-fully-dynamic-string --enable-large-address-aware --enable-vtable-verify --target=x86_64-w64-mingw32 --with-sysroot=/usr/local
> Build: x86_64-linux-gnu Target:x86_64-w64-mingw32 Host: x86_64-linux-gnu
>
>
> Error Messages:
> libtool: compile: /home/abc/build-gcc/./gcc/xgcc -shared-libgcc -B/home/abc/build-gcc/./gcc -nostdinc++ -L/home/abc/build-gcc/x86_64-w64-mingw32/libstdc++-v3/src -L/home/abc/build-gcc/x86_64-w64-mingw32/libstdc++-v3/src/.libs -L/home/abc/build-gcc/x86_64-w64-mingw32/libstdc++-v3/libsupc++/.libs -L/usr/local/x86_64-w64-mingw32/lib -L/usr/local/mingw/lib -isystem /usr/local/x86_64-w64-mingw32/include -isystem /usr/local/mingw/include -B/usr/local/x86_64-w64-mingw32/bin/ -B/usr/local/x86_64-w64-mingw32/lib/ -isystem /usr/local/x86_64-w64-mingw32/include -isystem /usr/local/x86_64-w64-mingw32/sys-include -I/home/abc/gcc-11.2.0/libstdc++-v3/../libgcc -I/home/abc/build-gcc/x86_64-w64-mingw32/libstdc++-v3/include/x86_64-w64-mingw32 -I/home/abc/build-gcc/x86_64-w64-mingw32/libstdc++-v3/include -I/home/abc/gcc-11.2.0/libstdc++-v3/libsupc++ -O3 -DNDEBUG -march=native -fno-ident -ffunction-sections -fdata-sections -O3 -DNDEBUG -march=native -fno-ident -ffunction-sections -fdata-sections -D_GLIBCXX_SHARED -fno-implicit-templates -Wall -Wextra -Wwrite-strings -Wcast-qual -Wabi=2 -fdiagnostics-show-location=once -ffunction-sections -fdata-sections -frandom-seed=atexit_thread.lo -O3 -DNDEBUG -march=native -fno-ident -ffunction-sections -fdata-sections -c ../../../../gcc-11.2.0/libstdc++-v3/libsupc++/atexit_thread.cc -o atexit_thread.o
> ../../../../gcc-11.2.0/libstdc++-v3/libsupc++/atexit_thread.cc:25:10: fatal error: cstdlib: No such file or directory
> 25 | #include <cstdlib>
> | ^~~~~~~~~
> compilation terminated.
> make[4]: *** [Makefile:769: atexit_thread.lo] Error 1
> make[4]: Leaving directory '/home/abc/build-gcc/x86_64-w64-mingw32/libstdc++-v3/libsupc++'
> make[3]: *** [Makefile:568: all-recursive] Error 1
> make[3]: Leaving directory '/home/abc/build-gcc/x86_64-w64-mingw32/libstdc++-v3'
> make[2]: *** [Makefile:493: all] Error 2
> make[2]: Leaving directory '/home/abc/build-gcc/x86_64-w64-mingw32/libstdc++-v3'
> make[1]: *** [Makefile:13388: all-target-libstdc++-v3] Error 2
> make[1]: Leaving directory '/home/abc/build-gcc'
> make: *** [Makefile:967: all] Error 2
>
I just tested against the latest 11.2.0 from git, works fine for me. mcf
threads is not in git, so I suggest contacting whoever you got the
source code from for help.
next prev parent reply other threads:[~2021-08-02 6:15 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-08-02 3:08 bootmgr
2021-08-02 6:16 ` Jonathan Yong [this message]
2021-08-02 14:19 ` LIU Hao
2021-08-03 4:50 ` bootmgr
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=7269d8dc-4f9c-ff0f-e86c-934217f47b1f@gmail.com \
--to=10walls@gmail.com \
--cc=gcc-help@gcc.gnu.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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).