From: Keith Owens <kaos@ocs.com.au>
To: "J . A . Magallon" <jamagallon@able.es>
Cc: linux-kernel <linux-kernel@vger.kernel.org>
Subject: Re: CCFOUND and more
Date: Thu, 28 Dec 2000 15:22:59 +1100 [thread overview]
Message-ID: <8203.977977379@ocs3.ocs-net> (raw)
In-Reply-To: Your message of "Tue, 26 Dec 2000 21:11:14 BST." <20001226211114.A1511@werewolf.able.es>
On Tue, 26 Dec 2000 21:11:14 +0100,
"J . A . Magallon" <jamagallon@able.es> wrote:
>Solving other things, I have realized that all that problem on fast
>CC detection (CCFOUND) is easily solved by doing:
> CC := $(.................)
>instead of
> CC = $(.........)
>The find of the suitable CC command is repeated many times along a
>kernel build. And CC is not anything that can change along a kernel
>build. So former syntax solves all the problems, CC detection can
>be so complex as you want because is done only once.
>
>Is there something I am missing ?
Yes. Some arch files change CROSS_COMPILE after CC has been set and
expect the change to flow into the definition of CC. This "feature"
only works because '=' stores the value as text and reevaluates the
text each time, automatically picking up any changes to CROSS_COMPILE.
Using CC := might break m68k and mips. The makefile redesign for 2.5
will fix this problem once and for all.
-
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/
next prev parent reply other threads:[~2000-12-28 4:53 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2000-12-26 20:11 CCFOUND and more J . A . Magallon
2000-12-28 4:22 ` Keith Owens [this message]
2000-12-29 1:27 ` J . A . Magallon
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=8203.977977379@ocs3.ocs-net \
--to=kaos@ocs.com.au \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox