Now the reason I did "make -j" was because I hadn't yet tried it on a
kernel which would blow up (2.1.108 didn't) and I wanted to observe the
symptoms at first hand. So I watched it with top, and when it got to
430ish processes, I ctrl-c'ed the make. It stopped, no problem.
Then I tried a more sane "make -j4 zImage", and it failed. Some
messages (ironically including the ll_rw_blk.c file) about things not
defined etc. etc. I thought, oh well, a buggy kernel, some option or
other hasn't been modified in the makefiles, I'll wait a while for the
patches etc.
But just to see, I tried again, with
make mrproper
make config
make dep;make clean
make zImage
This time, I got much more basic messages: in one of the very first
files to be compiled, I suddenly got "asm/io.h: file not found".
This woke me up. I did a comparison with the tar.bz2 file and found:
linux/include/linux/proc_fs.h: File does not exist
linux/include/linux/locks.h: File does not exist
linux/include/linux/poll.h: File does not exist
linux/include/linux/malloc.h: File does not exist
linux/include/linux/mc146818rtc.h: File does not exist
linux/include/linux/blk.h: File does not exist
linux/include/linux/selection.h: File does not exist
linux/include/linux/parport_pc.h: File does not exist
linux/include/asm-i386/dma.h: File does not exist
linux/include/asm-i386/io.h: File does not exist
linux/include/net/arp.h: File does not exist
linux/include/net/sock.h: File does not exist
linux/include/net/route.h: File does not exist
linux/include/net/ipx.h: File does not exist
linux/include/net/spx.h: File does not exist
linux/include/net/dst.h: File does not exist
linux/include/net/ndisc.h: File does not exist
linux/drivers/scsi/sd.h: File does not exist
(Lots of other include files had been modified but this appears to be
normal behaviour?)
Now, since this is on a DualPII400 (Dell 410, 512MB, 7890 SCSI), it
could be an SMP problem, an aic7xxx problem, or perhaps just freaky
kernel build behaviour.
Does anyone know of circumstances in which an out-of-control "make" can
end up deleting files ? Or perhaps if an out of control "make -j
zImage" on the linux kernel can perhaps do this - since it does modify
some include files maybe it can wipe some too ?
This bothered me lots. I fsck'ed and found nothing wrong, so I'm at a
loss to proceed.
Help?
Neil Conway
neil.conway@ukaea.org.uk
PS: I subsequently untarred again, copied in the SAME .config file, did
make config
make dep;make clean
make zImage
and it worked fine (though the kernel was too big so I then used
bzImage).
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.rutgers.edu
Please read the FAQ at http://www.tux.org/lkml/