On Thu, Dec 28, 2000 at 04:54:54PM -0600, Nathan E Norman wrote: > On Thu, Dec 28, 2000 at 04:30:07PM -0600, Rob VanFleet wrote: > > On Thu, Dec 28, 2000 at 07:29:12PM +0100, Carel Fellinger wrote: > > > I think it would be wise (and more debian like:) to explain how to > > > compile the kernel as *non* root using fakeroot. Furthermore I seem > > > to recall discussions on this list that it's better to refrain from > > > using/creating that /usr/src/linux link. > > > > I've been reading that as well, but I have yet to find out why it is a bad > > idea. Also, when my system was originally installed I didn't have > > /usr/src/linux symlink, but until I made one I couldn't compile any modules. > > So how would one tell code that needs to look for the kernel headers to look > > somewhere else? > > I think there's confusion between making links in /usr/include and > links in /usr/src. The first is bad [0], the second is (afaik) not.
Hmm, as I understood it, making a /usr/src/linux link is bad, /usr/include, AFAIK, is not the issue. The module I tried to compiled looked for the kernel-includes in /usr/src/linux/include. I'm just wondering why /usr/src/linux is bad, and how to tell compiles to look somewhere other than /usr/src/linux. -Rob
