public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Kay Sievers <kay.sievers@vrfy.org>
To: Greg KH <greg@kroah.com>
Cc: Tomasz K?oczko <kloczek@rudy.mif.pg.gda.pl>,
	Hotplug Devel <linux-hotplug-devel@lists.sourceforge.net>,
	linux-kernel@vger.kernel.org
Subject: Re: [ANNOUNCE] udev 048 release
Date: Wed, 08 Dec 2004 23:15:21 +0100	[thread overview]
Message-ID: <1102544121.5987.130.camel@localhost.localdomain> (raw)
In-Reply-To: <20041208220500.GA19187@kroah.com>

On Wed, 2004-12-08 at 14:05 -0800, Greg KH wrote:
> On Wed, Dec 08, 2004 at 10:56:27PM +0100, Tomasz K?oczko wrote:

> > Also after aplying this patches libsysfs/ subdirectory can be removed from 
> > udev source tree.
> 
> Will it still properly build with klibc?

This will not work at the moment, as we fake the getmntent() call in
libsysfs at compile time for the klibc build.

> I'm sure those who package up rpms of udev have dealt with this properly
> somehow.  For the rest of the world, I'd prefer to keep the current way.

I agree. It's much easier to tweak the udev sources to use a dynamic
linked libsysfs than the other way around.

Thanks,
Kay


  reply	other threads:[~2004-12-08 22:15 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-12-08 18:58 [ANNOUNCE] udev 047 release Greg KH
2004-12-08 19:28 ` Greg KH
2004-12-08 19:46   ` [ANNOUNCE] udev 048 release Greg KH
2004-12-08 21:56     ` Tomasz Kłoczko
2004-12-08 22:05       ` Greg KH
2004-12-08 22:15         ` Kay Sievers [this message]
2004-12-08 23:25         ` Tomasz Kłoczko
2004-12-09 21:47     ` Andrew Walrond
2004-12-09 23:25       ` Greg KH
2004-12-10  8:46         ` Andrew Walrond
2004-12-11 16:44 ` [ANNOUNCE] udev 047 release [u] Martin Schlemmer [c]

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=1102544121.5987.130.camel@localhost.localdomain \
    --to=kay.sievers@vrfy.org \
    --cc=greg@kroah.com \
    --cc=kloczek@rudy.mif.pg.gda.pl \
    --cc=linux-hotplug-devel@lists.sourceforge.net \
    --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