From: Peter Korsgaard <jacmet@uclibc.org>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH 1/1] tcpdump, libpcap: simplify and fix ac_cv_linux_vers
Date: Tue, 25 Jan 2011 16:23:44 +0100 [thread overview]
Message-ID: <8739ohovlr.fsf@macbook.be.48ers.dk> (raw)
In-Reply-To: <397ba8b1856a2465105b4a12e7500e50cc11768c.1295945207.git.thomas.petazzoni@free-electrons.com> (Thomas Petazzoni's message of "Tue, 25 Jan 2011 09:46:58 +0100")
>>>>> "Thomas" == Thomas Petazzoni <thomas.petazzoni@free-electrons.com> writes:
Thomas> For some reason, tcpdump and libpcap need to have some information
Thomas> about the kernel version being used. This information is passed using
Thomas> the ac_cv_linux_vers autoconf variable.
Thomas> However, the current value is determined using
Thomas> BR2_DEFAULT_KERNEL_HEADERS which is only defined when an internal
Thomas> Buildroot toolchain is used. So it would break with an external
Thomas> toolchain or the Crosstool-NG backend.
Thomas> According to Mike Frysinger at
Thomas> http://lists.busybox.net/pipermail/buildroot/2011-January/040861.html,
Thomas> this value is only used to determine if the kernel version is 0.x, 1.x
Thomas> or 2.x, so passing ac_cv_linux_vers=2 is sufficient since Buildroot
Thomas> only supports the 2.6 kernel anyway.
Committed, thanks.
--
Bye, Peter Korsgaard
prev parent reply other threads:[~2011-01-25 15:23 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-01-25 8:46 [Buildroot] [pull request] Pull request for branch fix-ac-cv-linux-vers Thomas Petazzoni
2011-01-25 8:46 ` [Buildroot] [PATCH 1/1] tcpdump, libpcap: simplify and fix ac_cv_linux_vers Thomas Petazzoni
2011-01-25 15:23 ` Peter Korsgaard [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=8739ohovlr.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.