From: Gustavo Zacarias <gustavo@zacarias.com.ar>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH] libnl: bump to version 2.0
Date: Thu, 28 Apr 2011 09:17:41 -0300 [thread overview]
Message-ID: <4DB95AE5.7050805@zacarias.com.ar> (raw)
In-Reply-To: <4DB91691.4030308@visionsystems.de>
On 04/28/11 04:26, Yegor Yefremov wrote:
>>>> I see there's already a libnl-3.0, is there any reason why you stick
>>>> with 2.0?
>>> You're right. I first tried 3.0 and it failed by some package, so I took 2.0 and didn't verify what was wrong. But I just checked the 3.0 version and it works with all 5 packages:
>>>
>>> wpa_supplicant
>>> iw
>>> hostapd
>>> kismet
>>> ti-utils
>> iw fails to build with 3.0
>> kismet builds without libnl support with 3.0
>> hostapd & wpa_supplicant build ok with your patches.
>> Did you make clean completely before trying? Otherwise you'll get stale
>> files in staging.
>> Regards
>
> You're right, that were stale files in staging. I made a patch for iw and will send it also upstream.
>
> I'll look into kismet issue or has it gone with the latest version?
>
> Best regards,
> Yegor
Latest kismet doesn't handle libnl-3.0 yet and i've just received your
patch for it.
I'll give the whole set a run and Ack once i'm done, we probably want
libnl-3.0 while we're at it like Peter said. It's supposed to be the
first API/ABI-stable version.
Regards.
next prev parent reply other threads:[~2011-04-28 12:17 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-04-27 8:23 [Buildroot] [PATCH] libnl: bump to version 2.0 Yegor Yefremov
2011-04-27 11:26 ` Peter Korsgaard
2011-04-27 12:51 ` Yegor Yefremov
2011-04-27 12:56 ` Peter Korsgaard
2011-04-27 12:58 ` Yegor Yefremov
2011-04-27 13:41 ` Gustavo Zacarias
2011-04-28 7:26 ` Yegor Yefremov
2011-04-28 12:17 ` Gustavo Zacarias [this message]
2011-04-28 12:26 ` Yegor Yefremov
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=4DB95AE5.7050805@zacarias.com.ar \
--to=gustavo@zacarias.com.ar \
--cc=buildroot@busybox.net \
/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