All of lore.kernel.org
 help / color / mirror / Atom feed
From: Andreas Schwab <schwab@suse.de>
To: Jan Dittmer <jdi@l4x.org>
Cc: linuxppc-dev@ozlabs.org, Anton Blanchard <anton@samba.org>
Subject: Re: boot/wrap assumes a biarch toolchain?
Date: Tue, 30 Oct 2007 10:20:15 +0100	[thread overview]
Message-ID: <jey7dlez74.fsf@sykes.suse.de> (raw)
In-Reply-To: <4726DD82.8050200@l4x.org> (Jan Dittmer's message of "Tue\, 30 Oct 2007 08\:30\:10 +0100")

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.

-- 
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."

  reply	other threads:[~2007-10-30  9:20 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 [this message]
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=jey7dlez74.fsf@sykes.suse.de \
    --to=schwab@suse.de \
    --cc=anton@samba.org \
    --cc=jdi@l4x.org \
    --cc=linuxppc-dev@ozlabs.org \
    /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.