This is the mail archive of the
gcc-bugs@gcc.gnu.org
mailing list for the GCC project.
[Bug libstdc++/35679] Cannot build cross compiler for i686-pc-linux-gnu: configure: error: Link tests are not allowed after GCC_NO_EXECUTABLES
- From: "brian at dessent dot net" <gcc-bugzilla at gcc dot gnu dot org>
- To: gcc-bugs at gcc dot gnu dot org
- Date: 24 Mar 2008 19:54:25 -0000
- Subject: [Bug libstdc++/35679] Cannot build cross compiler for i686-pc-linux-gnu: configure: error: Link tests are not allowed after GCC_NO_EXECUTABLES
- References: <bug-35679-13942@http.gcc.gnu.org/bugzilla/>
- Reply-to: gcc-bugzilla at gcc dot gnu dot org
------- Comment #1 from brian at dessent dot net 2008-03-24 19:54 -------
Subject: Re: New: Cannot build cross compiler for
i686-pc-linux-gnu: configure: error: Link tests are not allowed after
GCC_NO_EXECUTABLES
yakov at emc dot com wrote:
> --target=i686-emc-elf --enable-languages=c++ --disable-multilib --with-gnu-as
Your title for this bug is misleading as it seems you're building a
cross for a newlib bare metal target, not i686-pc-linux-gnu. That's
just the host, and is irrelevant to the issue.
There is currently a known problem with the libstdc++ configury and bare
metal newlib targets. You can fix it either by providing BSP files
(crt*.o, linker script, etc) for your board so that test programs can be
linked, or you can disable the AC_LIBTOOL_DLOPEN check in
libstc++-v3/configure.ac for newlib targets, as in
<http://gcc.gnu.org/ml/gcc/2007-11/msg00790.html>. For a summary of the
history of this issue:
<http://gcc.gnu.org/ml/gcc/2008-03/msg00515.html>.
--
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=35679