Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Daniel Mack <zonque@gmail.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH v3 4/5] iw: fix build with new libnl-3
Date: Sat, 03 Dec 2011 17:43:36 +0100	[thread overview]
Message-ID: <4EDA51B8.9070909@gmail.com> (raw)
In-Reply-To: <CAGm1_kv1d6catNQ-yVC++Kp+hztQUF1DJq5uFFpoh0B71owmBw@mail.gmail.com>

On 12/03/2011 04:20 PM, Yegor Yefremov wrote:
> On Sat, Dec 3, 2011 at 2:07 PM, Daniel Mack <zonque@gmail.com> wrote:
>> 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(-)
>>
>> diff --git a/package/iw/iw-libnl-30-support.patch b/package/iw/iw-libnl-30-support.patch
>> index 48a179f..02e818c 100644
>> --- a/package/iw/iw-libnl-30-support.patch
>> +++ b/package/iw/iw-libnl-30-support.patch
>> @@ -20,7 +20,7 @@ Index: b/Makefile
>>
>>  +ifeq ($(NL3FOUND),Y)
>>  +CFLAGS += -DCONFIG_LIBNL20
>> -+LIBS += -lnl-genl
>> ++LIBS += -lnl-genl-3
>>  +NLLIBNAME = libnl-3.0
>>  +endif
>>  +
>> diff --git a/package/iw/iw.mk b/package/iw/iw.mk
>> index 9f1d65f..65326b7 100644
>> --- a/package/iw/iw.mk
>> +++ b/package/iw/iw.mk
>> @@ -15,7 +15,7 @@ IW_MAKE_ENV = PKG_CONFIG_PATH="$(STAGING_DIR)/usr/lib/pkgconfig" \
>>
>>  define IW_CONFIGURE_CMDS
>>        echo "CC = $(TARGET_CC)" >$(IW_CONFIG)
>> -       echo "CFLAGS = $(TARGET_CFLAGS)" >>$(IW_CONFIG)
>> +       echo "CFLAGS = $(TARGET_CFLAGS) -I$(STAGING_DIR)/usr/include/libnl3/" >>$(IW_CONFIG)
>>        echo "LDFLAGS = $(TARGET_LDFLAGS)" >>$(IW_CONFIG)
>>  endef
> 
> This patch won't apply. This an old version (v1). 

Sorry, branch confusion on my side. Thanks for noticing.

> What is the reason for v3?

TARGET_DIR vs. STAGING_DIR confusion. I'll post a v4 against -next then.

Thanks,
Daniel

  reply	other threads:[~2011-12-03 16:43 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-12-03 13:07 [Buildroot] [PATCH v3 1/5] libnl: bump to version 3.2.3 Daniel Mack
2011-12-03 13:07 ` [Buildroot] [PATCH v3 2/5] hostapd: fix build with new libnl-3 Daniel Mack
2011-12-03 13:07 ` [Buildroot] [PATCH v3 3/5] wpa_supplicant: " Daniel Mack
2011-12-03 13:07 ` [Buildroot] [PATCH v3 4/5] iw: " Daniel Mack
2011-12-03 15:20   ` Yegor Yefremov
2011-12-03 16:43     ` Daniel Mack [this message]
2011-12-03 17:01       ` Yegor Yefremov
2011-12-03 13:07 ` [Buildroot] [PATCH v3 5/5] kismet: " 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=4EDA51B8.9070909@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