This is the mail archive of the
gcc@gcc.gnu.org
mailing list for the GCC project.
64-bit configure hell
- From: Stan Shebs <shebs at apple dot com>
- To: gcc at gcc dot gnu dot org
- Date: Wed, 24 Nov 2004 15:08:55 -0800
- Subject: 64-bit configure hell
I have a messy configure problem with 64-bit Darwin, and would
like to get some ideas about how to solve. The situation is that
Darwin 8.x aka Tiger is capable of running 64-bit-address-space
programs on G5s, and to support that in GCC I've set up a multilib
for the -m64 option that enables it. This all works on G5 Tiger
now, at least on prime-number days of the month when the moon is
full :-) , and I hope to check in the last bits soon.
The problem is that Tiger also runs on G4s, which are not capable
of running 64-bit programs - all the machinery is there to build
complete and correct binaries, the kernel just refuses to execute
them. This causes problems for some configure scripts, in particular
those in libstdc++ and libobjc, which want to be able to run
executables. It's not entirely clear to me why that's important,
since the libraries already build and run perfectly fine for
cross-compilers.
Although it would be good for sales to require that people
building GCC on Darwin upgrade to G5s :-) that's kind of
unfriendly, while producing different results from configure
and make depending on one's CPU is also just asking for
trouble. What other options do I have?
Stan