From: Keith Owens <kaos@ocs.com.au>
To: "J . A . Magallon" <jamagallon@able.es>
Cc: Alan Cox <alan@lxorguk.ukuu.org.uk>, linux-kernel@vger.kernel.org
Subject: Re: Linux 2.2.19pre5
Date: Wed, 03 Jan 2001 18:24:16 +1100 [thread overview]
Message-ID: <11635.978506656@kao2.melbourne.sgi.com> (raw)
In-Reply-To: Your message of "Wed, 03 Jan 2001 04:15:16 BST." <20010103041516.C1497@werewolf.able.es>
On Wed, 3 Jan 2001 04:15:16 +0100,
"J . A . Magallon" <jamagallon@able.es> wrote:
>I have seen that the CCFOUND stuff has flown away. I have read it
>breaks somthing, and the CROSS_COMPILE in alphas and m68k.
>Perhaps this way could be better : ??
>..
>include arch/$(ARCH)/Makefile
>
>AS :=$(AS)
>LD :=$(LD)
>CC :=$(CC)
>CPP :=$(CPP)
Agreed. Alan, please apply.
Index: 19-pre5.1/Makefile
--- 19-pre5.1/Makefile Wed, 03 Jan 2001 17:44:03 +1100 kaos (linux-2.2/G/b/14_Makefile 1.3.2.2.1.1.1.5.1.3.6.1.5.1.1.1.1.16.1.16 644)
+++ 19-pre5.1(w)/Makefile Wed, 03 Jan 2001 18:15:57 +1100 kaos (linux-2.2/G/b/14_Makefile 1.3.2.2.1.1.1.5.1.3.6.1.5.1.1.1.1.16.1.16 644)
@@ -219,6 +219,17 @@ DRIVERS := $(DRIVERS) drivers/telephony/
endif
include arch/$(ARCH)/Makefile
+# arch/$(ARCH)/Makefile is the last thing that is allowed to change CROSS_COMPILE.
+# Revaluate final values for speed.
+AS :=$(AS)
+LD :=$(LD)
+CC :=$(CC)
+CPP :=$(CPP)
+AR :=$(AR)
+NM :=$(NM)
+STRIP :=$(STRIP)
+OBJCOPY :=$(OBJCOPY)
+OBJDUMP :=$(OBJDUMP)
.S.s:
$(CC) -D__ASSEMBLY__ $(AFLAGS) -traditional -E -o $*.s $<
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
Please read the FAQ at http://www.tux.org/lkml/
prev parent reply other threads:[~2001-01-03 7:55 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-01-03 2:49 Linux 2.2.19pre5 Alan Cox
2001-01-03 3:15 ` J . A . Magallon
2001-01-03 7:24 ` Keith Owens [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=11635.978506656@kao2.melbourne.sgi.com \
--to=kaos@ocs.com.au \
--cc=alan@lxorguk.ukuu.org.uk \
--cc=jamagallon@able.es \
--cc=linux-kernel@vger.kernel.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.