From: Mike Frysinger <vapier@gentoo.org>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH 1/4] libpcap: update static handling
Date: Mon, 24 Jan 2011 16:46:23 -0500 [thread overview]
Message-ID: <201101241646.23935.vapier@gentoo.org> (raw)
In-Reply-To: <87pqrmtgju.fsf@macbook.be.48ers.dk>
On Monday, January 24, 2011 11:25:25 Peter Korsgaard wrote:
> >>>>> "Thomas" == Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
writes:
> Thomas> Hello,
> Thomas> Completely unrelated to Mike's change, but still spotted while
> looking Thomas> at the patch context:
>
> Thomas> On Wed, 19 Jan 2011 22:10:29 -0500
>
> Thomas> Mike Frysinger <vapier@gentoo.org> wrote:
> >> LIBPCAP_CONF_ENV:=ac_cv_linux_vers=$(firstword $(subst
> >> .,$(space),$(firstword $(call qstrip,$(BR2_DEFAULT_KERNEL_HEADERS)))))
> >> \
>
> Thomas> Both libpcap and tcpdump use this and I never noticed, but this
> Thomas> is completely broken with external toolchains and the
> Thomas> Crosstool-NG backend, since BR2_DEFAULT_KERNEL_HEADERS is only
> Thomas> set with internal toolchains.
>
> Thomas> I haven't thought of what the right fix would be, but it's
> definitely Thomas> not that one.
>
> True. The question is why they need this info? Perhaps we can just lie
> and simply say 2.6.x?
ive noticed this in all my builds, but ive just ignored it. it isnt a matter
of picking "linux 2.6" over "linux 2.4". you simply need to pick linux-2.x
over linux-1.x or linux-0.x. we've long used this in Gentoo/uclinux-dist:
export ac_cv_linux_vers=2
-mike
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 836 bytes
Desc: This is a digitally signed message part.
URL: <http://lists.busybox.net/pipermail/buildroot/attachments/20110124/1881ed86/attachment.asc>
prev parent reply other threads:[~2011-01-24 21:46 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-01-20 3:10 [Buildroot] Pull request buildroot.git (vapier branch) Mike Frysinger
2011-01-20 3:10 ` [Buildroot] [PATCH 1/4] libpcap: update static handling Mike Frysinger
2011-01-20 3:10 ` [Buildroot] [PATCH 2/4] debugging: do not require no stripping Mike Frysinger
2011-01-20 3:10 ` [Buildroot] [PATCH 3/4] initial support for Blackfin processors Mike Frysinger
2011-01-20 3:10 ` [Buildroot] [PATCH 4/4] gdb: add support for Blackfin gdbserver Mike Frysinger
2011-01-23 10:17 ` [Buildroot] [PATCH 1/4] libpcap: update static handling Peter Korsgaard
2011-01-23 21:07 ` Mike Frysinger
2011-01-24 16:16 ` Thomas Petazzoni
2011-01-24 16:27 ` Peter Korsgaard
2011-01-24 21:48 ` Mike Frysinger
2011-01-24 21:59 ` Peter Korsgaard
2011-01-25 8:36 ` Thomas Petazzoni
2011-01-24 16:11 ` Thomas Petazzoni
2011-01-24 16:25 ` Peter Korsgaard
2011-01-24 21:46 ` Mike Frysinger [this message]
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=201101241646.23935.vapier@gentoo.org \
--to=vapier@gentoo.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