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 08:30:10 +0100 [thread overview]
Message-ID: <4726DD82.8050200@l4x.org> (raw)
In-Reply-To: <je640pebqn.fsf@sykes.suse.de>
Andreas Schwab wrote:
> Jan Dittmer <jdi@l4x.org> 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 32-bit code (or use
>> --with-cpu=default32 to make that the default).
See the 'still' ? I just assumed that it must have been changed
in newer versions.
But to sum up. I've to compile with '--with-cpu=default32' and all
should be fine? Because I have no idea how to pass the -m32 flag
just to the 32-bit code generation. Passing it via CFLAGS obviously
does not work as it also passes it to the 64 bit code generation.
Jan
next prev parent reply other threads:[~2007-10-30 7:35 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 [this message]
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=4726DD82.8050200@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.