From: Andreas Schwab <schwab@suse•de>
To: Jan Dittmer <jdittmer@ppp0•net>
Cc: linuxppc-dev@ozlabs•org, Anton Blanchard <anton@samba•org>
Subject: Re: boot/wrap assumes a biarch toolchain?
Date: Mon, 29 Oct 2007 16:39:21 +0100 [thread overview]
Message-ID: <jelk9mdj6e.fsf@sykes.suse.de> (raw)
In-Reply-To: <4725F34C.6090904@ppp0.net> (Jan Dittmer's message of "Mon\, 29 Oct 2007 15\:50\:52 +0100")
Jan Dittmer <jdittmer@ppp0•net> 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
> --disable-werror --disable-libmudflap --with-newlib --with-gnu-as
> --with-gnu-ld --enable-languages=c
> Thread model: single
> gcc version 4.0.4
>
> g5_defconfig:
>
> $ make ARCH=powerpc HOSTCC=gcc-4.0 CROSS_COMPILE=powerpc64-linux-
> CROSS32_COMPILE=powerpc64-linux-
Your compiler still needs -m32 to generate 32-bit code (or use
--with-cpu=default32 to make that the default).
Andreas.
--
Andreas Schwab, SuSE Labs, schwab@suse•de
SuSE Linux Products GmbH, Maxfeldstraße 5, 90409 Nürnberg, Germany
PGP key fingerprint = 58CA 54C7 6D53 942B 1756 01D3 44D5 214B 8276 4ED5
"And now for something completely different."
next prev parent reply other threads:[~2007-10-29 15:39 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-10-29 14:07 boot/wrap assumes a biarch toolchain? Anton Blanchard
2007-10-29 14:38 ` Andreas Schwab
2007-10-29 14:50 ` Jan Dittmer
2007-10-29 15:39 ` Andreas Schwab [this message]
2007-10-29 19:44 ` Jan Dittmer
2007-10-29 21:15 ` Andreas Schwab
2007-10-29 21:49 ` Jan Dittmer
2007-10-29 23:34 ` Andreas Schwab
2007-10-30 7:30 ` Jan Dittmer
2007-10-30 9:20 ` Andreas Schwab
2007-10-30 16:15 ` Jan Dittmer
2007-10-30 16:18 ` Jan Dittmer
2007-10-29 14:57 ` Anton Blanchard
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=jelk9mdj6e.fsf@sykes.suse.de \
--to=schwab@suse$(echo .)de \
--cc=anton@samba$(echo .)org \
--cc=jdittmer@ppp0$(echo .)net \
--cc=linuxppc-dev@ozlabs$(echo .)org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox