From: Jan Dittmer <jdi@l4x.org>
To: Andreas Schwab <schwab@suse.de>
Cc: linuxppc-dev@ozlabs.org, Anton Blanchard <anton@samba.org>
Subject: Re: boot/wrap assumes a biarch toolchain?
Date: Tue, 30 Oct 2007 17:15:42 +0100 [thread overview]
Message-ID: <472758AE.70207@l4x.org> (raw)
In-Reply-To: <jey7dlez74.fsf@sykes.suse.de>
Andreas Schwab wrote:
> Jan Dittmer <jdi@l4x.org> 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 32bit code??
Andreas, I think we both got a bit lost. Lets take a step back.
The original problem was that after 2.6.23 cross compiling
powerpc/g5_defconfig broke (Regression). Using gcc 4.0.4, powerpc64
target as cross compiler and powerpc target as 32-bit cross compiler.
Since 2.6.23-git1 it is now broken. Using gcc 4.1.2 didn't fix this. Neither
with "--with-cpu=default32" present nor without. So could you please
explain to me how I'm supposed to cross compile powerpc/g5_defconfig now?
Passing CFLAGS=-m32 didn't help too.
Or is it just a new bug in the kernel make system?
Just for reference up till 2.6.23 I used the following command:
make ARCH=powerpc HOSTCC=gcc-4.0 CROSS_COMPILE=powerpc64-linux- \
CROSS32_COMPILE=powerpc-linux-
Thanks,
Jan
next prev parent reply other threads:[~2007-10-30 16:15 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
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 [this message]
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=472758AE.70207@l4x.org \
--to=jdi@l4x.org \
--cc=anton@samba.org \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.