--- Additional Comments From jdavidb at goreadthebible dot com 2005-04-22
17:02 ---
For that matter, if one cannot build the 64 bit compiler with the stock compiler
on Debian sparc64-unknown-linux-gnu, how does one build this compiler?
--
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=2
--- Additional Comments From pinskia at gcc dot gnu dot org 2005-04-22
15:55 ---
/usr/bin/ld: warning: sparc architecture of input file
`../build-sparc64-unknown-linux-gnu/libiberty/libiberty.a(hashtab.o)' is
incompatible with sparc:v9 output
This means that you are building a sparc 64
--- Additional Comments From jdavidb at goreadthebible dot com 2005-04-22
16:00 ---
Thank you, but doesn't this still represent a problem? Shouldn't config.guess
figure out what kind of compiler to build for my platform without my having to
tell it?
I checked and there's nothing in the
--- Additional Comments From davem at gcc dot gnu dot org 2005-04-22 18:27
---
You may with to restart your build with the correct environment
setup, just to be safe. Depending upon what you've enabled
it can take a long time :-)
Yes, the /etc/disable_64_gcc file is what prevents gcc f
--- Additional Comments From jdavidb at goreadthebible dot com 2005-04-22
18:25 ---
(In reply to comment #12)
> Right, it can't compile a test program with "-m64" because the
> /lib64/libc.so.6 package is not installed.
Strangely, I do seem to have that file installed. But I also hav
--- Additional Comments From davem at gcc dot gnu dot org 2005-04-22 18:21
---
Right, it can't compile a test program with "-m64" because the
/lib64/libc.so.6 package is not installed.
Also, when you use "sparc32" you should use it to create a
complete execution environment with "sparc3
--- 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/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
--- 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-bi
--- Additional Comments From jdavidb at goreadthebible dot com 2005-04-22
18:13 ---
(In reply to comment #7)
> > For that matter, if one cannot build the 64 bit compiler with the stock
> > compiler
> > on Debian sparc64-unknown-linux-gnu, how does one build this compiler?
>
> That's a
--- Additional Comments From jdavidb at goreadthebible dot com 2005-04-22
17:50 ---
(In reply to comment #7)
> > For that matter, if one cannot build the 64 bit compiler with the stock
> > compiler
> > on Debian sparc64-unknown-linux-gnu, how does one build this compiler?
>
> That's a
--- Additional Comments From ebotcazou at gcc dot gnu dot org 2005-04-22
17:42 ---
> For that matter, if one cannot build the 64 bit compiler with the stock
> compiler
> on Debian sparc64-unknown-linux-gnu, how does one build this compiler?
That's a Debian problem, the system compiler
--- Additional Comments From ebotcazou at gcc dot gnu dot org 2005-04-22
17:38 ---
David, could you help here? I don't think a cross-compiler is necessary.
--
What|Removed |Added
---
--- Additional Comments From pinskia at gcc dot gnu dot org 2005-04-22
17:24 ---
(In reply to comment #4)
> For that matter, if one cannot build the 64 bit compiler with the stock
> compiler
> on Debian sparc64-unknown-linux-gnu, how does one build this compiler?
You build a cross comp
13 matches
Mail list logo
