On Sun, 2012-01-08 at 16:30 +0000, Ken Moffat wrote:
> On Sun, Jan 08, 2012 at 07:12:04AM -0700, [email protected] wrote:
> >  
> > +<!ENTITY libnl-version "2.0">
> > +<!ENTITY libnl-size "650 KB">
> > +<!ENTITY libnl-url 
> > "http://www.infradead.org/~tgr/libnl/files/libnl-&libnl-version;.tar.gz";>
> > +<!ENTITY libnl-md5 "6aaf1e9802a17a7d702bb0638044ffa7">
> > +<!ENTITY libnl-home "http://www.infradead.org/~tgr/libnl/";>
> > +<!ENTITY libnl-ch6-du "22.0 MB">
> > +<!ENTITY libnl-ch6-sbu "0.1 SBU">
> 
>  Ouch!  I was watching this with interest (I need libnl to
> build-test NetworkManager for gnome-3: havn't quite got there yet),
> and when you mentioned a newer version I downloaded libnl-3.2.3.
> 
>  Perhaps 2.0 is indeed better (it appears not to have created static
> libs for you, which is nice - I had to pass --enable-static=no). Or
> perhaps the altered structure in 3.2, plus the absence of
> pkg-config, will make things in LFS too awkward.

3.2 had the incompatible-with-iproute2 structure, 3.1/3.0 wanted Python
and couldn't easily be convinced to not use it, so I just went back to
2.0 which didn't complain about anything!

If you run into issues with 2.0, just let me know.  libnl-git apparently
removes the mandatory Python dependency, and the sed to make iproute2
find the new header location should be relatively trivial, so I'm happy
to work on making LFS use a BLFS-compatible libnl version if it isn't
already.

Cheers,

Matt.

-- 
http://linuxfromscratch.org/mailman/listinfo/lfs-book
FAQ: http://www.linuxfromscratch.org/lfs/faq.html
Unsubscribe: See the above information page

Reply via email to