"Rafael E. Herrera" wrote:
>
> Hi,
>
> The README file in /usr/src/linux-2.0.36.SuSE mentions checking the
> links /usr/include/asm, /usr/include/linux, and /usr/include/scsi.
> Checking my fresh SuSE 6.0 install I found that 'asm' and 'linux' where
> linked properly, but 'scsi' was not a symlink. There was a directory
> there with what appeared to a different header file (sg.h) from the
> kernel sources. I moved and set up the symlink for that directory.
> Compiled 2.2.5 without problems. I've no problems with my scsi device.
>
> Does anybody have the symlinks set up that way after a fresh install?
>
> By the way, the READMEs for 2.2.4 or 2.2.5 do not mention this issue
> about setting the symlinks.
Don't care about these symlinks, or better, leave your fingers off.
These things have, for good reason, been removed from the README.
Fiddling with /usr/include/{asm,scsi,linux} will most probably
break your development environment.
If you compile software, it normally shouldn,t use the kernel headers,
but the (g)libc headers. Otherwise you risk having to recompile software
whenever the kernel changes.
Henning
--
H. Henning Vossieck - [EMAIL PROTECTED] - http://www.ndh.net/home/vossieck/
49 2291 3010/6519
--
To get out of this list, please send email to [EMAIL PROTECTED] with
this text in its body: unsubscribe suse-linux-e
Check out the SuSE-FAQ at http://www.suse.com/Support/Doku/FAQ/ and the
archive at http://www.suse.com/Mailinglists/suse-linux-e/index.html
