From: "J . A . Magallon" <jamagallon@able.es>
To: Keith Owens <kaos@ocs.com.au>
Cc: linux-kernel <linux-kernel@vger.kernel.org>
Subject: Re: CCFOUND and more
Date: Fri, 29 Dec 2000 02:27:03 +0100 [thread overview]
Message-ID: <20001229022703.A3038@werewolf.able.es> (raw)
In-Reply-To: <20001226211114.A1511@werewolf.able.es> <8203.977977379@ocs3.ocs-net>
In-Reply-To: <8203.977977379@ocs3.ocs-net>; from kaos@ocs.com.au on Thu, Dec 28, 2000 at 05:22:59 +0100
On 2000.12.28 Keith Owens wrote:
>
> 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.
>
OK, understrood. Anyway, I know there is not too much impact of this
issue, but you could always convert-to-fast-version the more
critical vars with something like:
CC = .........
CPP = $(CC) -E
..
include arch/$(ARCH)/Makefile
# Eval them once forever
CC:=$(CC)
CPP:=$(CPP)
--
J.A. Magallon $> cd pub
mailto:jamagallon@able.es $> more beer
Linux werewolf 2.2.19-pre3-aa3 #3 SMP Wed Dec 27 10:25:32 CET 2000 i686
-
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:[~2000-12-29 1:57 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
2000-12-29 1:27 ` J . A . Magallon [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=20001229022703.A3038@werewolf.able.es \
--to=jamagallon@able.es \
--cc=kaos@ocs.com.au \
--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