From: Daniel Mack <zonque@gmail.com> Date: 2011-11-29 16:27:13
This newer version splits the library code into libnl, libnl-route,
libnl-genl and libnl-nf, each individually selectable via pkgconfig.
Signed-off-by: Daniel Mack <zonque@gmail.com>
---
package/libnl/libnl.mk | 2 +-
1 files changed, 1 insertions(+), 1 deletions(-)
From: Daniel Mack <zonque@gmail.com> Date: 2011-11-29 18:16:59
The CFLAGS have to be augmented for the include dir and a small patch
will make the binary link to libnl-3 and libnl-genl-3 instead of libnl
and libnl-gen.
Signed-off-by: Daniel Mack <zonque@gmail.com>
---
package/hostapd/hostapd-0.7.3-libnl3.patch | 15 +++++++++++++++
package/hostapd/hostapd.mk | 1 +
2 files changed, 16 insertions(+), 0 deletions(-)
create mode 100644 package/hostapd/hostapd-0.7.3-libnl3.patch
From: Daniel Mack <zonque@gmail.com> Date: 2011-11-29 18:24:58
The CFLAGS have to be augmented for the include dir and a small patch
will make the binary link to libnl-3 and libnl-genl-3 instead of libnl
and libnl-gen.
Signed-off-by: Daniel Mack <zonque@gmail.com>
---
.../wpa_supplicant-0.7.3-libnl-3.patch | 15 +++++++++++++++
package/wpa_supplicant/wpa_supplicant.mk | 2 +-
2 files changed, 16 insertions(+), 1 deletions(-)
create mode 100644 package/wpa_supplicant/wpa_supplicant-0.7.3-libnl-3.patch
From: Daniel Mack <zonque@gmail.com> Date: 2011-11-29 18:27:33
On 11/29/2011 07:16 PM, Daniel Mack wrote:
The CFLAGS have to be augmented for the include dir and a small patch
will make the binary link to libnl-3 and libnl-genl-3 instead of libnl
and libnl-gen.
There might be more patches like this necessary, and unfortunately, the
approach is a nasty hack which don't like either. But don't see any
cleaner way to make this work.
The root cause for touching all this is that I need libnl-3 with
libnl-route3 support for another package I'm working on.
Daniel
On Tue, Nov 29, 2011 at 5:27 PM, Daniel Mack [off-list ref] wrote:
quoted hunk
This newer version splits the library code into libnl, libnl-route,
libnl-genl and libnl-nf, each individually selectable via pkgconfig.
Signed-off-by: Daniel Mack <zonque@gmail.com>
---
?package/libnl/libnl.mk | ? ?2 +-
?1 files changed, 1 insertions(+), 1 deletions(-)
The only package I know that is prepared for libnl 3.2.3 is iw (latest
git version). Other packages like wpa_supplicant, hostapd, kismet are
not prepared for the new version of libnl.
Yegor
On Tue, Nov 29, 2011 at 10:26 PM, Yegor Yefremov
[off-list ref] wrote:
On Tue, Nov 29, 2011 at 5:27 PM, Daniel Mack [off-list ref] wrote:
quoted
This newer version splits the library code into libnl, libnl-route,
libnl-genl and libnl-nf, each individually selectable via pkgconfig.
Signed-off-by: Daniel Mack <zonque@gmail.com>
---
?package/libnl/libnl.mk | ? ?2 +-
?1 files changed, 1 insertions(+), 1 deletions(-)
The only package I know that is prepared for libnl 3.2.3 is iw (latest
git version). Other packages like wpa_supplicant, hostapd, kismet are
not prepared for the new version of libnl.
I've seen your patches for wpa_supplicant, hostapd. So kismet and iw are left.
Yegor
From: Daniel Mack <zonque@gmail.com> Date: 2011-11-30 15:05:59
The CFLAGS have to be augmented for the include dir and the patch
needs to be tweaked to make the binary link to libnl-3 instead of
libnl-gen.
Signed-off-by: Daniel Mack <zonque@gmail.com>
---
package/iw/iw-libnl-30-support.patch | 2 +-
package/iw/iw.mk | 2 +-
2 files changed, 2 insertions(+), 2 deletions(-)
From: Daniel Mack <zonque@gmail.com> Date: 2011-11-30 15:06:00
The CFLAGS have to be augmented, so configure finds the correct include
dir, and the patch needs to be tweaked to make the binary link to
libnl-3 instead of libnl-gen.
Signed-off-by: Daniel Mack <zonque@gmail.com>
---
package/kismet/kismet-libnl-30-support.patch | 10 +++++++---
package/kismet/kismet.mk | 1 +
2 files changed, 8 insertions(+), 3 deletions(-)
From: Daniel Mack <zonque@gmail.com> Date: 2011-11-30 15:06:53
On 11/29/2011 10:28 PM, Yegor Yefremov wrote:
On Tue, Nov 29, 2011 at 10:26 PM, Yegor Yefremov
[off-list ref] wrote:
quoted
On Tue, Nov 29, 2011 at 5:27 PM, Daniel Mack [off-list ref] wrote:
quoted
This newer version splits the library code into libnl, libnl-route,
libnl-genl and libnl-nf, each individually selectable via pkgconfig.
Signed-off-by: Daniel Mack <zonque@gmail.com>
---
package/libnl/libnl.mk | 2 +-
1 files changed, 1 insertions(+), 1 deletions(-)
The only package I know that is prepared for libnl 3.2.3 is iw (latest
git version). Other packages like wpa_supplicant, hostapd, kismet are
not prepared for the new version of libnl.
I've seen your patches for wpa_supplicant, hostapd. So kismet and iw are left.
Ok, I've sent patches for these, too. Thanks for the heads-up.
Daniel
On Wed, Nov 30, 2011 at 4:05 PM, Daniel Mack [off-list ref] wrote:
quoted hunk
The CFLAGS have to be augmented for the include dir and the patch
needs to be tweaked to make the binary link to libnl-3 instead of
libnl-gen.
Signed-off-by: Daniel Mack <zonque@gmail.com>
---
?package/iw/iw-libnl-30-support.patch | ? ?2 +-
?package/iw/iw.mk ? ? ? ? ? ? ? ? ? ? | ? ?2 +-
?2 files changed, 2 insertions(+), 2 deletions(-)
From: Daniel Mack <zonque@gmail.com> Date: 2011-11-30 16:31:40
Hi Yegor,
On 11/30/2011 04:54 PM, Yegor Yefremov wrote:
On Wed, Nov 30, 2011 at 4:05 PM, Daniel Mack [off-list ref] wrote:
quoted
The CFLAGS have to be augmented for the include dir and the patch
needs to be tweaked to make the binary link to libnl-3 instead of
libnl-gen.
Signed-off-by: Daniel Mack <zonque@gmail.com>
---
package/iw/iw-libnl-30-support.patch | 2 +-
package/iw/iw.mk | 2 +-
2 files changed, 2 insertions(+), 2 deletions(-)
this file has gone in next. Please rebase your patches on the next
I can do this. I wasn't even aware of this branch, and part of the
reason is that it doesn't show up on the cgit web interface
(http://git.buildroot.net/buildroot) when there's no trailing slash in
the URI, which is unfortunately the location the website
(http://buildroot.uclibc.org/git.html) points visitors to. You can click
on "refs" and back on "summary" which will add the "/" suffix, and then
cgit will show the existance of the "next" branch. Very odd.
Not sure whether I follow you here. Do you suggest writing package
definitions for sources that are not released yet officially? If that is
the case, what is the reason?
Also, I fail to see how the commit you pointed me to is related to the
changed location of libnl-3. Is this not something that should be
addressed independently?
All my other libnl-related patches still seem to apply fine on the -next
branch, though.
Daniel
From: Michael S. Zick <hidden> Date: 2011-11-30 16:36:38
On Wed November 30 2011, Daniel Mack wrote:
I can do this. I wasn't even aware of this branch, and part of the
reason is that it doesn't show up on the cgit web interface
(http://git.buildroot.net/buildroot) when there's no trailing slash in
the URI, which is unfortunately the location the website
(http://buildroot.uclibc.org/git.html) points visitors to. You can click
on "refs" and back on "summary" which will add the "/" suffix, and then
cgit will show the existance of the "next" branch. Very odd.
Confirmed here also.
Just adding the "/" to the URI in the browser bar and hitting "enter"
fixes the display of the "next" branch also.
Mike
From: Michael S. Zick <hidden> Date: 2011-11-30 16:41:13
On Wed November 30 2011, Michael S. Zick wrote:
On Wed November 30 2011, Daniel Mack wrote:
quoted
I can do this. I wasn't even aware of this branch, and part of the
reason is that it doesn't show up on the cgit web interface
(http://git.buildroot.net/buildroot) when there's no trailing slash in
the URI, which is unfortunately the location the website
(http://buildroot.uclibc.org/git.html) points visitors to. You can click
on "refs" and back on "summary" which will add the "/" suffix, and then
cgit will show the existance of the "next" branch. Very odd.
Confirmed here also.
Just adding the "/" to the URI in the browser bar and hitting "enter"
fixes the display of the "next" branch also.
I haven't checked if the command line shown under the "Clone" section
is effected by this strange behavior.
Mike
The CFLAGS have to be augmented for the include dir and the patch
needs to be tweaked to make the binary link to libnl-3 instead of
libnl-gen.
Signed-off-by: Daniel Mack <zonque@gmail.com>
---
?package/iw/iw-libnl-30-support.patch | ? ?2 +-
?package/iw/iw.mk ? ? ? ? ? ? ? ? ? ? | ? ?2 +-
?2 files changed, 2 insertions(+), 2 deletions(-)
this file has gone in next. Please rebase your patches on the next
I can do this. I wasn't even aware of this branch, and part of the
reason is that it doesn't show up on the cgit web interface
(http://git.buildroot.net/buildroot) when there's no trailing slash in
the URI, which is unfortunately the location the website
(http://buildroot.uclibc.org/git.html) points visitors to. You can click
on "refs" and back on "summary" which will add the "/" suffix, and then
cgit will show the existance of the "next" branch. Very odd.
Not sure whether I follow you here. Do you suggest writing package
definitions for sources that are not released yet officially? If that is
the case, what is the reason?
I see here 3 possibilities:
1. replace official release with git one
2. wait for iw 3.3
3. apply related patches (from iw repo) only
the first way is simpler and quicker to implement
Also, I fail to see how the commit you pointed me to is related to the
changed location of libnl-3. Is this not something that should be
addressed independently?
I just pointed to the latest commit. You can choose the one with related changes
All my other libnl-related patches still seem to apply fine on the -next
branch, though.
From: Daniel Mack <zonque@gmail.com> Date: 2011-12-01 11:50:31
On 11/30/2011 10:31 PM, Yegor Yefremov wrote:
Hi Daniel,
quoted
quoted
quoted
The CFLAGS have to be augmented for the include dir and the patch
needs to be tweaked to make the binary link to libnl-3 instead of
libnl-gen.
Signed-off-by: Daniel Mack <zonque@gmail.com>
---
package/iw/iw-libnl-30-support.patch | 2 +-
package/iw/iw.mk | 2 +-
2 files changed, 2 insertions(+), 2 deletions(-)
this file has gone in next. Please rebase your patches on the next
I can do this. I wasn't even aware of this branch, and part of the
reason is that it doesn't show up on the cgit web interface
(http://git.buildroot.net/buildroot) when there's no trailing slash in
the URI, which is unfortunately the location the website
(http://buildroot.uclibc.org/git.html) points visitors to. You can click
on "refs" and back on "summary" which will add the "/" suffix, and then
cgit will show the existance of the "next" branch. Very odd.
Not sure whether I follow you here. Do you suggest writing package
definitions for sources that are not released yet officially? If that is
the case, what is the reason?
I see here 3 possibilities:
1. replace official release with git one
2. wait for iw 3.3
3. apply related patches (from iw repo) only
the first way is simpler and quicker to implement
Ok, fine. I did that and the git version seems to cope well with
nibnl-3. Nice.
quoted
Also, I fail to see how the commit you pointed me to is related to the
changed location of libnl-3. Is this not something that should be
addressed independently?
I just pointed to the latest commit. You can choose the one with related changes
Ok. I rebased all patches and will repost them all. Thanks for your review!
Dainel
From: Peter Korsgaard <hidden> Date: 2011-12-24 15:24:14
quoted
quoted
quoted
quoted
"Daniel" == Daniel Mack [off-list ref] writes:
>> this file has gone in next. Please rebase your patches on the next
Daniel> I can do this. I wasn't even aware of this branch, and part of the
Daniel> reason is that it doesn't show up on the cgit web interface
Daniel> (http://git.buildroot.net/buildroot) when there's no trailing slash in
Daniel> the URI, which is unfortunately the location the website
Daniel> (http://buildroot.uclibc.org/git.html) points visitors to. You can click
Daniel> on "refs" and back on "summary" which will add the "/" suffix, and then
Daniel> cgit will show the existance of the "next" branch. Very odd.
Yes, I know. I've reported it to the osuosl.org guys a while back, and
they are looking into it, but so far without any luck.
I've now fixed the website link.
--
Bye, Peter Korsgaard
From: Stephan Hoffmann <hidden> Date: 2011-12-24 15:56:09
Am 24.12.2011 16:24, schrieb Peter Korsgaard:
quoted
quoted
quoted
quoted
quoted
"Daniel" == Daniel Mack [off-list ref] writes:
>> this file has gone in next. Please rebase your patches on the next
Daniel> I can do this. I wasn't even aware of this branch, and part of the
Daniel> reason is that it doesn't show up on the cgit web interface
Daniel> (http://git.buildroot.net/buildroot) when there's no trailing slash in
Daniel> the URI, which is unfortunately the location the website
Daniel> (http://buildroot.uclibc.org/git.html) points visitors to. You can click
Daniel> on "refs" and back on "summary" which will add the "/" suffix, and then
Daniel> cgit will show the existance of the "next" branch. Very odd.
Yes, I know. I've reported it to the osuosl.org guys a while back, and
they are looking into it, but so far without any luck.
I've now fixed the website link.