Brian <lxy at cloudnet.com> writes: > On 18 Oct 2001, Jon Schewe wrote: > > > Figured it out. Seems that there's a bug in the 2.4.10 nfs server that > > created bad symlinks. Something like instead of linking to the file, it > > linked to the actual data, so ls would give me foo -> #include <stdio.h> ... > > Really nasty. I put everything local, recompiled and rebooted and I'm all > > good now. > > This is why I use the Linus/Alan approved method of compiling kernels in > my home directory (no symlinking). The only thing you need to be root for > is to rebuild the boot sector and install the modules if applicable. It > also assures that the headers you're compiling against are the same across > all your apps, which in your case turned out to be a problem for you. > > I compile all my kernels this way and it makes a lot more sense than > dumping everything to /usr/local/src. I'm compiling it in a separate directory too, however the Makefile creates symlinks itself. The one I was getting into trouble with was the one it makes in linux/include from asm-i386 to asm. -- Jon Schewe | http://mtu.net/~jpschewe | jpschewe at mtu.net For I am convinced that neither death nor life, neither angels nor demons, neither the present nor the future, nor any powers, neither height nor depth, nor anything else in all creation, will be able to separate us from the love of God that is in Christ Jesus our Lord. - Romans 8:38-39