[Bug target/17646] [4.0 Regression] xgcc links 64bit objects into a 32bit target

2005-01-06 Thread jakub at gcc dot gnu dot org
--- Additional Comments From jakub at gcc dot gnu dot org 2005-01-06 14:12 --- There is no bug, the compiler has been configured incorrectly. --libdir=/usr/lib64 should not be used for multilibbed gcc's, --libdir=/usr/lib is what you want. The os multilib magic will DTRT. Similarly,

[Bug target/17646] [4.0 Regression] xgcc links 64bit objects into a 32bit target

2005-01-06 Thread pinskia at gcc dot gnu dot org
--- Additional Comments From pinskia at gcc dot gnu dot org 2005-01-06 14:16 --- So closing as invalid. -- What|Removed |Added Status|UNCONFIRMED

[Bug target/17646] [4.0 Regression] xgcc links 64bit objects into a 32bit target

2005-01-06 Thread olh at suse dot de
--- Additional Comments From olh at suse dot de 2005-01-06 21:58 --- I tried this: /home/abuild/gcc-4.0.0-20050103/configure --enable-threads=posix --prefix=/usr --with-local-prefix=/usr/local --infodir=/usr/share/info --mandir=/usr/share/man --enable-languages=c,c++,objc,f95,java

[Bug target/17646] [4.0 Regression] xgcc links 64bit objects into a 32bit target

2005-01-06 Thread pinskia at gcc dot gnu dot org
--- Additional Comments From pinskia at gcc dot gnu dot org 2005-01-06 22:42 --- (In reply to comment #17) I tried this: That appears to work. Only the binaries like cc1 end up in /usr/libexec/gcc/powerpc64-suse-linux/4.0.0 This should be /usr/lib64/gcc-lib (at least thats the

[Bug target/17646] [4.0 Regression] xgcc links 64bit objects into a 32bit target

2005-01-06 Thread olh at suse dot de
--- Additional Comments From olh at suse dot de 2005-01-06 23:46 --- Ok, libexec always looked like a sane place, to me. But anyway. I will leave it to Andreas to update our rpm spec file. I still wonder why the same configure options work on x86_64-linux --

[Bug target/17646] [4.0 Regression] xgcc links 64bit objects into a 32bit target

2004-12-19 Thread pinskia at gcc dot gnu dot org
--- Additional Comments From pinskia at gcc dot gnu dot org 2004-12-20 01:02 --- Is this fixed now? -- http://gcc.gnu.org/bugzilla/show_bug.cgi?id=17646

[Bug target/17646] [4.0 Regression] xgcc links 64bit objects into a 32bit target

2004-12-19 Thread aj at gcc dot gnu dot org
--- Additional Comments From aj at gcc dot gnu dot org 2004-12-20 05:57 --- It is not fixed, it still fails the same way -- http://gcc.gnu.org/bugzilla/show_bug.cgi?id=17646

[Bug target/17646] [4.0 Regression] xgcc links 64bit objects into a 32bit target

2004-10-27 Thread jgrimm2 at us dot ibm dot com
--- Additional Comments From jgrimm2 at us dot ibm dot com 2004-10-27 15:38 --- What I've finally done to get my 64-bit biarch default64 compiler is to first build a 32-bit biarch default64 compiler. I can then make bootstrap using this intermediate compiler as the host compiler to

[Bug target/17646] [4.0 Regression] xgcc links 64bit objects into a 32bit target

2004-10-19 Thread jgrimm2 at us dot ibm dot com
--- Additional Comments From jgrimm2 at us dot ibm dot com 2004-10-19 21:25 --- I see this too. Or rather, I see what Michael is describing. Should there be a new bug for the problem as described by Michael? My test scenario was from desire to build 64-bit biarch compiler that