This is the mail archive of the
gcc-help@gcc.gnu.org
mailing list for the GCC project.
Re: Cross-build for x86_64-pc-mingw32
- From: FX Coudert <fxcoudert at gmail dot com>
- To: gcc-help at gcc dot gnu dot org
- Cc: mingw-w64-public at lists dot sourceforge dot net
- Date: Sat, 1 Dec 2007 18:38:49 +0000
- Subject: Re: Cross-build for x86_64-pc-mingw32
- References: <19c433eb0711300950r43f1ccffi28ef6b7a2e51548d@mail.gmail.com> <b609cb3b0711301053g178ed7c7pb7f225f3579a4591@mail.gmail.com> <15BB3B75-14C5-4E4E-8C44-EBD567E70A79@gmail.com> <47519B7A.C4E7AC23@dessent.net>
That error means that something went wrong earlier. Look upwards at
config.log and you will see somewhere that it tried to do a link test
that fails, typically due to missing or improper crt*.o, and thus
it set
the NO_EXECUTABLES flag. From that point on, the next test that tries
to link something will give that error, but the problem was whatever
test failed originally. The details should all be in config.log.
OK, thanks a lot for the explanation. I grepped for gcc_no_link and
found that crt2.o was not found, because the latest mingw-win64 crt
puts it in lib64/ while GCC expect it to be in lib/. That brings two
questions: 1. is the lib64/ choice final, and should GCC be modified
to find libraries there? 2. has there been any attempt at building a
multilib -m32/-m64 mingw compiler?
Thanks,
FX