On Sat, Oct 19, 2019 at 2:58 AM Richard Purdie < [email protected]> wrote:
> On Fri, 2019-10-18 at 18:03 +0530, Khem Raj wrote: > > > > > > On Fri, Oct 18, 2019 at 4:58 PM Ross Burton <[email protected]> > > wrote: > > > 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 <[email protected]> > > > --- > > > meta/recipes-devtools/file/file_5.37.bb | 2 ++ > > > 1 file changed, 2 insertions(+) > > > > > > diff --git a/meta/recipes-devtools/file/file_5.37.bb > > > b/meta/recipes-devtools/file/file_5.37.bb > > > index a840dbc012b..c53a120b840 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" > > > + > > > > On host it makes sense but how about for target recipe ? We do have > > libseccomp support > > Perhaps it’s best to disable it for native and native sdk alone ? > > Given the problem reports in the media and the decisions made by most > other distros I think disabling this is probably safest until its been > make more usable (no other distro is shipping this enabled now). > Ok makes sense > Cheers, > > Richard > > > > > >
-- _______________________________________________ Openembedded-core mailing list [email protected] http://lists.openembedded.org/mailman/listinfo/openembedded-core
