From: "Kevin P. Fleming" <kpfleming@backtobasicsmgmt.com>
To: linux-hotplug@vger.kernel.org
Subject: Re: latest klibc for udev
Date: Mon, 20 Sep 2004 14:51:29 +0000 [thread overview]
Message-ID: <414EEE71.2020507@backtobasicsmgmt.com> (raw)
In-Reply-To: <20040917191134.GA28506@vrfy.org>
Bob Barry wrote:
> What's "that"? Compilation failure of ash?
No, you said that the udev package needs to "provide klibc-0.17x" the
support the 2.6.9-rc2 kernel, and I was disagreeing. That should only be
necessary if you are allowing udev/klibc to build against raw kernel
headers, instead of sanitized headers. I run udev-032 against 2.6.9-rc2
kernels here and have not had any trouble.
> Can you refer me to an explanation of this dependency?
Sorry, I don't know of one. There are many, many threads on the
linux-kernel mailing list archives that talk about this issue, though.
> Can you give me a URL for appropriate headers?
Google for "linux-libc-headers", it's the first link listed.
-------------------------------------------------------
This SF.Net email is sponsored by: YOU BE THE JUDGE. Be one of 170
Project Admins to receive an Apple iPod Mini FREE for your judgement on
who ports your project to Linux PPC the best. Sponsored by IBM.
Deadline: Sept. 24. Go here: http://sf.net/ppc_contest.php
_______________________________________________
Linux-hotplug-devel mailing list http://linux-hotplug.sourceforge.net
Linux-hotplug-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/linux-hotplug-devel
next prev parent reply other threads:[~2004-09-20 14:51 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-09-17 19:11 latest klibc for udev Kay Sievers
2004-09-18 0:31 ` [klibc] " H. Peter Anvin
2004-09-18 21:44 ` Bob Barry
2004-09-19 20:18 ` Kevin P. Fleming
2004-09-20 7:23 ` Bob Barry
2004-09-20 14:51 ` Kevin P. Fleming [this message]
2004-09-24 12:48 ` Bob Barry
2004-09-29 14:31 ` [klibc] " Jürg Billeter
2004-09-29 18:25 ` H. Peter Anvin
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=414EEE71.2020507@backtobasicsmgmt.com \
--to=kpfleming@backtobasicsmgmt.com \
--cc=linux-hotplug@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;
as well as URLs for NNTP newsgroup(s).