From: Hollis Blanchard <hollisb@us.ibm.com>
To: Sam Ravnborg <sam@ravnborg.org>
Cc: linux-kernel@vger.kernel.org
Subject: Re: using cc-option in arch/ppc64/boot/Makefile
Date: Mon, 18 Oct 2004 13:47:55 +0000 [thread overview]
Message-ID: <200410181347.55746.hollisb@us.ibm.com> (raw)
In-Reply-To: <20041017095700.GB16186@mars.ravnborg.org>
On Sunday 17 October 2004 09:57, Sam Ravnborg wrote:
> Something like this should do the trick?
> You could also include everything in your Makefile but I prefer
> Makefile.lib to make it a bit more general.
That's what I had tried. I'm having strange problems though. This patch:
--- 1.25/arch/ppc64/boot/Makefile Sun Oct 3 12:23:50 2004
+++ edited/arch/ppc64/boot/Makefile Mon Oct 18 14:03:40 2004
@@ -20,6 +20,8 @@
# CROSS32_COMPILE is setup as a prefix just like CROSS_COMPILE
# in the toplevel makefile.
+include scripts/Makefile.lib
+
CROSS32_COMPILE ?=
#CROSS32_COMPILE = /usr/local/ppc/bin/powerpc-linux-
@@ -72,7 +74,12 @@
quiet_cmd_stripvm = STRIP $@
cmd_stripvm = $(STRIP) -s $< -o $@
+HAS_BIARCH := $(call cc-option-yn, -lalala)
+
vmlinux.strip: vmlinux FORCE
+ echo $(cc-option-yn)
+ echo $(HAS_BIARCH)
+ $(call cc-option-yn, -m64)
$(call if_changed,stripvm)
$(obj)/vmlinux.initrd: vmlinux.strip $(obj)/addRamDisk
$(obj)/ramdisk.image.gz FORCE
$(call if_changed,ramdisk)
... yields the following output:
make -f scripts/Makefile.build obj=arch/ppc64/boot arch/ppc64/boot/zImage
echo y
y
echo y
y
y
make[1]: y: Command not found
Also confusing: the gcc switch "-lalala" is invalid, so I don't know where
*any* y's came from. User error?
--
Hollis Blanchard
IBM Linux Technology Center
next prev parent reply other threads:[~2004-10-18 18:56 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-10-14 16:11 Hollis Blanchard
2004-10-17 9:57 ` Sam Ravnborg
2004-10-18 13:47 ` Hollis Blanchard [this message]
2004-10-18 21:01 ` Sam Ravnborg
2004-10-18 15:58 ` Hollis 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=200410181347.55746.hollisb@us.ibm.com \
--to=hollisb@us.ibm.com \
--cc=linux-kernel@vger.kernel.org \
--cc=sam@ravnborg.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
all inboxes | Powered by JetHome®