Re: [yocto] Yocto Poky 2.4.1 - Remove python3 from build
Yes. I've seen compilation log and it does do_install in final image. It's installed in /usr/lib64/python3.5 on RootFS. Le mer. 17 oct. 2018, à 00 h 48, Burton, Ross a écrit : > On Tue, 16 Oct 2018 at 14:06, Marwen BRIKCHA > wrote: > > > > because, when i run : > > : > > $> bitbake -v opencv > > I can see that python3 is fetched, configure, ... etc > > So, i think it the responsible for this. > > Please remember to CC the list. > > Python being built doesn't lead to Python being installed in the > image. Have a look at the image manifest (in deploy/images) or look > at what is actually installed inside the image. > > Ross > -- ___ yocto mailing list yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/yocto
Re: [yocto] Sumo distro problem with dhcp packet?
Hello Kosta and others,
I am a bit behind on a schedule on this one. Albeit I followed the
advise, This does work for compiling and adding all these packages to
the ROOTFS. I see that after I added all them, I see the
initramfs.tar.xz expanded in
...poky/build/tmp/deploy/image/beagleboneblack/ directory.
But after I do the testing with initramfs, with all these packages
added. I do not find anything in the ROOTFS even what it should be
lookalike DHCP.
After trying # which dhclient, or # which dhcp-client, or # which
dhcp... It finds nothing!
Then, the next step was to find /etc/dhcp/ or similar. There is
nothing lookalike dhcp/ or dhcp* in /etc, which shows that these lines
in dhcp.inc recipe are not executed:
do_install_append () {
install -d ${D}${sysconfdir}/init.d
install -d ${D}${sysconfdir}/default
install -d ${D}${sysconfdir}/dhcp
install -m 0755 ${WORKDIR}/init-relay ${D}${sysconfdir}/init.d/dhcp-relay
install -m 0644 ${WORKDIR}/default-relay
${D}${sysconfdir}/default/dhcp-relay
install -m 0755 ${WORKDIR}/init-server
${D}${sysconfdir}/init.d/dhcp-server
install -m 0644 ${WORKDIR}/default-server
${D}${sysconfdir}/default/dhcp-server
rm -f ${D}${sysconfdir}/dhclient.conf*
rm -f ${D}${sysconfdir}/dhcpd.conf*
In addition, when I execute: $ bitbake -c cleanall dhcp, it says that
it executes thee tasks, and none of them are actually executed (0
executed).
I also recompiled form scratch the whole sumo BBB build, but this did
NOT solve the problem.
Any hint how I should proceed?
Thank you,
Zoran
___
On Thu, Oct 11, 2018 at 1:40 PM Zoran Stojsavljevic
wrote:
>
> Hello Kosta,
>
> > For example, you can do the below:
> > CORE_IMAGE_EXTRA_INSTALL_append = "openssh dhcp-client dhcp-server cmake...
> > "
>
> I added to this example dhcp-relay, just to test the whole build, and
> it does work. Actually, I need only dhcp-client for the target (since
> I have dhcp-server on the ETH interface on the opposite (VM) side).
>
> Thank you for the help!
> Zoran
> ___
> On Wed, Oct 10, 2018 at 5:57 PM Kosta Zertsekel
> wrote:
> >
> > You need to take a look at the available dhcp packages
> > for dhcp recipe here:
> > https://git.yoctoproject.org/clean/cgit.cgi/poky/tree/meta/recipes-connectivity/dhcp/dhcp.inc#n100
> >
> > PACKAGES += "dhcp-libs dhcp-server dhcp-server-config dhcp-client
> > dhcp-relay dhcp-omshell"
> >
> > For example, you can do the below:
> > CORE_IMAGE_EXTRA_INSTALL_append = "openssh dhcp-client dhcp-server cmake...
> > "
> >
> > Thanks,
> > --- Kosta Z
> >
> > From: yocto-boun...@yoctoproject.org on
> > behalf of Zoran Stojsavljevic
> > Sent: Wednesday, 10 October 2018 16:29:05
> > To: Yocto Project
> > Subject: [yocto] Sumo distro problem with dhcp packet?
> >
> > Hello.
> >
> > I need on my test initramfs YOCTO image to add dhcp package (both dhcp
> > server and client).
> >
> > For the beginning, I traced it, where it is:
> > .../poky/meta/recipes-connectivity/dchp
> >
> > and decided to test it adding it to ...poky/build/conf/local.conf for the
> > starters:
> > CORE_IMAGE_EXTRA_INSTALL_append = "openssh dhcp cmake... "
> >
> > But it produced the following error:
> > [user@fedora28-ssd conf]$ bitbake -k core-image-base
> >
> >[snap]
> >
> > ERROR: Nothing RPROVIDES 'dhcp' (but
> > /home/user/projects2/beaglebone-black/sumo/poky/meta/recipes-core/images/core-image-base.bb
> > RDEPENDS on or otherwise requires it)
> > NOTE: Runtime target 'dhcp' is unbuildable, removing...
> > Missing or unbuildable dependency chain was: ['dhcp']
> > ERROR: Nothing RPROVIDES 'core-image-base'
> > No eligible RPROVIDERs exist for 'core-image-base'
> > NOTE: Runtime target 'core-image-base' is unbuildable, removing...
> > Missing or unbuildable dependency chain was: ['core-image-base']
> >
> > I added another package, dhcpcd, which is located in the another layer:
> > CORE_IMAGE_EXTRA_INSTALL_append = "openssh dhcpcd cmake... "
> >
> > so this one worked/was integrated seamlessly.
> >
> > What is the catch 22 here?
> >
> > Thank you,
> > Zoran
> >
--
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto
Re: [yocto] Sumo distro problem with dhcp packet?
I suggest trying other reference image.
For example, core-image-minimal.
If it does not help, then core-image-full-cmdline.
Let's get the working reference first with one of these images.
--- Kosta Z.
From: Zoran Stojsavljevic
Sent: Wednesday, 17 October 2018 11:37:38
To: Kosta Zertsekel; Yocto Project
Subject: Re: [yocto] Sumo distro problem with dhcp packet?
Hello Kosta and others,
I am a bit behind on a schedule on this one. Albeit I followed the
advise, This does work for compiling and adding all these packages to
the ROOTFS. I see that after I added all them, I see the
initramfs.tar.xz expanded in
...poky/build/tmp/deploy/image/beagleboneblack/ directory.
But after I do the testing with initramfs, with all these packages
added. I do not find anything in the ROOTFS even what it should be
lookalike DHCP.
After trying # which dhclient, or # which dhcp-client, or # which
dhcp... It finds nothing!
Then, the next step was to find /etc/dhcp/ or similar. There is
nothing lookalike dhcp/ or dhcp* in /etc, which shows that these lines
in dhcp.inc recipe are not executed:
do_install_append () {
install -d ${D}${sysconfdir}/init.d
install -d ${D}${sysconfdir}/default
install -d ${D}${sysconfdir}/dhcp
install -m 0755 ${WORKDIR}/init-relay ${D}${sysconfdir}/init.d/dhcp-relay
install -m 0644 ${WORKDIR}/default-relay
${D}${sysconfdir}/default/dhcp-relay
install -m 0755 ${WORKDIR}/init-server
${D}${sysconfdir}/init.d/dhcp-server
install -m 0644 ${WORKDIR}/default-server
${D}${sysconfdir}/default/dhcp-server
rm -f ${D}${sysconfdir}/dhclient.conf*
rm -f ${D}${sysconfdir}/dhcpd.conf*
In addition, when I execute: $ bitbake -c cleanall dhcp, it says that
it executes thee tasks, and none of them are actually executed (0
executed).
I also recompiled form scratch the whole sumo BBB build, but this did
NOT solve the problem.
Any hint how I should proceed?
Thank you,
Zoran
___
On Thu, Oct 11, 2018 at 1:40 PM Zoran Stojsavljevic
wrote:
>
> Hello Kosta,
>
> > For example, you can do the below:
> > CORE_IMAGE_EXTRA_INSTALL_append = "openssh dhcp-client dhcp-server cmake...
> > "
>
> I added to this example dhcp-relay, just to test the whole build, and
> it does work. Actually, I need only dhcp-client for the target (since
> I have dhcp-server on the ETH interface on the opposite (VM) side).
>
> Thank you for the help!
> Zoran
> ___
> On Wed, Oct 10, 2018 at 5:57 PM Kosta Zertsekel
> wrote:
> >
> > You need to take a look at the available dhcp packages
> > for dhcp recipe here:
> > https://git.yoctoproject.org/clean/cgit.cgi/poky/tree/meta/recipes-connectivity/dhcp/dhcp.inc#n100
> >
> > PACKAGES += "dhcp-libs dhcp-server dhcp-server-config dhcp-client
> > dhcp-relay dhcp-omshell"
> >
> > For example, you can do the below:
> > CORE_IMAGE_EXTRA_INSTALL_append = "openssh dhcp-client dhcp-server cmake...
> > "
> >
> > Thanks,
> > --- Kosta Z
> >
> > From: yocto-boun...@yoctoproject.org on
> > behalf of Zoran Stojsavljevic
> > Sent: Wednesday, 10 October 2018 16:29:05
> > To: Yocto Project
> > Subject: [yocto] Sumo distro problem with dhcp packet?
> >
> > Hello.
> >
> > I need on my test initramfs YOCTO image to add dhcp package (both dhcp
> > server and client).
> >
> > For the beginning, I traced it, where it is:
> > .../poky/meta/recipes-connectivity/dchp
> >
> > and decided to test it adding it to ...poky/build/conf/local.conf for the
> > starters:
> > CORE_IMAGE_EXTRA_INSTALL_append = "openssh dhcp cmake... "
> >
> > But it produced the following error:
> > [user@fedora28-ssd conf]$ bitbake -k core-image-base
> >
> >[snap]
> >
> > ERROR: Nothing RPROVIDES 'dhcp' (but
> > /home/user/projects2/beaglebone-black/sumo/poky/meta/recipes-core/images/core-image-base.bb
> > RDEPENDS on or otherwise requires it)
> > NOTE: Runtime target 'dhcp' is unbuildable, removing...
> > Missing or unbuildable dependency chain was: ['dhcp']
> > ERROR: Nothing RPROVIDES 'core-image-base'
> > No eligible RPROVIDERs exist for 'core-image-base'
> > NOTE: Runtime target 'core-image-base' is unbuildable, removing...
> > Missing or unbuildable dependency chain was: ['core-image-base']
> >
> > I added another package, dhcpcd, which is located in the another layer:
> > CORE_IMAGE_EXTRA_INSTALL_append = "openssh dhcpcd cmake... "
> >
> > so this one worked/was integrated seamlessly.
> >
> > What is the catch 22 here?
> >
> > Thank you,
> > Zoran
> >
--
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto
Re: [yocto] Yocto Poky 2.4.1 - Remove python3 from build
Easiest way to determine what is pulling it in is to try removing the package on the target using the package manager. That will tell you what dependencies are keeping it in. Ross On Wed, 17 Oct 2018 at 08:32, Marwen BRIKCHA wrote: > > Yes. I've seen compilation log and it does do_install in final image. > It's installed in /usr/lib64/python3.5 on RootFS. > > Le mer. 17 oct. 2018, à 00 h 48, Burton, Ross a écrit > : >> >> On Tue, 16 Oct 2018 at 14:06, Marwen BRIKCHA >> wrote: >> > >> > because, when i run : >> > : >> > $> bitbake -v opencv >> > I can see that python3 is fetched, configure, ... etc >> > So, i think it the responsible for this. >> >> Please remember to CC the list. >> >> Python being built doesn't lead to Python being installed in the >> image. Have a look at the image manifest (in deploy/images) or look >> at what is actually installed inside the image. >> >> Ross -- ___ yocto mailing list yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/yocto
Re: [yocto] Yocto Poky 2.4.1 - Remove python3 from build
Alternatively if you're using RPMs, you can set PACKAGE_EXCLUDE = "python3-core": Error: Problem 1: conflicting requests - nothing provides python3-core needed by dnf-2.7.5-r0.corei7_64 Problem 2: conflicting requests - nothing provides python3-core needed by rpm-1:4.14.2-r0.corei7_64 In this case, Python 3 is in my image because I have package-management on, which needs Python 3. Ross On Wed, 17 Oct 2018 at 10:43, Burton, Ross wrote: > > Easiest way to determine what is pulling it in is to try removing the > package on the target using the package manager. That will tell you > what dependencies are keeping it in. > > Ross > On Wed, 17 Oct 2018 at 08:32, Marwen BRIKCHA wrote: > > > > Yes. I've seen compilation log and it does do_install in final image. > > It's installed in /usr/lib64/python3.5 on RootFS. > > > > Le mer. 17 oct. 2018, à 00 h 48, Burton, Ross a > > écrit : > >> > >> On Tue, 16 Oct 2018 at 14:06, Marwen BRIKCHA > >> wrote: > >> > > >> > because, when i run : > >> > : > >> > $> bitbake -v opencv > >> > I can see that python3 is fetched, configure, ... etc > >> > So, i think it the responsible for this. > >> > >> Please remember to CC the list. > >> > >> Python being built doesn't lead to Python being installed in the > >> image. Have a look at the image manifest (in deploy/images) or look > >> at what is actually installed inside the image. > >> > >> Ross -- ___ yocto mailing list yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/yocto
[yocto] Bitbake Build Configurations
Hi Yocto, I have my bitbake environment set up on the host system CentOS 7 and building images for the target ARM cortex A8 with the following BUILD CONFIGURATION, Build Configuration: BB_VERSION = "1.37.0" BUILD_SYS= "x86_64-linux" NATIVELSBSTRING = "universal-4.8" TARGET_SYS = "arm-poky-linux-gnueabi" MACHINE = "arm-cortex-a8" DISTRO = "poky" DISTRO_VERSION = "2.5" TUNE_FEATURES= "arm armv7a vfp neon callconvention-hard cortexa8" TARGET_FPU = "hard" meta-networking meta-python = "master:45ee3c0e98bd3ed81419aaeae1e7324e486161a2" meta-userbsp-ti meta meta-poky meta-yocto-bsp meta-user-common = ":" meta-oe = "master:45ee3c0e98bd3ed81419aaeae1e7324e486161a2" 1. What I don't understand is how exactly are these Variables set? 2. For the NATIVELSBSTRING which should actually be displaying the HOST OS according to the Yocto Manual, isn't doing that. What could be the reason for that? (Earlier, with Poky Fido, this wasn't the case. It displays "CentOS-Linux-7.1.1503".) 3. From where does Bitbake pull this information? 4. Also how is the TARGET_FPU variable set? Could someone please shed some light on this. Thanks! Mit freundlichen Grüßen / Best Regards, Dhanush Keshava Reddy Soppahalli Mob: +4915216144064 -- ___ yocto mailing list yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/yocto
Re: [yocto] Add python2 as native package in openembedded sdk
Please remember to CC the list. On Wed, 17 Oct 2018 at 14:18, Alberto Eusebi wrote: > On Monday 15 October 2018, alle 17:57, Burton, Ross wrote: > > Add nativesdk-python-core and nativesdk-python-modules to > > TOOLCHAIN_HOST_TASK (using _append). > > But the resulting script don't work, it only unpacks the sysroots and then > stalls: > > > __ ># ./angstrom-glibc-x86_64-armv7at2hf-neon-v2017.12-toolchain.sh -d 4.9 >Angstrom SDK installer version nodistro.0 >= >You are about to install the SDK to "/opt/toradex_sdk/imx6/4.9". > Proceed[Y/n]? >Extracting > SDK.done >Setting it up...ls: cannot access > '/opt/toradex_sdk/imx6/4.9/environment-setup-*': No such file or directory > > __ Sounds like you broke the SDK. How did you set TOOLCHAIN_HOST_TASK? Ross -- ___ yocto mailing list yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/yocto
[yocto] meta-oracle-java still maintained?
I was wondering if meta-oracle-java is still maintained? It looks like there haven't been any release branches created since pyro. We are looking at using it to provide virtual/java-native for some build host tools we have that were written in Java, but I want to make sure that it isn't going to die off on us if we do. Thanks, -- Joshua Watt -- ___ yocto mailing list yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/yocto
Re: [yocto] meta-oracle-java still maintained?
On 10/17/18 9:33 AM, Joshua Watt wrote: > I was wondering if meta-oracle-java is still maintained? It looks like > there haven't been any release branches created since pyro. > > We are looking at using it to provide virtual/java-native for some > build host tools we have that were written in Java, but I want to make > sure that it isn't going to die off on us if we do. I believe this was abandoned when Oracle changed their licensing. The 'meta-java' layer however is still being updated and provides an alternative to the Oracle Java. --Mark > Thanks, > -- ___ yocto mailing list yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/yocto
Re: [yocto] meta-oracle-java still maintained?
On 10/17/18 8:55 AM, Mark Hatle wrote: > On 10/17/18 9:33 AM, Joshua Watt wrote: >> I was wondering if meta-oracle-java is still maintained? It looks like >> there haven't been any release branches created since pyro. >> >> We are looking at using it to provide virtual/java-native for some >> build host tools we have that were written in Java, but I want to make >> sure that it isn't going to die off on us if we do. > I believe this was abandoned when Oracle changed their licensing. > > The 'meta-java' layer however is still being updated and provides an > alternative > to the Oracle Java. Maybe that layer should be moved to the "Yocto Metadata Layer Archive" area then. - armin > --Mark > >> Thanks, >> -- ___ yocto mailing list yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/yocto
[yocto] [meta-security][PATCH] tpm2 packagegroup: fix filenames
tpm2.0-tss package names changed, update accordingly Signed-off-by: Armin Kuster --- meta-tpm/recipes-core/packagegroup/packagegroup-security-tpm2.bb | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/meta-tpm/recipes-core/packagegroup/packagegroup-security-tpm2.bb b/meta-tpm/recipes-core/packagegroup/packagegroup-security-tpm2.bb index 13b505f..099e01c 100644 --- a/meta-tpm/recipes-core/packagegroup/packagegroup-security-tpm2.bb +++ b/meta-tpm/recipes-core/packagegroup/packagegroup-security-tpm2.bb @@ -12,7 +12,7 @@ RDEPENDS_packagegroup-security-tpm2 = " \ tpm2.0-tools \ trousers \ libtss2 \ -libtctidevice \ -libtctisocket \ +libtss2-tcti-device \ +libtss2-tcti-mssim \ resourcemgr \ " -- 2.7.4 -- ___ yocto mailing list yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/yocto
Re: [yocto] Bitbake Build Configurations
On Wed, Oct 17, 2018 at 5:12 AM, Dhanush K.S wrote: > Hi Yocto, > > I have my bitbake environment set up on the host system CentOS 7 and > building images for the target ARM cortex A8 with the following BUILD > CONFIGURATION, > > Build Configuration: > BB_VERSION = "1.37.0" > BUILD_SYS= "x86_64-linux" > NATIVELSBSTRING = "universal-4.8" > TARGET_SYS = "arm-poky-linux-gnueabi" > MACHINE = "arm-cortex-a8" > DISTRO = "poky" > DISTRO_VERSION = "2.5" > TUNE_FEATURES= "arm armv7a vfp neon callconvention-hard cortexa8" > TARGET_FPU = "hard" > meta-networking > meta-python = "master:45ee3c0e98bd3ed81419aaeae1e7324e486161a2" > meta-userbsp-ti > meta > meta-poky > meta-yocto-bsp > meta-user-common = ":" > meta-oe = "master:45ee3c0e98bd3ed81419aaeae1e7324e486161a2" > > What I don't understand is how exactly are these Variables set? > For the NATIVELSBSTRING which should actually be displaying the HOST OS > according to the Yocto Manual, isn't doing that. What could be the reason > for that? (Earlier, with Poky Fido, this wasn't the case. It displays > "CentOS-Linux-7.1.1503".) The documentation for NATIVELSBSTRING perhaps hasn't caught up with recent changes in it's definition and usage. If you see "universal" it means native recipes are being compiled against a version of glibc distributed by the Yocto project rather than the version of glibc provided by your host distro. It's the default approach in recent versions of poky and has the advantage that native recipes are always built against a known and up to date version of glibc. It also allows sstate for native recipes to be shared between hosts with different versions of glibc (which wasn't previously possible). > Also how is the TARGET_FPU variable set? The answer to the question "how is variable XXX set" is always the same... "bitbake -e" will tell you :-) The reason this variable changed compared to older versions of poky is likely to be that your machine config uses the default value of DEFAULTTUNE set by tune-cortexa8.inc. That's the recommended approach, but it does mean your builds will follow any change in the default value. ie you are seeing the result of: http://git.openembedded.org/openembedded-core/commit/?id=2b3ae58f5eaecc8474761c543ff5347aa0e3c4c8 If you don't like the new default and need to compile for softfloat then your machine config should explicitly set DEFAULTTUNE. > Could someone please shed some light on this. > > Thanks! > > Mit freundlichen Grüßen / Best Regards, > Dhanush Keshava Reddy Soppahalli > Mob: +4915216144064 > > -- > ___ > yocto mailing list > yocto@yoctoproject.org > https://lists.yoctoproject.org/listinfo/yocto > -- ___ yocto mailing list yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/yocto
[yocto] [selinux] sumo compilation
Hi, We realized today that SELinux does not compile on sumo branch. Is it possible for someone to branch the last working version to a sumo branch? http://git.yoctoproject.org/cgit/cgit.cgi/meta-selinux/refs/ NOTE: Running task 352 of 2707 (virtual:native:/sources/poky/meta/recipes-devtools/e2fsprogs/e2fsprogs_1.43.8.bb:do_patch) NOTE: recipe e2fsprogs-native-1.43.8-r0: task do_patch: Started NOTE: Running task 1413 of 2707 (/sources/poky/meta/recipes-devtools/e2fsprogs/e2fsprogs_1.43.8.bb:do_patch) NOTE: recipe e2fsprogs-1.43.8-r0: task do_patch: Started ERROR: e2fsprogs-native-1.43.8-r0 do_patch: Command Error: 'quilt --quiltrc Applying patch misc_create_inode.c-label_rootfs.patch patching file misc/create_inode.c Hunk #1 FAILED at 979. Hunk #2 FAILED at 987. Sinan -- ___ yocto mailing list yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/yocto
Re: [yocto] [selinux] sumo compilation
It was broken in rocko too. I added this to local.conf to workaround the problem: PREFERRED_VERSION_refpolicy-standard = "2.20170204" -steve Sinan Kaya wrote: > Hi, > > We realized today that SELinux does not compile on sumo branch. > > Is it possible for someone to branch the last working version to a sumo > branch? > > http://git.yoctoproject.org/cgit/cgit.cgi/meta-selinux/refs/ > > NOTE: Running task 352 of 2707 > (virtual:native:/sources/poky/meta/recipes-devtools/e2fsprogs/e2fsprogs_1.43.8.bb:do_patch) > NOTE: recipe e2fsprogs-native-1.43.8-r0: task do_patch: Started > NOTE: Running task 1413 of 2707 > (/sources/poky/meta/recipes-devtools/e2fsprogs/e2fsprogs_1.43.8.bb:do_patch) > NOTE: recipe e2fsprogs-1.43.8-r0: task do_patch: Started > ERROR: e2fsprogs-native-1.43.8-r0 do_patch: Command Error: 'quilt --quiltrc > Applying patch misc_create_inode.c-label_rootfs.patch > patching file misc/create_inode.c > Hunk #1 FAILED at 979. > Hunk #2 FAILED at 987. > > Sinan > -- > ___ > yocto mailing list > yocto@yoctoproject.org > https://lists.yoctoproject.org/listinfo/yocto -- ___ yocto mailing list yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/yocto
Re: [yocto] [selinux] sumo compilation
Exactly the same issue since September. Here is my discussion https://lists.yoctoproject.org/pipermail/yocto/2018-September/042711.html. With that trick did you find a solution also on sumo? Il gio 18 ott 2018, 01:42 ha scritto: > > It was broken in rocko too. I added this to local.conf to workaround the > problem: > > PREFERRED_VERSION_refpolicy-standard = "2.20170204" > > -steve > > Sinan Kaya wrote: > > Hi, > > > > We realized today that SELinux does not compile on sumo branch. > > > > Is it possible for someone to branch the last working version to a sumo > branch? > > > > http://git.yoctoproject.org/cgit/cgit.cgi/meta-selinux/refs/ > > > > NOTE: Running task 352 of 2707 > > (virtual:native:/sources/poky/meta/recipes-devtools/e2fsprogs/ > e2fsprogs_1.43.8.bb:do_patch) > > NOTE: recipe e2fsprogs-native-1.43.8-r0: task do_patch: Started > > NOTE: Running task 1413 of 2707 > > (/sources/poky/meta/recipes-devtools/e2fsprogs/e2fsprogs_1.43.8.bb: > do_patch) > > NOTE: recipe e2fsprogs-1.43.8-r0: task do_patch: Started > > ERROR: e2fsprogs-native-1.43.8-r0 do_patch: Command Error: 'quilt > --quiltrc > > Applying patch misc_create_inode.c-label_rootfs.patch > > patching file misc/create_inode.c > > Hunk #1 FAILED at 979. > > Hunk #2 FAILED at 987. > > > > Sinan > > -- > > ___ > > yocto mailing list > > yocto@yoctoproject.org > > https://lists.yoctoproject.org/listinfo/yocto > > -- > ___ > yocto mailing list > yocto@yoctoproject.org > https://lists.yoctoproject.org/listinfo/yocto > -- ___ yocto mailing list yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/yocto
