From: Peter Korsgaard <jacmet@uclibc.org>
To: buildroot@busybox.net
Subject: [Buildroot] [git commit] ipset: ensure target kernel headers are used
Date: Mon, 25 Jul 2011 09:55:04 +0200 [thread overview]
Message-ID: <87hb6au753.fsf@macbook.be.48ers.dk> (raw)
In-Reply-To: <20110725094903.35873b1a@skate> (Thomas Petazzoni's message of "Mon, 25 Jul 2011 09:49:03 +0200")
>>>>> "Thomas" == Thomas Petazzoni <thomas.petazzoni@free-electrons.com> writes:
Thomas> Le Fri, 22 Jul 2011 13:51:45 +0200,
Thomas> Peter Korsgaard <jacmet@sunsite.dk> a ?crit :
>> diff --git a/package/ipset/ipset.mk b/package/ipset/ipset.mk
>> index 9d901fc..700d2bc 100644
>> --- a/package/ipset/ipset.mk
>> +++ b/package/ipset/ipset.mk
>> @@ -9,5 +9,6 @@ IPSET_SOURCE = ipset-$(IPSET_VERSION).tar.bz2
>> IPSET_SITE = http://ipset.netfilter.org
>> IPSET_AUTORECONF = YES
>> IPSET_DEPENDENCIES = libmnl host-pkg-config
>> +IPSET_CONF_OPT = --with-ksource=$(LINUX_HEADERS_DIR)
Thomas> I am sorry, but LINUX_HEADERS_DIR is only defined when the internal
Thomas> toolchain backend is used, so I guess this is broken for external
Thomas> toolchain or ct-ng toolchain builds.
Thomas> bridge-utils, busybox and iptables are already using LINUX_HEADERS_DIR,
Thomas> but I guess this needs some work as well.
Ah yes, what should we do for external toolchains then - point
LINUX_HEADERS_DIR at $(STAGING_DIR)/usr/include/linux?
--
Bye, Peter Korsgaard
next prev parent reply other threads:[~2011-07-25 7:55 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-07-22 11:51 [Buildroot] [git commit] ipset: ensure target kernel headers are used Peter Korsgaard
2011-07-25 7:49 ` Thomas Petazzoni
2011-07-25 7:55 ` Peter Korsgaard [this message]
2011-08-17 19:32 ` Gustavo Zacarias
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=87hb6au753.fsf@macbook.be.48ers.dk \
--to=jacmet@uclibc.org \
--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