From: Jan Dittmer <jdi@l4x.org>
To: Andreas Schwab <schwab@suse.de>
Cc: linuxppc-dev@ozlabs.org, Jan Dittmer <jdittmer@ppp0.net>,
Anton Blanchard <anton@samba.org>
Subject: Re: boot/wrap assumes a biarch toolchain?
Date: Mon, 29 Oct 2007 20:44:48 +0100 [thread overview]
Message-ID: <47263830.2010009@l4x.org> (raw)
In-Reply-To: <jelk9mdj6e.fsf@sykes.suse.de>
Andreas Schwab wrote:
> 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).
4.1.2 exhibits the same behavior. When did it start to work without
additional options? 4.2?
Jan
next prev parent reply other threads:[~2007-10-29 20:13 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
2007-10-29 19:44 ` Jan Dittmer [this message]
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=47263830.2010009@l4x.org \
--to=jdi@l4x.org \
--cc=anton@samba.org \
--cc=jdittmer@ppp0.net \
--cc=linuxppc-dev@ozlabs.org \
--cc=schwab@suse.de \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
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;
as well as URLs for NNTP newsgroup(s).