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
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
On Tue, 26 Dec 2000 21:11:14 +0100,
"J . A . Magallon" <[EMAIL PROTECTED]> 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
On Tue, 26 Dec 2000 21:11:14 +0100,
"J . A . Magallon" [EMAIL PROTECTED] 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
Hi everyone.
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
Hi everyone.
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
6 matches
Mail list logo
