From: Stefan Schmidt <stefan@datenfreihafen.org>
To: openembedded-devel@lists.openembedded.org
Subject: Re: libnl vs. libnl2 madness
Date: Thu, 3 Feb 2011 13:42:44 +0100 [thread overview]
Message-ID: <20110203124244.GJ4580@excalibur.local> (raw)
In-Reply-To: <20110203101242.GF3265@jama>
Hello.
On Thu, 2011-02-03 at 11:12, Martin Jansa wrote:
> On Thu, Feb 03, 2011 at 10:54:08AM +0100, Thomas Zimmermann wrote:
> > On Thursday 03 February 2011 10:32:53 Stefan Schmidt wrote:
> >
> > At that time there was just one recipe depending on libnl2 and that was FSO2.
> > I think one month ago JaMa has build the first SHR image without libnl(1),
>
> yes after couple of changes
> http://git.openembedded.org/cgit.cgi/openembedded/log/?h=org.openembedded.dev&qt=grep&q=libnl
>
> > until then it was impossible because of some important parts. I'm not sure but
> > i think the main blocker was bluez4 (Can't check now).
>
> Yes older bluez4 with nl plugin (which was removed later).
Good, so bluez is of the table.
> and:
> http://gitorious.org/~jama/angstrom/jama-shr-experimental/commit/70b13d30b335b8fd67116d3bc0834382a77bc319
> 81 ANGSTROM_BLACKLIST_pn-bmon = "bmon depends on libnl we want libnl2"
> 82 ANGSTROM_BLACKLIST_pn-crda = "crda depends on libnl we want libnl2"
No idea about these two.
> 83 ANGSTROM_BLACKLIST_pn-hostap-daemon = "hostap-daemon depends on libnl we want libnl2"
Should be fine to build with CONFIG_LIBNL20 set. Its the same codebase as
wpa-supplicant.
> 84 ANGSTROM_BLACKLIST_pn-ibrdtn = "ibrdtn depends on libnl we want libnl2"
Maybe I should get a stab at this as I'm the main user of it in OE. :)
> 85 ANGSTROM_BLACKLIST_pn-iw = "iw depends on libnl we want libnl2"
Need to check latest version for libnl2 support. Should not be to hard to change
it.
> 86 ANGSTROM_BLACKLIST_pn-lowpan-tools = "lowpan-tools depends on libnl we want libnl2"
When I'm going to poke ibrdtn I could take a look here as well. Maybe Dmitry .
> 87 ANGSTROM_BLACKLIST_pn-networkmanager = "networkmanager depends on libnl we want libnl2"
> 88 ANGSTROM_BLACKLIST_pn-networkmanager-openvpn = "networkmanager-openvpn depends on libnl we want libnl2"
Those two have a pretty big code base and I'm not going to dive into it (again).
> 89 ANGSTROM_BLACKLIST_pn-pstree = "pstree depends on libnl we want libnl2"
> 90 ANGSTROM_BLACKLIST_pn-rfkill = "rfkill depends on libnl we want libnl2"
Need to check latest version for libnl2 support. Should not be to hard to change
it.
> I didn't check if those can be built with libnl2 or if they work properly with libnl2.
As you can see I would be willing to work on some of these. Personally I would
aim for getting the recipes over to libnl2 and the kill libnl1 for good in OE.
> But be aware that we had enough issues in runtime (build passes ok) caused by libnl1 built in same sysroot
> as libnl2 (that's why I had to blacklist libnl2 in SHR).
Thats one more reason to get rid of the old version. :)
regards
Stefan Schmidt
next prev parent reply other threads:[~2011-02-03 12:43 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-02-03 9:32 libnl vs. libnl2 madness Stefan Schmidt
2011-02-03 9:54 ` Thomas Zimmermann
2011-02-03 10:12 ` Martin Jansa
2011-02-03 12:42 ` Stefan Schmidt [this message]
2011-02-03 14:08 ` Stefan Schmidt
2011-02-09 10:00 ` Stefan Schmidt
2011-02-09 10:20 ` Koen Kooi
2011-02-09 10:46 ` Stefan Schmidt
2011-02-11 10:15 ` Koen Kooi
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=20110203124244.GJ4580@excalibur.local \
--to=stefan@datenfreihafen.org \
--cc=openembedded-devel@lists.openembedded.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.