From: Bob Barry <bobb@absamail.co.za>
To: linux-hotplug@vger.kernel.org
Subject: Re: latest klibc for udev
Date: Mon, 20 Sep 2004 07:23:19 +0000 [thread overview]
Message-ID: <200409200923.19643.bobb@absamail.co.za> (raw)
In-Reply-To: <20040917191134.GA28506@vrfy.org>
Kevin -
On Monday 20 September 2004 05:10, you wrote:
> > Does your klibc-0.177 have "ash"? If not, perhaps it's a better
> > fit for udev. Either way, the udev package needs to provide or
> > use klibc-0.17x to support the 2.6.9-rc2 kernel.
>
> That's only true if you're building against raw kernel headers, right?
What's "that"? Compilation failure of ash?
> If you build against the latest linux-libc-headers, it should work fine.
Can you refer me to an explanation of this dependency?
Can you give me a URL for appropriate headers?
Thanks,
Bob Barry
-------------------------------------------------------
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 7:23 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 [this message]
2004-09-20 14:51 ` Kevin P. Fleming
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=200409200923.19643.bobb@absamail.co.za \
--to=bobb@absamail.co.za \
--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).