linuxppc-dev.lists.ozlabs.org archive mirror
 help / color / mirror / Atom feed
From: Adam Litke <agl@us.ibm.com>
To: paulus@samba.org
Cc: linuxppc-dev@ozlabs.org
Subject: zImage wrapper broken when cross compiling on Intel
Date: Tue, 10 Oct 2006 10:39:30 -0500	[thread overview]
Message-ID: <1160494770.9894.10.camel@localhost.localdomain> (raw)

Hey Paul.  My cross compile environment has been broken by the zImage
wrapper stuff.  I set both CROSS_COMPILE and CROSS32_COMPILE and build
my pSeries kernels on an Intel box.  The current logic is setting
CROSSWRAP := -C $(CROSS32_COMPILE) but my cross32 tools don't understand
the 64bit binaries I built :)

I am not quite sure how to properly handle my case without breaking one
of the other cases you are probably accounting for with the current
logic.  For the time being I've hacked my Makefile with the following
patch (just to get things working again for me).

 Makefile |    8 ++++----
 1 file changed, 4 insertions(+), 4 deletions(-)
diff -upN reference/arch/powerpc/boot/Makefile current/arch/powerpc/boot/Makefile
--- reference/arch/powerpc/boot/Makefile
+++ current/arch/powerpc/boot/Makefile
@@ -104,13 +104,13 @@ wrapperbits	:= $(extra-y) $(addprefix $(
 #############
 # Bits for building various flavours of zImage
 
-ifneq ($(CROSS32_COMPILE),)
-CROSSWRAP := -C $(CROSS32_COMPILE)
-else
+#ifneq ($(CROSS32_COMPILE),)
+#CROSSWRAP := -C $(CROSS32_COMPILE)
+#else
 ifneq ($(CROSS_COMPILE),)
 CROSSWRAP := -C $(CROSS_COMPILE)
 endif
-endif
+#endif
 
 quiet_cmd_wrap	= WRAP    $@
       cmd_wrap	=$(CONFIG_SHELL) $(wrapper) -c -o $@ -p $2 $(CROSSWRAP) vmlinux

-- 
Adam Litke - (agl at us.ibm.com)
IBM Linux Technology Center

                 reply	other threads:[~2006-10-10 15:39 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=1160494770.9894.10.camel@localhost.localdomain \
    --to=agl@us.ibm.com \
    --cc=linuxppc-dev@ozlabs.org \
    --cc=paulus@samba.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 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).