From: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH 1/1] package/zeromq: enable kernel-based feature flags
Date: Sun, 15 Mar 2015 23:28:50 +0100 [thread overview]
Message-ID: <20150315232850.21412e3a@free-electrons.com> (raw)
In-Reply-To: <1423214752-29779-1-git-send-email-lionel.orry@gmail.com>
Dear Lionel Orry,
On Fri, 6 Feb 2015 10:25:52 +0100, Lionel Orry wrote:
> The current configuration system does not check for cached variables for
> these flags, and thus they are always disabled when cross-compiling.
> This patch fixes the configuration system to use cached variables and
> enables them at configuration time.
>
> Signed-off-by: Lionel Orry <lionel.orry@gmail.com>
> ---
> ...e.m4-make-kernel-specific-flags-cacheable.patch | 204 +++++++++++++++++++++
> package/zeromq/zeromq.mk | 10 +
> 2 files changed, 214 insertions(+)
> create mode 100644 package/zeromq/0002-acinclude.m4-make-kernel-specific-flags-cacheable.patch
Thanks for this patch, and sorry for the slow response.
However, I believe it would be a lot better to change the acinclude.m4
tests to not use AC_TRY_RUN, but instead to simply test if TCP_KEEPCNT,
TCP_KEEPIDLE, etc. exist at compile time. If they are defined in the
kernel headers, then you know the kernel supports them, since running a
kernel older than the kernel headers used in the toolchain cannot work.
So, replace AC_TRY_RUN with AC_TRY_LINK or something like that. Or
maybe there's even a simpler autoconf macro to test if a definition
exists or not.
Can you try this instead?
Also, did you submit your patch upstream?
Thanks a lot,
Thomas
--
Thomas Petazzoni, CTO, Free Electrons
Embedded Linux, Kernel and Android engineering
http://free-electrons.com
next prev parent reply other threads:[~2015-03-15 22:28 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-02-06 9:25 [Buildroot] [PATCH 1/1] package/zeromq: enable kernel-based feature flags Lionel Orry
2015-03-15 22:28 ` Thomas Petazzoni [this message]
2015-03-16 6:43 ` Lionel Orry
2015-03-16 8:05 ` Thomas Petazzoni
2015-03-18 22:27 ` Arnout Vandecappelle
2015-04-21 20:47 ` Thomas Petazzoni
2015-04-21 21:48 ` Arnout Vandecappelle
-- strict thread matches above, loose matches on Subject: below --
2015-04-21 13:30 Lionel Orry
2015-04-21 13:33 ` Thomas Petazzoni
2015-04-21 13:39 ` Lionel Orry
2015-04-21 20:19 ` Arnout Vandecappelle
2015-04-22 6:01 ` Lionel Orry
2015-04-22 7:38 ` Thomas Petazzoni
2015-04-22 5:54 ` Lionel Orry
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=20150315232850.21412e3a@free-electrons.com \
--to=thomas.petazzoni@free-electrons.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