From: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH 2/2] package/libseccomp: fix musl build
Date: Mon, 1 Feb 2016 14:16:31 +0100 [thread overview]
Message-ID: <20160201141631.53d89e66@free-electrons.com> (raw)
In-Reply-To: <1454176919-12144-2-git-send-email-bernd.kuhls@t-online.de>
Dear Bernd Kuhls,
On Sat, 30 Jan 2016 19:01:59 +0100, Bernd Kuhls wrote:
> diff --git a/package/libseccomp/0002-musl.patch b/package/libseccomp/0002-musl.patch
> new file mode 100644
> index 0000000..c3affba
> --- /dev/null
> +++ b/package/libseccomp/0002-musl.patch
> @@ -0,0 +1,33 @@
> +Fix musl build
> +
> +Downloaded from upstream PR:
> +https://github.com/seccomp/libseccomp/pull/23
> +
> +Signed-off-by: Bernd Kuhls <bernd.kuhls@t-online.de>
This should go ...
> +
> +
> +From eb5382287cd25235e760b5da4939510b11bbf2a1 Mon Sep 17 00:00:00 2001
> +From: Kylie McClain <somasis@exherbo.org>
> +Date: Fri, 1 Jan 2016 13:12:59 -0500
> +Subject: [PATCH] system.h: Remove conflicting kernel header include
> +
> +This fixes building on musl libc, since musl does not include kernel
> +headers. I've tested this as working on both glibc and musl.
> +
> +Signed-off-by: Kylie McClain <somasis@exherbo.org>
... here
I've fixed this and applied your patch.
Thanks!
Thomas
--
Thomas Petazzoni, CTO, Free Electrons
Embedded Linux, Kernel and Android engineering
http://free-electrons.com
next prev parent reply other threads:[~2016-02-01 13:16 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-01-30 18:01 [Buildroot] [PATCH 1/2] package/libseccomp: bump version to 2.2.3 Bernd Kuhls
2016-01-30 18:01 ` [Buildroot] [PATCH 2/2] package/libseccomp: fix musl build Bernd Kuhls
2016-02-01 13:16 ` Thomas Petazzoni [this message]
2016-02-01 13:16 ` [Buildroot] [PATCH 1/2] package/libseccomp: bump version to 2.2.3 Thomas Petazzoni
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=20160201141631.53d89e66@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