Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Daniel Mack <zonque@gmail.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH] hostapd: fix build with new libnl-3
Date: Tue, 29 Nov 2011 19:27:33 +0100	[thread overview]
Message-ID: <4ED52415.8000501@gmail.com> (raw)
In-Reply-To: <1322590619-9814-1-git-send-email-zonque@gmail.com>

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



> 
> 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
> 
> diff --git a/package/hostapd/hostapd-0.7.3-libnl3.patch b/package/hostapd/hostapd-0.7.3-libnl3.patch
> new file mode 100644
> index 0000000..e47da73
> --- /dev/null
> +++ b/package/hostapd/hostapd-0.7.3-libnl3.patch
> @@ -0,0 +1,15 @@
> +--- a/src/drivers/drivers.mak	2011-11-29 19:09:23.889942913 +0100
> ++++ b/src/drivers/drivers.mak	2011-11-29 19:09:40.637381428 +0100
> +@@ -31,10 +31,10 @@
> + NEED_AP_MLME=y
> + NEED_NETLINK=y
> + NEED_LINUX_IOCTL=y
> +-DRV_LIBS += -lnl
> ++DRV_LIBS += -lnl-3
> + 
> + ifdef CONFIG_LIBNL20
> +-DRV_LIBS += -lnl-genl
> ++DRV_LIBS += -lnl-genl-3
> + DRV_CFLAGS += -DCONFIG_LIBNL20
> + endif
> + endif
> diff --git a/package/hostapd/hostapd.mk b/package/hostapd/hostapd.mk
> index 0d6c2c5..53af871 100644
> --- a/package/hostapd/hostapd.mk
> +++ b/package/hostapd/hostapd.mk
> @@ -18,6 +18,7 @@ endif
>  
>  define HOSTAPD_LIBNL_CONFIG
>  	echo "CONFIG_LIBNL20=y" >>$(HOSTAPD_CONFIG)
> +	echo "CFLAGS += -I$(TARGET_DIR)/usr/include/libnl3/" >>$(HOSTAPD_CONFIG)
>  endef
>  
>  define HOSTAPD_CRYPTO_CONFIG

  reply	other threads:[~2011-11-29 18:27 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-11-29 16:27 [Buildroot] [PATCH] libnl: bump to version 3.2.3 Daniel Mack
2011-11-29 18:16 ` [Buildroot] [PATCH] hostapd: fix build with new libnl-3 Daniel Mack
2011-11-29 18:27   ` Daniel Mack [this message]
2011-11-29 18:24 ` [Buildroot] [PATCH] wpa_supplicant: " Daniel Mack
2011-11-29 21:26 ` [Buildroot] [PATCH] libnl: bump to version 3.2.3 Yegor Yefremov
2011-11-29 21:28   ` Yegor Yefremov
2011-11-30 15:05     ` [Buildroot] [PATCH 1/2] iw: fix build with new libnl-3 Daniel Mack
2011-11-30 15:06       ` [Buildroot] [PATCH 2/2] kismet: " Daniel Mack
2011-11-30 15:54       ` [Buildroot] [PATCH 1/2] iw: " Yegor Yefremov
2011-11-30 16:31         ` Daniel Mack
2011-11-30 16:36           ` Michael S. Zick
2011-11-30 16:41             ` Michael S. Zick
2011-11-30 21:31           ` Yegor Yefremov
2011-12-01 11:50             ` Daniel Mack
2011-12-24 15:24           ` Peter Korsgaard
2011-12-24 15:56             ` Stephan Hoffmann
2011-11-30 15:06     ` [Buildroot] [PATCH] libnl: bump to version 3.2.3 Daniel Mack

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=4ED52415.8000501@gmail.com \
    --to=zonque@gmail.com \
    --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