[zeus,14/28] file: explicitly disable seccomp

Message ID cbbbee1dce84d6ff62fb72282088f839cb642857.1572072422.git.akuster808@gmail.com
State New
Headers show
  • Untitled series #24473
Related show

Commit Message

Armin Kuster Oct. 26, 2019, 6:49 a.m.
From: Ross Burton <ross.burton@intel.com>

file will automatically enable seccomp if the seccomp headers are available, but
the build will fail on Opensuse Tumbleweed because the include paths are wrong.

Enabling seccomp is a bad idea because it interacts badly with pseudo (causing
build failures), so explicitly and globally disable seccomp.

Signed-off-by: Ross Burton <ross.burton@intel.com>

Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>

(cherry picked from commit a752faa152df031df5acaa40491299ac115109a4)
Signed-off-by: Armin Kuster <akuster808@gmail.com>

 meta/recipes-devtools/file/file_5.37.bb | 2 ++
 1 file changed, 2 insertions(+)


Openembedded-core mailing list


diff --git a/meta/recipes-devtools/file/file_5.37.bb b/meta/recipes-devtools/file/file_5.37.bb
index 803aa9a..6547d12 100644
--- a/meta/recipes-devtools/file/file_5.37.bb
+++ b/meta/recipes-devtools/file/file_5.37.bb
@@ -21,6 +21,8 @@  S = "${WORKDIR}/git"
 inherit autotools update-alternatives
+EXTRA_OECONF += "--disable-libseccomp"
 ALTERNATIVE_${PN} = "file"
 ALTERNATIVE_LINK_NAME[file] = "${bindir}/file"