This is the mail archive of the mailing list for the GCC project.

Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]
Other format: [Raw text]

[Bug bootstrap/21162] Build failure

------- Additional Comments From davem at gcc dot gnu dot org  2005-04-22 18:08 -------
Yes, it should just "work".  And it would have if you:

1) Make sure /lib64/ 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.

           What    |Removed                     |Added
             Status|WAITING                     |RESOLVED
         Resolution|                            |INVALID

Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]