[OE-core] "make clean" on Weston

Neither "bitbake -c clean weston" nor "bitbake -c cleanall weston" seems to clean the build directory for me. Is this how it is for autotool project? "make clean" doesn't work either ("no rule to make target clean"). I need my directory cleaned so I can commit only the necessary changes.

Re: [OE-core] [PATCH] openssl_1.0: drop unnecessary dependency on makedepend-native

If you are pretty sure, that makedepend command will available after makedepend-native package dropping, I am fine with that. Cheers, Andrej On 07/31/18 15:34, Andre McCurdy wrote: > On Tue, Jul 31, 2018 at 3:24 AM, Andrej Valek > wrote: >> This program is required for "oe_runmake depend"

[OE-core] [PATCH 1/4] python-pbr: 3.1.1 -> 4.2.0

Signed-off-by: Robert Yang --- meta/recipes-devtools/python/python-pbr.inc | 4 ++-- .../python/{python3-pbr_3.1.1.bb => python3-pbr_4.2.0.bb} | 0 2 files changed, 2 insertions(+), 2 deletions(-) rename meta/recipes-devtools/python/{python3-pbr_3.1.1.bb =>

[OE-core] [PATCH 4/4] e2fsprogs: 1.44.2 -> 1.44.3

Rebased ptest.patch. Signed-off-by: Robert Yang --- .../e2fsprogs/e2fsprogs/ptest.patch| 49 -- .../{e2fsprogs_1.44.2.bb => e2fsprogs_1.44.3.bb} | 2 +- 2 files changed, 29 insertions(+), 22 deletions(-) rename

[OE-core] [PATCH 3/4] python3-testtools: 2.2.0 -> 2.3.0

Signed-off-by: Robert Yang --- meta/recipes-devtools/python/python-testtools.inc | 4 ++-- .../python/{python3-testtools_2.2.0.bb => python3-testtools_2.3.0.bb} | 0 2 files changed, 2 insertions(+), 2 deletions(-) rename

[OE-core] [PATCH 2/4] python3-subunit: 1.1.0 -> 1.3.0

The license file changes from README to README.rst, and the lines which contains license info is from 1 to 20. The license is still Apache-2.0. Signed-off-by: Robert Yang --- meta/recipes-devtools/python/python-subunit.inc | 6 +++--- .../python/{python3-subunit_1.1.0.bb =>

[OE-core] [PATCH 0/4] Recipes upgrade

The following changes since commit 51a09ba2729a840a9f2f87b68c7f50a3e6ac0d04: gcc-7.3: Backport fixes for std::pair high memory usage (2018-07-31 22:55:31 +0100) are available in the git repository at: git://git.openembedded.org/openembedded-core-contrib rbt/pu

[OE-core] [PATCH] wic/qemux86: don't pass ip parameter to kernel in wks

Images that rely on dhcp being used won't have network setup properly otherwise. Fixes [YOCTO #12804] Signed-off-by: Anuj Mittal --- scripts/lib/wic/canned-wks/qemux86-directdisk.wks | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git

[OE-core] [PATCH] sudo: add PACKAGECONFIG for pam-wheel

The pam_wheel PAM module is used to enforce the so-called wheel group. By default it permits root access to the system if the applicant user is a member of the wheel group. Add PACKAGECONFIG to enable pam_wheel module for sudo. Signed-off-by: Yi Zhao --- meta/recipes-extended/sudo/sudo.inc

[OE-core] [PATCH] mdadm: add init and systemd service scripts

Add init script and service file for sysvinit and systemd. Signed-off-by: Zheng Ruoqin --- .../recipes-extended/mdadm/files/mdadm.conf.sample | 1 + meta/recipes-extended/mdadm/files/mdadm.default| 25 meta/recipes-extended/mdadm/files/mdadm.init | 71 ++

Re: [OE-core] [PATCH] devtool-source.bbclass: Support kernel fragments not in SRC_URI

On 07/31/2018 05:21 AM, Jaewon Lee wrote: > When using a recipe space kernel-meta, scc files are added through > SRC_URI, but they may include corresponding kernel fragments that are > not necessarily in SRC_URI. > > For bitbake, this is not a problem because the kernel-yocto class adds > the

Re: [OE-core] [PATCH] machine: remove kernel-modules from RRECOMMENDS

Hi Anuj, On Wed, Aug 01, 2018 at 10:43:03AM +0800, Anuj Mittal wrote: > On 07/31/2018 11:22 PM, openembedded-core-boun...@lists.openembedded.org > wrote: > > On Tue, 2018-07-31 at 17:15 +0300, Maxin B. John wrote: > >> qemumips,qemumips64 and x86 based machines include kernel-modules by > >>

Re: [OE-core] [PATCH 2/2] multiconfig: Enable multiconfig dependencies on oe-core

On Tue, Jul 31, 2018 at 4:59 AM Richard Purdie < richard.pur...@linuxfoundation.org> wrote: > On Mon, 2018-07-30 at 15:05 -0700, Alejandro Enedino Hernandez > Samaniego wrote: > > On 07/26/2018 08:36 PM, Khem Raj wrote: > > > > > > On 7/25/18 9:05 AM, Alejandro Enedino Hernandez Samaniego wrote:

[OE-core] Why does Openssl 1.0.2n use libcrypto.so.1.0.2 and not libcrypto.so.1.0.0?

All, I have a library that uses libcrypto.so.1.0.0 from openssl 1.0.2n, which is the libcrypto.so version if you download the source code to ubuntu 16.04 from openssl and compile. However, Yocto Rocko uses the same openssl 1.0.2n version but it uses libcrypto.so.1.0.2 and sets the

Re: [OE-core] Why does Openssl 1.0.2n use libcrypto.so.1.0.2 and not libcrypto.so.1.0.0?

Alex, The library was precompiled by tail-f but I've also recompiled on Ubuntu 16.04 with openssl 1.0.2n. In both cases the library crypto.so and libconfd.so refer to libcrypto.so.1.0.0. Having a pre-compiled library worked on krogoth and morty, but does not seem to work on rocko. Ryan On

Re: [OE-core] Strip kernel modules and signatures

On Wed, Aug 1, 2018 at 3:46 PM, Ocampo Coronado, Omar wrote: > Hello OE, > > While attempting to sign our kernel modules (using the kernel configuration > CONFIG_MODULE_SIG) the drivers in our image did not have the signature, even > the certificate was being loaded by the kernel or the driver

[OE-core] [PATCH] ffmpeg: Upgrade to 4.0.2

From: Mingli Yu Signed-off-by: Mingli Yu --- .../ffmpeg/{ffmpeg_4.0.bb => ffmpeg_4.0.2.bb} | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) rename meta/recipes-multimedia/ffmpeg/{ffmpeg_4.0.bb => ffmpeg_4.0.2.bb} (97%) diff --git

[OE-core] Strip kernel modules and signatures

Hello OE, While attempting to sign our kernel modules (using the kernel configuration CONFIG_MODULE_SIG) the drivers in our image did not have the signature, even the certificate was being loaded by the kernel or the driver being signed during do_install(). Turns out package.bbclass, while

Re: [OE-core] [PATCH 2/2] multiconfig: Enable multiconfig dependencies on oe-core

Hey Khem, Richard, On 08/01/2018 10:44 AM, Khem Raj wrote: On Tue, Jul 31, 2018 at 4:59 AM Richard Purdie > wrote: On Mon, 2018-07-30 at 15:05 -0700, Alejandro Enedino Hernandez Samaniego wrote: > On 07/26/2018 08:36 PM, Khem Raj

[OE-core] [PATCH v2] devtool-source.bbclass: Support kernel-fragments/patch not in SRC_URI

When using a recipe space kernel-meta, scc files are added through SRC_URI, but they may include corresponding kernel fragments or patches that are not necessarily in SRC_URI. For bitbake, this is not a problem because the kernel-yocto class adds the path where the .scc file was found to includes

Re: [OE-core] Why does Openssl 1.0.2n use libcrypto.so.1.0.2 and not libcrypto.so.1.0.0?

On Wed, Aug 1, 2018 at 1:35 PM, Ryan Pabis (pabisr) via Openembedded-core wrote: > Alex, > > The library was precompiled by tail-f but I've also recompiled on Ubuntu > 16.04 with openssl 1.0.2n. In both cases the library crypto.so and > libconfd.so refer to libcrypto.so.1.0.0. > > Having a

Re: [OE-core] [PATCH] machine: remove kernel-modules from RRECOMMENDS

I believe the rationale for genericx86 is "this BSP should boot on most hardware, so build and ship all the modules". Ross On 1 August 2018 at 12:58, Maxin B. John wrote: > Hi Anuj, > > On Wed, Aug 01, 2018 at 10:43:03AM +0800, Anuj Mittal wrote: >> On 07/31/2018 11:22 PM,

Re: [OE-core] Why does Openssl 1.0.2n use libcrypto.so.1.0.2 and not libcrypto.so.1.0.0?

2018-08-01 20:20 GMT+02:00 Ryan Pabis (pabisr) via Openembedded-core : > I have a library that uses libcrypto.so.1.0.0 from openssl 1.0.2n, which is > the libcrypto.so version if you download the source code to ubuntu 16.04 > from openssl and compile. However, Yocto Rocko uses the same openssl

Re: [OE-core] [PATCH] openssl_1.0: drop unnecessary dependency on makedepend-native

On Wed, Aug 1, 2018 at 12:44 AM, Andrej Valek wrote: > If you are pretty sure, that makedepend command will available after > makedepend-native package dropping, I am fine with that. I am sure that the makedepend command will NOT be available after removing the makedepend-native dependency.

Re: [OE-core] [PATCH] devtool-source.bbclass: Support kernel fragments not in SRC_URI

On 08/02/2018 08:27 AM, Jaewon Lee wrote: > Hi Anuj, > > Thanks for the reply > That is a good point, will send a v2 that also deals with patches. > Regarding other scc files, according to the kernel dev manual, > "It is only necessary to specify the .scc files on the SRC_URI." > > So from my

Re: [OE-core] [PATCH] devtool-source.bbclass: Support kernel fragments not in SRC_URI

Hey Anuj, On 08/01/2018 04:25 AM, Anuj Mittal wrote: On 07/31/2018 05:21 AM, Jaewon Lee wrote: When using a recipe space kernel-meta, scc files are added through SRC_URI, but they may include corresponding kernel fragments that are not necessarily in SRC_URI. For bitbake, this is not a

[OE-core] [oe-core][PATCH v4 0/3] udev-extraconf/mount.sh: add support to systemd

v4: Fix the recursively dependency for the systemd-mount v3: perfect syntax Hongzhi.Song (3): udev-extraconf/mount.sh: add support to systemd udev-extraconf/mount.sh: Fix the recursively dependency for the systemd-mount udev-extraconf/mount.sh: Skip the entry in /etc/fstab when

[OE-core] [oe-core][PATCH v4 1/3] udev-extraconf/mount.sh: add support to systemd

Udev-extraconf works correctly with sysvinit in the aspect of automounting block devices. But it has a serious problem in case of systemd. Block devices automounted by udev is unaccessible to host space(out of udevd's private namespace). For example, we cannot format those block devices. e.g.

[OE-core] [oe-core][PATCH 2/3] udev-extraconf/mount.sh: Fix the recursively dependency for the systemd-mount

If systemd is used, using the systemd-mount to mount the new added disk partitions forgets to move the codes which tries to mount the partition by using the configuration in /etc/fstab to the non-systemd function. And it will cause the systemd-mount try to mount the partition synchronously and

[OE-core] [oe-core][PATCH 3/3] udev-extraconf/mount.sh: Skip the entry in /etc/fstab when using the systemd-mount

When using systemd, the systemd-fstab-generator would parse the /etc/fstab and create the corresponding unit dynamically. So we don't need to handle the ADD action for the partitions in /etc/fstab. Signed-off-by: Kevin Hao Signed-off-by: Hongzhi.Song ---

Re: [OE-core] [PATCH] devtool-source.bbclass: Support kernel fragments not in SRC_URI

On 08/02/2018 07:30 AM, Alejandro Enedino Hernandez Samaniego wrote: > Hey Anuj, > > > On 08/01/2018 04:25 AM, Anuj Mittal wrote: >> On 07/31/2018 05:21 AM, Jaewon Lee wrote: >>> When using a recipe space kernel-meta, scc files are added through >>> SRC_URI, but they may include corresponding

[OE-core] [PATCH 1/1] man-db: remove '--disable-cache-owner' option

The following error appeared at boot. systemd-tmpfiles[115]: [/usr/lib/tmpfiles.d/man-db.conf:1] Unknown user '1w' By default cache owner is enabled and defaults to 'man'. Users could supply '--enable-cache-owner=[ARG]' to change the default cache owner. Using '--disable-cache-owner' leaves

[OE-core] [PATCH 0/1] man-db: remove '--disable-cache-owner' option

*** BLURB HERE *** The following changes since commit 2b2dfec80b6ce45325dfaa4bdf680ad0cd0a8460: libtool: Fix patch status tag (2018-08-01 10:28:05 +0100) are available in the git repository at: git://git.pokylinux.org/poky-contrib ChenQi/man-db