[Aboriginal] lsi_scsi: error

[John Spencer]

On 10/10/2011 07:35 PM, Rob Landley wrote:
> On 10/10/2011 01:14 AM, John Spencer wrote:
>> On 10/10/2011 03:08 AM, John Spencer wrote:
>>> btw, do you happen to know by chance why the kernel make disrespects
>>> my CC/HOSTCC settings and uses gcc instead of distcc ?
>> nevermind, it seems the only way is to mess with the makefile, if you
>> dont happen to use the usual prefixed crosstoolchain.
> Make is horrible, here's how bits of the horror work:
>
> Environment variables become the default values of make variables when
> make starts, but there are two forms of assignment in make: ?= leaves a
> variable alone if it already has a value, = overwrites unconditionally.
>   Make developers tend to use the = without thinking about it.
>
> To overcome this, variables assigned on the make command line become
> read-only and cannot be overridden by make assignments.  (The
> assignments are ignored.)  Thus you specify your architecture and cross
> compiler on the command line, not in environment variables.

thanks for the explanation. using make dep; make -j4 CC=distcc i could 
finally get the kernel to use distcc...
however it compiles since more than 26 hours. the distcc threads on the 
host are rarely doing some work.
it seems the bottleneck is the cpp work done on the qemu vm.
google has targeted this weakness in their "pump mode" addition to 
distcc, but that is unfortunately written in *python*.
it seems nobody, and especially not big corporations, cares about 
portability any more.
> Then we get into recursive make, which is an abomination:
>
>    http://aegis.sourceforge.net/auug97.pdf
>
> And really, the whole of make has outlived its usefulness, but I've
> ranted about that here (at length) before:
>
> http://lists.landley.net/pipermail/aboriginal-landley.net/2011-June/000165.html
lol, that sounds familiar.

apart from its syntax which is even harder to learn than perl, make is 
not that bad imo... at least it is available on nearly all systems and 
compiles without patches, and is relatively powerful.
once you copy/pasted together your first working makefile, you can reuse 
that relatively well....
of course i could imagine a better solution, but hey, most of the rest 
is much worse ;)
> Rob
>




 1318394627.0