From: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH] memcached: fix musl build
Date: Fri, 15 Apr 2016 09:36:46 +0200 [thread overview]
Message-ID: <20160415093646.4571d2c2@free-electrons.com> (raw)
In-Reply-To: <1163900c34d6fa034bcb8defc1b0f6578a293b28.1460697551.git.baruch@tkos.co.il>
Hello,
On Fri, 15 Apr 2016 08:19:11 +0300, Baruch Siach wrote:
> Add a patch fixing pre-processor warnings that breaks the build. The patch is
> pending upstream.
>
> Signed-off-by: Baruch Siach <baruch@tkos.co.il>
> ---
> .../memcached/0001-fix-build-with-musl-libc.patch | 78 ++++++++++++++++++++++
> 1 file changed, 78 insertions(+)
> create mode 100644 package/memcached/0001-fix-build-with-musl-libc.patch
I've added a reference to the autobuilder failure being fixed by this
patch, and applied. Thanks!
Thomas
--
Thomas Petazzoni, CTO, Free Electrons
Embedded Linux, Kernel and Android engineering
http://free-electrons.com
next prev parent reply other threads:[~2016-04-15 7:36 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-04-15 5:19 [Buildroot] [PATCH] memcached: fix musl build Baruch Siach
2016-04-15 7:36 ` Thomas Petazzoni [this message]
2016-04-16 14:48 ` Peter Korsgaard
2016-04-16 19:30 ` Baruch Siach
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=20160415093646.4571d2c2@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