------- Additional Comments From jdavidb at goreadthebible dot com 2005-04-22 18:15 ------- (In reply to comment #9) > Yes, it should just "work". And it would have if you: > > 1) Make sure /lib64/libc.so.6 is installed. > 2) Delete the file /etc/disable_64_gcc > > Then gcc would output 64-bit code by default when the > "uname" command outputs "sparc64". You could then simply > run "sparc32 bash" to get an environment where uname outputs > plain "sparc" and this causes the Debian gcc to output 32-bit > code by default. > > We plan on adding similar logic to the compiler driver itself. > > I totally agree with you that when "uname" outputs "sparc64" > the compiler on the system should be outputting 64-bit code > by default which is what many (not just gcc's) configure > scripts and build trees expect. > > Since this problem has to do with Debian's gcc behavior and > not with a gcc proper bug per-se, I'm closing this as invalid.
Thanks for the additional information. I'm in uncharted waters for me personally with the mixed 32/64 bit environment. Sounds like the preferred solution, at present, is to run $ sparc32 ../gcc-4.0.0/configure ... Someone might add a note to the docs along these lines: "If you are running Debian GNU/Linux for Sparc and you 'just want a compiler,' you will probably need to set up a 32-bit sparc environment when you run configure, as follows: $ sparc32 ../gcc-4.0.0/configure ..." -- http://gcc.gnu.org/bugzilla/show_bug.cgi?id=21162
