public inbox for linuxppc-dev@ozlabs.org
 help / color / mirror / Atom feed
From: Anton Blanchard <anton@samba.org>
To: Andreas Schwab <schwab@suse.de>
Cc: linuxppc-dev@ozlabs.org, jdittmer@ppp0.net
Subject: Re: boot/wrap assumes a biarch toolchain?
Date: Mon, 29 Oct 2007 09:57:10 -0500	[thread overview]
Message-ID: <20071029145710.GB17120@kryten> (raw)
In-Reply-To: <jesl3udm0e.fsf@sykes.suse.de>

 
Hi,

> If you configure your toolchain for powerpc64-linux you get a biarch
> toolchain by default.

I was wondering about people using pre biarch gcc toolchains. But I take
your point - I'm guessing binutils has been biarch for a long time.
Since we are only calling binutils functions in boot/wrap, maybe we can
just do:

diff --git a/arch/powerpc/boot/Makefile b/arch/powerpc/boot/Makefile
index 18e3271..8961afd 100644
--- a/arch/powerpc/boot/Makefile
+++ b/arch/powerpc/boot/Makefile
@@ -121,13 +121,9 @@ wrapperbits	:= $(extra-y) $(addprefix $(obj)/,addnote hack-coff mktree) \
 #############
 # Bits for building various flavours of zImage
 
-ifneq ($(CROSS32_COMPILE),)
-CROSSWRAP := -C "$(CROSS32_COMPILE)"
-else
 ifneq ($(CROSS_COMPILE),)
 CROSSWRAP := -C "$(CROSS_COMPILE)"
 endif
-endif
 
 # args (to if_changed): 1 = (this rule), 2 = platform, 3 = dts 4=dtb 5=initrd
 quiet_cmd_wrap	= WRAP    $@

      parent reply	other threads:[~2007-10-29 14:57 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
2007-10-30 16:18                   ` Jan Dittmer
2007-10-29 14:57   ` Anton Blanchard [this message]

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=20071029145710.GB17120@kryten \
    --to=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