On Mon, 2002-01-07 at 20:00, Michel Lanners wrote: > 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?
Nothing here. > Clues, anybody? Not really. :( make and its dependencies are the same versions in woody and sid so it can't be a version conflict. Unless you had something older installed? This is current: make 3.79.1-10 testing libc6 2.2.4-7 testing fileutils 4.1-9 testing -- Earthling Michel D�nzer (MrCooper)/ Debian GNU/Linux (powerpc) developer XFree86 and DRI project member / CS student, Free Software enthusiast
