[yocto] meta-selinux warrior support

Mohammad, Jamal M MohammadJamal.Mohiuddin at ncr.com
Tue Oct 8 04:20:00 PDT 2019


Yes openembedded-core has glib-2.60.x in master branch. When I updated the glib recipe to what it is present in master branch. Similar error was reported by mesa recipe. I performed the same process and now I have warrior build available with selinux enabled

From: Jussi Kukkonen <jku at goto.fi>
Sent: Tuesday, October 8, 2019 12:33 PM
To: Mark Hatle <mark.hatle at kernel.crashing.org>
Cc: Oriya, Raxesh <Raxeshkumar.Oriya at ncr.com>; yocto at yoctoproject.org; C M, Kiran Reddy <kiran.reddy at ncr.com>; Mohammad, Jamal M <MohammadJamal.Mohiuddin at ncr.com>
Subject: Re: [yocto] meta-selinux warrior support

*External Message* - Use caution before opening links or attachments

On Tue, 8 Oct 2019 at 09:59, Jussi Kukkonen <jku at goto.fi<mailto:jku at goto.fi>> wrote:


On Mon, 7 Oct 2019 at 17:57, Mark Hatle <mark.hatle at kernel.crashing.org<mailto:mark.hatle at kernel.crashing.org>> wrote:
I thought this issue was already fixed:

http://git.yoctoproject.org/cgit/cgit.cgi/meta-selinux/commit/?h=warrior&id=bb0c9c3abcb935e4b362eb57985e1ee7fec0bfe0<https://urldefense.com/v3/__http:/git.yoctoproject.org/cgit/cgit.cgi/meta-selinux/commit/?h=warrior&id=bb0c9c3abcb935e4b362eb57985e1ee7fec0bfe0__;!9cTk8lEYrHI!_NfmPJMRhiXL2qhIop6uLhChWTOSbHKxot-FGygv9jnHXS1HsCVYfGDANPjJQPvTHQTD3KeZ$>

From the error log:
> glib-2.58.3

From the commit changelog
> In glib 2.60.x, it turns selinux into a meson feature.

That should explain the issue -- maybe oe-core was older than meta-selinux or glib was older for another reason.

Actually, poky warrior only has Glib 2.58.3, right? So the meta-selinux commit makes no sense in Warrior branch?




This patch is what specifically adds the enabled/disabled that the system is
saying (in the logs quoted below) is invalid.

Can you try changing these to 'true' and 'false' instead?

In the file: classes/meson-enable-selinux.bbclass

--Mark

On 10/1/19 1:39 AM, Oriya, Raxesh wrote:
> Hi,
>
>
>
> I am getting the below error when I am trying to integrate 'meta-selinux' into
> our yocto solution. This error also happens when I just build
> 'core-image-selinux' by including the required layers in warrior branch. Can
> anyone provide a fix for this..
>
>
>
> local.conf contains the following lines:
>
> ---------
>
> DISTRO_FEATURES_append = " acl xattr pam selinux"
>
> PREFERRED_PROVIDER_virtual/refpolicy ?= "refpolicy-mls"
>
> ---------
>
>
>
> ERROR: glib-2.0-native-1_2.58.3-r0 do_configure: meson failed
>
> ERROR: glib-2.0-native-1_2.58.3-r0 do_configure: Function failed: do_configure
> (log file is located at
> /home/panther2/warrior/build/tmp/work/x86_64-linux/glib-2.0-native/1_2.58.3-r0/temp/log.do_configure.34545)
>
> ERROR: Logfile of failure stored in:
> /home/panther2/warrior/build/tmp/work/x86_64-linux/glib-2.0-native/1_2.58.3-r0/temp/log.do_configure.34545
>
> Log data follows:
>
> | DEBUG: Executing shell function do_configure
>
> | NOTE: Executing meson -Ddtrace=false -Dfam=false -Dsystemtap=false
> -Dselinux=false -Dlibmount=true -Dman=false -Dselinux=disabled
> -Dinternal_pcre=false -Dinstalled_tests=false...
>
> | The Meson build system
>
> | Version: 0.49.2
>
> | Source dir:
>
> | /home/panther2/warrior/build/tmp/work/x86_64-linux/glib-2.0-native/1_2
>
> | .58.3-r0/glib-2.58.3 Build dir:
>
> | /home/panther2/warrior/build/tmp/work/x86_64-linux/glib-2.0-native/1_2
>
> | .58.3-r0/build
>
> | Build type: native build
>
> |
>
> | meson.build<https://urldefense.com/v3/__http:/meson.build__;!9cTk8lEYrHI!_NfmPJMRhiXL2qhIop6uLhChWTOSbHKxot-FGygv9jnHXS1HsCVYfGDANPjJQPvTHQmUm7_x$>:1:0: ERROR:  Value disabled is not boolean (true or false).
>
> |
>
> | A full log can be found at
>
> | /home/panther2/warrior/build/tmp/work/x86_64-linux/glib-2.0-native/1_2
>
> | .58.3-r0/build/meson-logs/meson-log.txt
>
> | ERROR: meson failed
>
>
>
> Thanks,
>
> Raxesh
>
>
>
>
--
_______________________________________________
yocto mailing list
yocto at yoctoproject.org<mailto:yocto at yoctoproject.org>
https://lists.yoctoproject.org/listinfo/yocto<https://urldefense.com/v3/__https:/lists.yoctoproject.org/listinfo/yocto__;!9cTk8lEYrHI!_NfmPJMRhiXL2qhIop6uLhChWTOSbHKxot-FGygv9jnHXS1HsCVYfGDANPjJQPvTHT1fZ2us$>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.yoctoproject.org/pipermail/yocto/attachments/20191008/5298b96d/attachment-0001.html>


More information about the yocto mailing list