2009-07-01 16:50:49

by Jon Loeliger

[permalink] [raw]
Subject: Compiling wpa_supplicant?

Folks,

Has hostapd's wpa_supplicant code been brought up to a
consistent standard with the current libnl? In particular,
I'm trying to compile wpa_supplicant to use driver_nl80211,
but it is failing due to the use of the obsolete 'struct nl_handle'
in src/driver/driver_nl80211.c, line 131 or so.

I am using:
$ git remote -v
origin git://w1.fi/srv/git/hostap-06.git
$ git rev-parse HEAD
fa4e296f542af01da135d997358d6d45a32dd59e
and:
$ git remote -v
origin git://git.kernel.org/pub/scm/libs/netlink/libnl.git
$ git rev-parse HEAD
ef8ba32e0ca7ac7bbbaf87f6fd7b197af18aed25

In libnl, I see this commit:

commit b624b9ed936f4c23bc4f30d8dce34da49775dd15
Author: Thomas Graf <[email protected]>
Date: Wed Dec 10 18:02:25 2008 +0100

Remove obsoleted struct nl_handle definition

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?

Thanks,
jdl




2009-07-01 18:34:43

by Johannes Berg

[permalink] [raw]
Subject: Re: Compiling wpa_supplicant?

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 :) Otherwise, you can rip the compat code out off iw and stick it
into wpa_supplicant/hostapd.

johannes


Attachments:
signature.asc (801.00 B)
This is a digitally signed message part

2009-07-01 20:57:24

by Jon Loeliger

[permalink] [raw]
Subject: Re: Compiling wpa_supplicant?

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