Hey all, >>> I'd run the command that segfaults directly, if I knew which one? Hm, >>> make -n comes to mind... I'll have to see what that gives. >> >> -n won't do anything so I'm not sure it'll act just as make (in case >> targets get updated). Add a few echo "yadda" around the makefile to see >> where it happens. > > Well, for sure make -n dep segfaults as well. Not always in the same > spot, but always. Repeatedly executing make -n dep tends to go further > and further in the process. It also makes it clear that it's indeed make > that segfaults: it's within a sequence of terminating childs that it > segfaults.
OK, I tried other memory DIMMs: no dice. I then tried to recompile make locally: that worked! (rebuilt the .deb, in fact). So, the question that remains is: why on earth am I the only that one whose make segfaults when building kernels? What is wrong (if anything) with woody's make package? Clues, anybody? Cheers Michel ------------------------------------------------------------------------- Michel Lanners | " Read Philosophy. Study Art. 23, Rue Paul Henkes | Ask Questions. Make Mistakes. L-1710 Luxembourg | email [EMAIL PROTECTED] | http://www.cpu.lu/~mlan | Learn Always. "
