--- Comment #8 from pinskia at gcc dot gnu dot org 2006-03-14 03:30 ---
Reporter reports this is fixed so closing as such.
--
pinskia at gcc dot gnu dot org changed:
What|Removed |Added
--
--- Comment #7 from quanah at stanford dot edu 2006-03-14 03:28 ---
gcc 4.0.3 builds for me without issue on the AMD 64, so the issue I hit must
have been something fixed between 4.0.2 and 4.0.3. This can be closed.
--Quanah
--
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=26437
--- Comment #6 from quanah at stanford dot edu 2006-02-27 03:46 ---
What version of binutils would you recommend I try?
--
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=26437
--- Comment #5 from pinskia at gcc dot gnu dot org 2006-02-25 15:55 ---
I cannot reproduce this, I just built 4.0.3 lately and it worked.
Can you try using a different binutils as this seems like a bug there.
--
pinskia at gcc dot gnu dot org changed:
What|Removed
--- Comment #4 from quanah at stanford dot edu 2006-02-25 00:59 ---
Setting the PIC flags did not fix this issue. It appears impossible at this
time to build gcj on AMD64 with 4.0.x.
--Quanah
--
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=26437
--- Comment #3 from quanah at stanford dot edu 2006-02-24 23:24 ---
This may be in part because two variables are not being set correctly:
"PICFLAG=" "PICFLAG_FOR_TARGET="
when building in libjava/
--Quanah
--
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=26437
--- Comment #2 from quanah at stanford dot edu 2006-02-24 23:09 ---
This seems to be because libsax_gcj_la-sax.o is not being built with -fPIC,
like it apparently needs to be:
[EMAIL
PROTECTED]:/afs/ir/src/pubsw/languages/gcc-build/amd64_linux26/x86_64-unknown-linux-gnu/libjava/extern
--- Comment #1 from quanah at stanford dot edu 2006-02-23 01:25 ---
Oh, and here are my configure options:
configure '--datadir=${prefix}/lib' '--libexecdir=${prefix}/lib'
'--sharedstatedir=${prefix}/lib' --prefix=/usr/pubsw --enable-threads --wi
th-gnu-as --with-as=/usr/pubsw/bin/as
