On Thu, Dec 28, 2000 at 05:05:30PM -0600, Rob VanFleet wrote: > > 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. I'm not trying to be rude, but the only person saying the /usr/src/linux symlink is bad is you (and you don't sound convinced :) I've never heard that a /usr/src/linux symlink is bad; I have heard people freak out if the entire kernel-source tree is unpacked in a /usr/src/linux directory ... So far, everyone agrees that a /usr/src/linux symlink is ok, especially if some module depends on its presence. Cheers, -- Nathan Norman - Staff Engineer | A good plan today is better Micromuse Inc. | than a perfect plan tomorrow. mailto:nnorman@micromuse.com | -- Patton
Attachment:
pgpeR8aorXaXa.pgp
Description: PGP signature