From mboxrd@z Thu Jan 1 00:00:00 1970 From: Robby Workman Date: Wed, 21 Apr 2010 03:46:19 +0000 Subject: Re: [ANNOUNCE] udev 152 release Message-Id: <20100420224619.34ae50cb@liberty.rlwhome.lan> MIME-Version: 1 Content-Type: multipart/mixed; boundary="Sig_/Q+=tPPzSjS0bVqFPvQJ9oKv" List-Id: References: <1271750116.2583.12.camel@yio.site> In-Reply-To: <1271750116.2583.12.camel@yio.site> To: linux-hotplug@vger.kernel.org --Sig_/Q+=tPPzSjS0bVqFPvQJ9oKv Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: quoted-printable On Tue, 20 Apr 2010 09:55:16 +0200 Kay Sievers wrote: > The tarball can be found here: > ftp://ftp.kernel.org/pub/linux/utils/kernel/hotplug/ > ...=20 > 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=20 suspect someone else might run across this and be equally=20 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=3D"/lib/fimware/updates:/lib/fimware" ./configure.ac: [with_firmware_path=3D"/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. =20 -RW --Sig_/Q+=tPPzSjS0bVqFPvQJ9oKv Content-Type: application/pgp-signature; name=signature.asc Content-Disposition: attachment; filename=signature.asc -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.10 (GNU/Linux) iEYEARECAAYFAkvOdQsACgkQvGy9tf6lsvuamgCgsLdl/lCJthhdbN6xgFxZRETs a/sAniCPkBeXDxPW6VaezG/dSGNFwAy7 =3ywv -----END PGP SIGNATURE----- --Sig_/Q+=tPPzSjS0bVqFPvQJ9oKv--