diff options
| author | Peter Korsgaard <peter@korsgaard.com> | 2018-10-08 22:28:34 +0200 |
|---|---|---|
| committer | Thomas Petazzoni <thomas.petazzoni@bootlin.com> | 2018-10-09 08:53:00 +0200 |
| commit | a609f83296a27f7677ba53ba40d60c9da21237a9 (patch) | |
| tree | 42d50ffd6d1966b18bf1ada6bf33eba5cad74493 /package/python-numpy/Config.in | |
| parent | 2cd5d6eea13e2a4fcfcf864e2cb0b92ac196a3fe (diff) | |
| download | buildroot-a609f83296a27f7677ba53ba40d60c9da21237a9.tar.gz buildroot-a609f83296a27f7677ba53ba40d60c9da21237a9.zip | |
file: explicitly disable libseccomp support for host
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>
Signed-off-by: Thomas Petazzoni <thomas.petazzoni@bootlin.com>
Diffstat (limited to 'package/python-numpy/Config.in')
0 files changed, 0 insertions, 0 deletions
