From: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH] package/keepalived: fix compilation with musl
Date: Sun, 19 Mar 2017 22:08:57 +0100 [thread overview]
Message-ID: <20170319220857.2e4a986d@free-electrons.com> (raw)
In-Reply-To: <1488999383-18704-1-git-send-email-yann.morin.1998@free.fr>
Hello,
On Wed, 8 Mar 2017 19:56:23 +0100, Yann E. MORIN wrote:
> Backport one patch from upstream to fix build without netlink.
> Add two patches to fix integer types.
>
> Fixes:
> http://autobuild.buildroot.org/results/b61/b61c2cfa949c2a20f0702522857d78651207e6d2/
>
> Signed-off-by: "Yann E. MORIN" <yann.morin.1998@free.fr>
> Cc: Ilias Apalodimas <apalos@gmail.com>
> ---
> ...onal-compilation-for-LIBIPVS-without-netl.patch | 35 +++++++++
> .../0002-check-libipvs-add-missing-include.patch | 36 +++++++++
> .../0003-keepalived-ip_vs-fix-integer-types.patch | 87 ++++++++++++++++++++++
> 3 files changed, 158 insertions(+)
> create mode 100644 package/keepalived/0001-Fix-conditional-compilation-for-LIBIPVS-without-netl.patch
> create mode 100644 package/keepalived/0002-check-libipvs-add-missing-include.patch
> create mode 100644 package/keepalived/0003-keepalived-ip_vs-fix-integer-types.patch
Another simpler patch from Baruch, using what you contributed upstream,
has been applied. So I've marked this patch as Rejected.
Thanks!
Thomas
--
Thomas Petazzoni, CTO, Free Electrons
Embedded Linux, Kernel and Android engineering
http://free-electrons.com
prev parent reply other threads:[~2017-03-19 21:08 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-03-08 18:56 [Buildroot] [PATCH] package/keepalived: fix compilation with musl Yann E. MORIN
2017-03-09 7:39 ` Ilias Apalodimas
2017-03-19 21:08 ` 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=20170319220857.2e4a986d@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