linux-hotplug.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Robby Workman <rw@rlworkman.net>
To: linux-hotplug@vger.kernel.org
Subject: Re: [ANNOUNCE] udev 152 release
Date: Wed, 21 Apr 2010 04:19:20 +0000	[thread overview]
Message-ID: <20100420231920.368ddc75@liberty.rlwhome.lan> (raw)
In-Reply-To: <1271750116.2583.12.camel@yio.site>

[-- Attachment #1: Type: text/plain, Size: 1215 bytes --]

On Tue, 20 Apr 2010 22:46:19 -0500
Robby Workman <rw@rlworkman.net> wrote:

> On Tue, 20 Apr 2010 09:55:16 +0200
> Kay Sievers <kay.sievers@vrfy.org> wrote:
> 
> > The tarball can be found here:
> >  ftp://ftp.kernel.org/pub/linux/utils/kernel/hotplug/
> > ... 
> > udev 152
> 
> 
> I rambled around the IRC channel a bit before I figured out
> what the heck was wrong, and I'm only posting here because I 
> suspect someone else might run across this and be equally 
> baffled trying to find what is later an obvious thing :-)
> 
> Somehow the configure and configure.ac inside the udev-152 source
> tarball has this:
> 
>   ./configure:  with_firmware_path="/lib/fimware/updates:/lib/fimware"
>   ./configure.ac:
> [with_firmware_path="/lib/fimware/updates:/lib/fimware"]
> 
> I don't see that string in the git repo, so I guess there was
> a typo when running autogen.sh on your end of things.  


Ooh, I take that back.  I'm blind.

configure.ac in git has the bad string.  I suspect it's easier
to just fix yourself as opposed to applying a patch, but just
in case:
http://git.rlworkman.net/gitweb.cgi?p=udev.git;a=commitdiff;h=24e229e4c0bbbb0c882f70cab40be9d03c67be91

-RW

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 198 bytes --]

  parent reply	other threads:[~2010-04-21  4:19 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-04-20  7:55 [ANNOUNCE] udev 152 release Kay Sievers
2010-04-21  3:46 ` Robby Workman
2010-04-21  4:19 ` Robby Workman [this message]
2010-10-03  6:55 ` Andreas Metzler
2010-10-03 11:17 ` Kay Sievers
2010-10-03 11:59 ` Andreas Metzler

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=20100420231920.368ddc75@liberty.rlwhome.lan \
    --to=rw@rlworkman.net \
    --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).