All of lore.kernel.org
 help / color / mirror / Atom feed
From: Kay Sievers <kay.sievers@vrfy.org>
To: linux-hotplug@vger.kernel.org
Subject: Re: udev-067 and 2.6.12?
Date: Wed, 17 Aug 2005 15:10:29 +0000	[thread overview]
Message-ID: <20050817151029.GA19505@vrfy.org> (raw)
In-Reply-To: <200508162349.01610.s0348365@sms.ed.ac.uk>

On Wed, Aug 17, 2005 at 03:52:26PM +0100, Alistair John Strachan wrote:
> On Wednesday 17 August 2005 13:35, Kay Sievers wrote:
> > On Wed, Aug 17, 2005 at 09:26:08AM +0100, Alistair John Strachan wrote:
> [snip]
> > > No. I typed "make" and edited nothing. I'm sceptical that this is a
> > > problem with "only" my configuration, since I've compiled literally
> > > hundreds of packages with a problem, and run_directory/ is the only thing
> > > I've ever seen not link bizarrely. I think the problem is that it's a
> > > mistake to use ld explicitly to link in the case where I want to also
> > > link in libc, and not use klibc. Many of the missing symbols were from
> > > libc.
> >
> > You may need to run make from the top-level directory of of the udev
> > tree with "make EXTRAS=extras/run_directory"?
> 
> [alistair] 15:34 [~/udev-067] make extras/run_directory

Seems you didn't you try what I wrote in the last mail:
  make EXTRAS=extras/run_directory

Kay


-------------------------------------------------------
SF.Net email is Sponsored by the Better Software Conference & EXPO
September 19-22, 2005 * San Francisco, CA * Development Lifecycle Practices
Agile & Plan-Driven Development * Managing Projects & Teams * Testing & QA
Security * Process Improvement & Measurement * http://www.sqe.com/bsce5sf
_______________________________________________
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

  parent reply	other threads:[~2005-08-17 15:10 UTC|newest]

Thread overview: 23+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-08-16 22:49 udev-067 and 2.6.12? Alistair John Strachan
2005-08-16 23:00 ` David Brown
2005-08-16 23:26 ` Alistair John Strachan
2005-08-16 23:31 ` David Brown
2005-08-16 23:55 ` Kay Sievers
2005-08-17  8:09 ` Arioch
2005-08-17  8:26 ` Alistair John Strachan
2005-08-17 12:35 ` Kay Sievers
2005-08-17 14:52 ` Alistair John Strachan
2005-08-17 15:10 ` Kay Sievers [this message]
2005-08-17 23:48 ` Greg KH
2005-08-18 15:27 ` David Brown
2005-08-18 15:38 ` Greg KH
2005-08-18 15:53 ` David Brown
2005-08-18 16:32 ` Alistair John Strachan
2005-08-18 16:56 ` Greg KH
2005-08-18 17:19 ` Alistair John Strachan
  -- strict thread matches above, loose matches on Subject: below --
2005-08-16 22:02 Alistair John Strachan
2005-08-16 22:05 ` Greg KH
2005-08-16 22:12   ` Alistair John Strachan
2005-08-16 22:14     ` Greg KH
2005-08-16 23:09       ` Kay Sievers
2005-08-16 23:33         ` Alistair John Strachan

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=20050817151029.GA19505@vrfy.org \
    --to=kay.sievers@vrfy.org \
    --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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.