Andreas Schwab wrote:
Jan Dittmer [EMAIL PROTECTED] writes:
Same error, you write above that a newer compiler version should
not need -m32 or --with-cpu=default32 any more?
??? Where did I say that?
Your mail from 2007-10-29 4:39 pm (CET)
Your compiler still needs -m32 to generate
Andreas Schwab wrote:
Jan Dittmer [EMAIL PROTECTED] writes:
Your mail from 2007-10-29 4:39 pm (CET)
Your compiler still needs -m32 to generate 32-bit code (or use
--with-cpu=default32 to make that the default).
See the 'still' ?
How would the compiler know whether to generate 64bit or
Andreas Schwab wrote:
Jan Dittmer [EMAIL PROTECTED] writes:
Your mail from 2007-10-29 4:39 pm (CET)
Your compiler still needs -m32 to generate 32-bit code (or use
--with-cpu=default32 to make that the default).
See the 'still' ?
How would the compiler know whether to generate 64bit or
Hi,
Jan is seeing the following fail:
WRAParch/powerpc/boot/zImage.pmac
powerpc-linux-objcopy: vmlinux: File format not recognized
He is using a cross compile toolchain invoked with the following command
line:
# make HOSTCC=gcc-4.0 ARCH=powerpc CROSS_COMPILE=powerpc64-linux-
Anton Blanchard [EMAIL PROTECTED] writes:
One way to make this go away would be to build binutils as biarch:
# configure --target=powerpc-linux --enable-targets=powerpc64-linux ...
If you configure your toolchain for powerpc64-linux you get a biarch
toolchain by default.
Andreas.
--
Hi,
If you configure your toolchain for powerpc64-linux you get a biarch
toolchain by default.
I was wondering about people using pre biarch gcc toolchains. But I take
your point - I'm guessing binutils has been biarch for a long time.
Since we are only calling binutils functions in
Jan Dittmer [EMAIL PROTECTED] writes:
$ powerpc64-linux-gcc-4.0.4 -v
Using built-in specs.
Target: powerpc64-linux
Configured with: ../configure --prefix=/usr/cc217
--exec-prefix=/usr/cc217/powerpc64 --target=powerpc64-linux
--disable-shared --disable-werror --disable-nls --disable-threads
Andreas Schwab wrote:
Jan Dittmer [EMAIL PROTECTED] writes:
Andreas Schwab wrote:
Jan Dittmer [EMAIL PROTECTED] writes:
$ powerpc64-linux-gcc-4.0.4 -v
Using built-in specs.
Target: powerpc64-linux
Configured with: ../configure --prefix=/usr/cc217
--exec-prefix=/usr/cc217/powerpc64
Andreas Schwab wrote:
Jan Dittmer [EMAIL PROTECTED] writes:
$ powerpc64-linux-gcc-4.0.4 -v
Using built-in specs.
Target: powerpc64-linux
Configured with: ../configure --prefix=/usr/cc217
--exec-prefix=/usr/cc217/powerpc64 --target=powerpc64-linux
--disable-shared --disable-werror
Andreas Schwab wrote:
Anton Blanchard [EMAIL PROTECTED] writes:
One way to make this go away would be to build binutils as biarch:
# configure --target=powerpc-linux --enable-targets=powerpc64-linux ...
If you configure your toolchain for powerpc64-linux you get a biarch
toolchain by
Jan Dittmer [EMAIL PROTECTED] writes:
Same error, you write above that a newer compiler version should
not need -m32 or --with-cpu=default32 any more?
??? Where did I say that?
Andreas.
--
Andreas Schwab, SuSE Labs, [EMAIL PROTECTED]
SuSE Linux Products GmbH, Maxfeldstraße 5, 90409
11 matches
Mail list logo