lkml.org 
[lkml]   [1999]   [Nov]   [7]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
 
Messages in this thread
/
SubjectRe: the joy of scsi headers and glibc...
From
Date
>>>>> CaT  writes:

> Ok. this is beginning to confuse me.
> glibc install:

> Note that `/usr/include/net' and `/usr/include/scsi' should *not* be
> symlinks into the kernel sources. GNU libc provides its own versions
> of these files.

> kernel docs:
You mean Documentation/scsi-generic?

I don't understand why people write such documentation without
contacting the glibc developers first. I've never seen such a request
from anybody regarding the scsi subdirectory.

Instead of writing such lines, it would be better to try to find a
general solution. I kindly ask the author of this docu to get in
contact with me and tell me exactly the existing problems so that we
can fix this in glibc.

Andreas
> Several distributions have taken their own copies of these files and placed
> them in /usr/include/scsi which is where "#include <scsi/sg.h>" would go
> looking. The directory /usr/include/scsi _should_ be a symbolic link to
> /usr/src/linux/include/scsi/ . It was is Redhat 5.1 and 5.2 but it is
> not is Redhat 6.0 . Some other distributions have the same problem. To
> solve this (as root) do the following:

> # cd /usr/include
> # mv scsi scsi_orig
> # ln -s ../src/linux/include/scsi scsi

> Now, the question that I have is... What in the name of god am I to do?

> *sob*

> I hope someone can understand my confusion...

--
Andreas Jaeger
SuSE Labs aj@suse.de
private aj@arthur.rhein-neckar.de

-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.rutgers.edu
Please read the FAQ at http://www.tux.org/lkml/

\
 
 \ /
  Last update: 2005-03-22 13:54    [W:0.053 / U:0.268 seconds]
©2003-2020 Jasper Spaans|hosted at Digital Ocean and TransIP|Read the blog|Advertise on this site