From: Thomas Petazzoni <thomas.petazzoni@bootlin.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH] file: explicitly disable libseccomp support for host
Date: Tue, 9 Oct 2018 08:59:11 +0200 [thread overview]
Message-ID: <20181009085911.1a863a1a@windsurf> (raw)
In-Reply-To: <20181008202834.13821-1-peter@korsgaard.com>
Hello,
On Mon, 8 Oct 2018 22:28:34 +0200, Peter Korsgaard wrote:
> Fixes:
> http://autobuild.buildroot.net/results/8a2/8a2ea2e4426416447705492237f526fc84b595d7/
> http://autobuild.buildroot.net/results/a1f/a1f2369d31c2387efdec908877e0bcaa728b5aeb/
>
> file-5.33 added optional seccomp support, but the filters did not cover all
> needed syscalls, leading to errors when the freshly built host-file is
> executed as part of the build on distributions with seccomp support (E.G.
> Arch Linux):
>
> checking for seccomp_init in -lseccomp... yes
> ..
> ../src/file -C -m magic
> make[3]: *** [Makefile:764: magic.mgc] Bad system call
>
> This has been fixed in file-5.34, but it anyway makes sense to explicitly
> disable libseccomp support for consistency as we do not need it for the host
> build.
>
> Signed-off-by: Peter Korsgaard <peter@korsgaard.com>
> ---
> package/file/file.mk | 1 +
> 1 file changed, 1 insertion(+)
Applied to master, thanks.
Thomas
--
Thomas Petazzoni, CTO, Bootlin
Embedded Linux and Kernel engineering
https://bootlin.com
next prev parent reply other threads:[~2018-10-09 6:59 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-10-08 20:28 [Buildroot] [PATCH] file: explicitly disable libseccomp support for host Peter Korsgaard
2018-10-09 6:59 ` Thomas Petazzoni [this message]
2018-10-21 12:50 ` Peter Korsgaard
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=20181009085911.1a863a1a@windsurf \
--to=thomas.petazzoni@bootlin.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