From: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH 1/1] keepalived: Allow the package to be selected only if linux-headers >= 3.4
Date: Sat, 27 May 2017 17:14:56 +0200 [thread overview]
Message-ID: <20170527171456.08fa6d4c@free-electrons.com> (raw)
In-Reply-To: <1495889267-7358-1-git-send-email-apalos@gmail.com>
Hello,
On Sat, 27 May 2017 15:47:47 +0300, Ilias Apalodimas wrote:
> Hello everyone,
>
> This patch fixes build issues of keepalived reported here:
> http://autobuild.buildroot.net/results/770d8fd2f3bacbdbe233da1b4d6e64e20a84d5a5
> http://autobuild.buildroot.net/results/1adb710b915427f681eae37452a0942833ce533e
> http://autobuild.buildroot.net/results/70b31547e51ec7213372d2ef07bec34c5df77560
>
> These builds are all using an external toolchain and linux-3.2 headers.
> Keepalived includes linux_ip_set.h when ipset package is enabled,
> which conflicts with linux xt_set.h header(prior to 3.4).
>
> As Yann Morin suggested we are making keepalived depending on the kernel-headers
> version.
>
> Regards
> Ilias
>
> Signed-off-by: Ilias Apalodimas <apalos@gmail.com>
> ---
> package/keepalived/Config.in | 5 +++--
> 1 file changed, 3 insertions(+), 2 deletions(-)
Applied to master, after fixing the commit log and Config.in comment as
suggested by Yann. Thanks!
Thomas
--
Thomas Petazzoni, CTO, Free Electrons
Embedded Linux, Kernel and Android engineering
http://free-electrons.com
prev parent reply other threads:[~2017-05-27 15:14 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-05-27 12:47 [Buildroot] [PATCH 1/1] keepalived: Allow the package to be selected only if linux-headers >= 3.4 Ilias Apalodimas
2017-05-27 13:24 ` Yann E. MORIN
2017-05-27 15:14 ` Thomas Petazzoni [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=20170527171456.08fa6d4c@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