From: Keith Owens <kaos@ocs.com.au>
To: linux-kernel@vger.kernel.org
Subject: Re: Fix for include/linux/fs.h in 2.4.0 kernels
Date: Sat, 03 Feb 2001 22:38:19 +1100 [thread overview]
Message-ID: <15031.981200299@ocs3.ocs-net> (raw)
In-Reply-To: Your message of "03 Feb 2001 10:09:39 -0000." <m28znoulgc.fsf@barnowl.demon.co.uk>
On 03 Feb 2001 10:09:39 +0000,
Graham Murray <graham@barnowl.demon.co.uk> wrote:
>Keith Owens <kaos@ocs.com.au> writes:
>> This has all been thrashed out before. Read the threads
>>
>> http://www.mail-archive.com/linux-kernel@vger.rutgers.edu/2000-month-07/msg04096.html
>> http://www.mail-archive.com/linux-kernel@vger.kernel.org/msg18256.html
>
>I don't think that these address my question. I was asking about when
>building (upgrading) glibc from source. I believe that the glibc
>headers are "derived" from the kernel against which it is built.
That way everybody builds a different glibc. Does that strike you as a
good idea? glibc should be shipped with standard include files.
-
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 11:38 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-02-03 2:49 Fix for include/linux/fs.h in 2.4.0 kernels Frédéric L. W. Meunier
2001-02-03 3:03 ` Brian May
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 [this message]
-- 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=15031.981200299@ocs3.ocs-net \
--to=kaos@ocs.com.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