Hello, I am new to the mailing list, so my apologies if this issue has been
covered in the past.
Less than a week ago I switched from RedHat 5.1 installation to SuSe 5.3
[kernel 2.0.35].
I have fixed the problem which I am about to describe, but I would like to
let other newbies know how to fix it if they experience the same thing. I
would also like to know if I can expect any other problems along the same
lines.
I installed all the relevant C development stuff neccesary to compile
programs. When I tried to compile a few basic programs, I kept getting errors
about 'No such file or directory...' for 'linux/*.h' files which were being
refered to by other files. The files were there--well, they were on my hard
disk that is, I knew because I could find them. My newbieness kept me
puzzling over this for longer than I'd like to admit, but I did eventually
figure out that the problem was two broken symbolic links: /usr/include/asm
-was linked to-> ../src/linux/include/asm which should've been linked to->
.../src/linux-2.0.35/include/asm & number two
/usr/include/linux -was linked to-> ../src/linux/include/linux
which should've been linked to-> ../src/linux-2.0.35/include/linux
I just checked, & it seems that the scsi link also is broken in the same
way...
-
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
