This is the mail archive of the
gcc@gcc.gnu.org
mailing list for the GCC project.
Cross compiling libstc++-v3 fails
- From: "Leif Ekblad" <leif at rdos dot net>
- To: <gcc at gcc dot gnu dot org>
- Date: Wed, 11 Jan 2006 12:10:32 +0100
- Subject: Cross compiling libstc++-v3 fails
- References: <20051229083827.56B6384025@ws1-5.us4.outblaze.com> <69F191C3-9B76-4FBB-A8BE-EE0CF8F09A09@apple.com> <046001c60cb0$5fdf87a0$0201a8c0@LEIFACER> <40FF9C62-30CD-4703-80EF-2453A415A454@apple.com> <04a701c60cbb$12b99e10$0201a8c0@LEIFACER> <13AB625C-8D2E-496A-B88C-C13B767B3BBD@apple.com>
- Reply-to: leif at rdos dot net
In configure script, line 2580, there is a link test which checks if
an executable can be generated. The config.log file emits the
following errors:
/usr/local/bin/rdos-ld: unrecognised emulation mode: -o
Supported emulations: elf_i386
collect2: ld returned status 1 exit status.
This error later in the configure scripts leads to an abort
with "Link tests are not allowed after GCC_NO_EXECUTABLES".
To try to figure out this problem, I manully compiled the same
file with the same options using the same compiler (xgcc), and
it returns the same error. I then tried to use the cross-compiler
built using gcc-4.1-20051008, with which I can build other
executables, and it returns the same error. Only if I remove
the "-B/usr/src/toolchain/gcc-4.2-20060107/host-i686-pc-linux-gnu/gcc"
option, does it generate the executable without any errors. How
can this include give ld the wrong emulation mode? Apparently,
there is no "-o" in any file in the build-directory.
Is this a known problem?
Leif Ekblad