From: Brian May <bam@snoopy.apana.org.au>
To: linux-kernel@vger.kernel.org
Subject: Re: Fix for include/linux/fs.h in 2.4.0 kernels
Date: 03 Feb 2001 14:03:09 +1100 [thread overview]
Message-ID: <847l38lb82.fsf@snoopy.apana.org.au> (raw)
In-Reply-To: <20010203004926.M160@pervalidus.dyndns.org>
In-Reply-To: 0@pervalidus.net's message of "3 Feb 01 02:49:26 GMT"
>>>>> "Frédéric" == Frédéric L W Meunier <0@pervalidus.net> writes:
Frédéric> Keith Owens wrote:
>> Rule 2. Any glibc that has a symlink from
>> /usr/include/{linux,asm} to /usr/src/linux/include/{linux,asm}
>> is wrong.
Frédéric> Such symlinks are created by the user.
>> Relying on /usr/include/{linux,asm} always pointing at the
>> current kernel source is broken as designed.
Frédéric> From glibc 2.2.1 FAQ:
Frédéric> 2.17. I have /usr/include/net and /usr/include/scsi as
Frédéric> symlinks into my Linux source tree. Is that wrong?
Frédéric> {PB} This was necessary for libc5, but is not correct
Frédéric> when using glibc. Including the kernel header files
Frédéric> directly in user programs usually does not work (see
Frédéric> question 3.5). glibc provides its own <net/*> and
Frédéric> <scsi/*> header files to replace them, and you may have
Frédéric> to remove any symlink that you have in place before you
Frédéric> install glibc. However, /usr/include/asm and
Frédéric> /usr/include/linux should remain as they were.
Frédéric> Keith, are you saying that glibc is wrong?
You both seem to be saying the same thing: that symlinks for
/usr/include/{linux,asm} are wrong.
Why try to argue when you agree?
(Debian does this right; last I heard Red-Hat didn't)
--
Brian May <bam@snoopy.apana.org.au>
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
Please read the FAQ at http://www.tux.org/lkml/
next prev parent reply other threads:[~2001-02-03 3:03 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-02-03 2:49 Frédéric L. W. Meunier
2001-02-03 3:03 ` Brian May [this message]
2001-02-03 3:10 ` Keith Owens
2001-02-03 4:21 ` Brian May
2001-02-03 4:39 ` Brian Wellington
2001-02-03 4:41 ` Brian May
2001-02-03 8:48 ` Graham Murray
2001-02-03 8:59 ` Keith Owens
2001-02-03 10:09 ` Graham Murray
2001-02-03 11:38 ` Keith Owens
-- strict thread matches above, loose matches on Subject: below --
2001-02-02 23:04 Jocelyn Mayer
2001-02-02 23:25 ` Keith Owens
2001-02-03 7:42 ` Alan Cox
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=847l38lb82.fsf@snoopy.apana.org.au \
--to=bam@snoopy.apana.org.au \
--cc=linux-kernel@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®