From: Jon Loeliger <jdl@bigfootnetworks.com>
To: Johannes Berg <johannes@sipsolutions.net>
Cc: "linux-wireless@vger.kernel.org" <linux-wireless@vger.kernel.org>
Subject: Re: Compiling wpa_supplicant?
Date: Wed, 01 Jul 2009 15:57:28 -0500 [thread overview]
Message-ID: <1246481848.11632.33.camel@jdl-desktop> (raw)
In-Reply-To: <1246473271.8154.5.camel@johannes.local>
On Wed, 2009-07-01 at 20:34 +0200, Johannes Berg wrote:
> On Wed, 2009-07-01 at 11:50 -0500, Jon Loeliger wrote:
>
> > Is there a version of hostapd/wpa_suppliant that is more
> > up-to-date WRT libnl-2.0? Or should I just use the wext
> > driver for now?
>
> I would suggest you compile against a released version of libnl, namely
> 1.1 :)
I was afraid someone would say something like that... :-)
And since that seems to be effort in the wrong direction,
I was even more afraid someone would say something like:
> Otherwise, you can rip the compat code out off iw and stick it
> into wpa_supplicant/hostapd.
So I did something like that. Patch to follow.
> johannes
Thanks,
jdl
prev parent reply other threads:[~2009-07-01 20:57 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-07-01 16:50 Compiling wpa_supplicant? Jon Loeliger
2009-07-01 18:34 ` Johannes Berg
2009-07-01 20:57 ` Jon Loeliger [this message]
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=1246481848.11632.33.camel@jdl-desktop \
--to=jdl@bigfootnetworks.com \
--cc=johannes@sipsolutions.net \
--cc=linux-wireless@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).