Christopher Friesen wrote:
> Andy Whitcroft wrote:
>
>> remove ccache from top level Makefile and make configurable
>
> Isn't it already configurable?
Yes and no. You can specify CC, but you need to know the form of that
line. Ok, we do now but will be in the future. If it changes then the
semantics to use CCACHE would change. This seem like something to avoid.
>> diff -upN reference/Makefile current/Makefile
>> --- reference/Makefile
>> +++ current/Makefile
>> @@ -171,9 +171,11 @@ SUBARCH := $(shell uname -m | sed -e s/i
>> # Alternatively CROSS_COMPILE can be set in the environment.
>> # Default value for CROSS_COMPILE is not to prefix executables
>> # Note: Some architectures assign CROSS_COMPILE in their arch/*/Makefile
>> +# CCACHE specifies the name of a ccache binary to use with gcc.
>>
>> ARCH ?= $(SUBARCH)
>> CROSS_COMPILE ?=
>> +CCACHE ?=
>
>
> This sets it to nothing if it isn't already set--seems like you should
> be able to set it on the commandline or else it has no effect.
Yes this would really allow a subarch to set it if it wanted to, which
isn't likely to. It can probabally be killed.
-apw
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [email protected]
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
[Index of Archives]
[Kernel Newbies]
[Netfilter]
[Bugtraq]
[Photo]
[Stuff]
[Gimp]
[Yosemite News]
[MIPS Linux]
[ARM Linux]
[Linux Security]
[Linux RAID]
[Video 4 Linux]
[Linux for the blind]
[Linux Resources]
