2.6.0 not accepting CC?

[Kurt Wall]

In a 1.1K blaze of typing glory, Net Llama! wrote:
> On 12/23/03 05:53, Kurt Wall wrote:
> 
> >In a 0.7K blaze of typing glory, Net Llama! wrote:
> >
> >>I've got a Redhat box with gcc-2.96 and my own gcc-3.2.3.  Calling gcc 
> >>will always end up using 2.96.  I've exported CC so that it calls 3.2.3, 
> >>however whenever I attempt to build a 2.6.0 kernel, its ignoring CC, and 
> >>using gcc instead.  Anyone know if this is a bug, or intentional?
> >
> >
> >I don't know if it's a bug or not. Have you tried 
> >
> >$ make CC=/path/to/gcc 
> 
> Nope, didn't try that.  I wasn't aware that make would accept a CC 
> variable.  Even if that does work, this seems like a bug to me, if its 
> ignoring CC altogether and has 'gcc' hardcoded.  Thanks though.

It does. Have a look at the kernel makefile. Note the interaction
between HOSTCC, CC, and CROSSCOMPILE.

It isn't a bug, however. The kernel uses a GCCisms that don't usually
work with non-GCC compilers. The Intel C compiler is a notable
exception, but Intel specifically works to make sure that ICC can
compile the kernel.

Kurt
-- 
Putt's Law:
	Technology is dominated by two types of people:
		Those who understand what they do not manage.
		Those who manage what they do not understand.