[yocto] [meta-security][PATCH] scap-security-guide: use makefile generator instead of ninja for cmake

2019-03-06 Thread Yi Zhao
Fixes build error: | make: *** No rule to make target 'openembedded'. Stop. Signed-off-by: Yi Zhao --- .../recipes-openscap/scap-security-guide/scap-security-guide_0.1.33.bb | 2 ++ 1 file changed, 2 insertions(+) diff --git

Re: [yocto] [opkg-devel] [opkg-utils] Question: why update-alternatives from opkg-utils chooses /usr/lib to hold database?

2019-03-06 Thread Alex Kiernan
On Wed, Mar 6, 2019 at 11:37 PM Mark Hatle wrote: > > On 3/5/19 10:44 PM, Alex Kiernan wrote: > > On Tue, Mar 5, 2019 at 10:50 PM Richard Purdie > > wrote: > >> > >> On Tue, 2019-03-05 at 16:05 +, Alejandro Del Castillo wrote: > >>> > >>> On 3/5/19 12:11 AM, ChenQi wrote: > Hi All, >

Re: [yocto] [opkg-devel] [opkg-utils] Question: why update-alternatives from opkg-utils chooses /usr/lib to hold database?

2019-03-06 Thread Mark Hatle
On 3/5/19 10:44 PM, Alex Kiernan wrote: > On Tue, Mar 5, 2019 at 10:50 PM Richard Purdie > wrote: >> >> On Tue, 2019-03-05 at 16:05 +, Alejandro Del Castillo wrote: >>> >>> On 3/5/19 12:11 AM, ChenQi wrote: Hi All, Recently I'm dealing with issue from which some discussion

Re: [yocto] Incremental rebuild doesn't pick up FILES changes.

2019-03-06 Thread Kaz Kylheku (poky)
On 2019-03-06 14:26, Kaz Kylheku (poky) wrote: So I'm guessing this should be FILES_${PN}-core_remove = No dice. FILES_${PN}-core_remove = "${libdir}/python-2.7/encodings" does not register anywhere. In the "bitbake -e" output, no _remove event appears for FILES_python-core, and the image

Re: [yocto] Incremental rebuild doesn't pick up FILES changes.

2019-03-06 Thread Burton, Ross
On Wed, 6 Mar 2019 at 22:27, Kaz Kylheku (poky) <442-103-8...@kylheku.com> wrote: > Ah, okay; this is because it's been split into various sub-packages. So > we have to operate on "-core". > The .json manifest brings these into the "core" package: > > "${libdir}/python2.7/encodings",

Re: [yocto] Incremental rebuild doesn't pick up FILES changes.

2019-03-06 Thread Kaz Kylheku (poky)
On 2019-03-06 12:29, Burton, Ross wrote: On Wed, 6 Mar 2019 at 20:14, Kaz Kylheku (poky) <442-103-8...@kylheku.com> wrote: So, the issues are now is that FILES_${PN}_remove = "${libdir}/python2.7/encodings" in fact does not work, as I believed. Have a look at python.bb. Specifically:

[linux-yocto] Risks to transfer from Debian armhf to Yocto

2019-03-06 Thread JH
Hi, Sorry I am new to Yocto to ask very basic questions. My application was previously running on Debian 8 armhf, the new embedded device is now to reduce the Flash and Ram size I have been battering to cut the Debian image size down, the chance to make the small Debian image size to fit the new

Re: [yocto] Incremental rebuild doesn't pick up FILES changes.

2019-03-06 Thread Burton, Ross
On Wed, 6 Mar 2019 at 20:14, Kaz Kylheku (poky) <442-103-8...@kylheku.com> wrote: > So, the issues are now is that > > FILES_${PN}_remove = "${libdir}/python2.7/encodings" > > in fact does not work, as I believed. Have a look at python.bb. Specifically: PACKAGES_remove = "${PN}" There is no PN

Re: [yocto] Incremental rebuild doesn't pick up FILES changes.

2019-03-06 Thread Kaz Kylheku (poky)
On 2019-03-06 10:23, Richard Purdie wrote: On Tue, 2019-03-05 at 18:28 -0800, Kaz Kylheku (poky) wrote: How do we get Yocto to react to FILES changes, short of blowing away the entire build tree? Maybe related to this change:

Re: [yocto] INHIBIT_SYSROOT_STRIP

2019-03-06 Thread Dimitris Tassopoulos
My use case, as I've told to Scott, was building a bare metal firmware for a cortex m0 with an external GCC toolchain. Although, the toolchain's binaries are strippable, there are some other blob files that are needed for the build, which are not. Cheers, Dimitris Scott Rifenbark schrieb am

Re: [yocto] INHIBIT_SYSROOT_STRIP

2019-03-06 Thread Scott Rifenbark
Got it. Thanks Khem. On Wed, Mar 6, 2019 at 10:22 AM Khem Raj wrote: > On Wed, Mar 6, 2019 at 9:48 AM Scott Rifenbark > wrote: > > > > I think we should probably at least document the variable in the YP > Reference Manual's glossary. Correct? > > > > yes and also mention that we only expect

Re: [yocto] Incremental rebuild doesn't pick up FILES changes.

2019-03-06 Thread Richard Purdie
On Tue, 2019-03-05 at 18:28 -0800, Kaz Kylheku (poky) wrote: > Hi, > > I'm working in a Yocto 2.5 environment. > > In my own layer, I added a bbappend targeting python which does this: > >FILES_${PN}_remove = "${libdir}/python2.7/encodings" > > Now this didn't take effect as I expected. I

Re: [yocto] INHIBIT_SYSROOT_STRIP

2019-03-06 Thread Khem Raj
On Wed, Mar 6, 2019 at 9:48 AM Scott Rifenbark wrote: > > I think we should probably at least document the variable in the YP Reference > Manual's glossary. Correct? > yes and also mention that we only expect it to be used in rare special curcumstances, e,g, prebuilt binaries etc. > Scott > >

Re: [yocto] INHIBIT_SYSROOT_STRIP

2019-03-06 Thread Scott Rifenbark
I think we should probably at least document the variable in the YP Reference Manual's glossary. Correct? Scott On Wed, Mar 6, 2019 at 9:24 AM Khem Raj wrote: > On Wed, Mar 6, 2019 at 8:15 AM Scott Rifenbark > wrote: > > > > Dimitris, > > > > Good find... I will see about documenting this. >

Re: [yocto] INHIBIT_SYSROOT_STRIP

2019-03-06 Thread Khem Raj
On Wed, Mar 6, 2019 at 8:15 AM Scott Rifenbark wrote: > > Dimitris, > > Good find... I will see about documenting this. > Although its not encouranged to use it, its to be used as a last resort we use it sparingly. > Scott > > On Wed, Mar 6, 2019 at 8:12 AM Dimitris Tassopoulos wrote: >> >> Hi

[yocto] [PATCH 4/4] poky/kernel: make default 5.0

2019-03-06 Thread bruce . ashfield
From: Bruce Ashfield The 5.0 kernel is available and 4.18 will soon be dropped, so we updated the preferred version to 5.0. Signed-off-by: Bruce Ashfield --- meta-poky/conf/distro/poky.conf | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/meta-poky/conf/distro/poky.conf

[yocto] [PATCH 3/4] meta-yocto-bsp: Update the default kernel to v5.0 for the non-x86 BSPs

2019-03-06 Thread bruce . ashfield
From: Kevin Hao Signed-off-by: Kevin Hao Signed-off-by: Bruce Ashfield --- meta-yocto-bsp/conf/machine/beaglebone-yocto.conf | 2 +- meta-yocto-bsp/conf/machine/edgerouter.conf | 2 +- meta-yocto-bsp/conf/machine/mpc8315e-rdb.conf | 2 +- 3 files changed, 3 insertions(+), 3

[yocto] [PATCH 2/4] meta-yocto-bsp: Add the v5.0 kernel support for all the BSPs

2019-03-06 Thread bruce . ashfield
From: Kevin Hao Boot test for all the boards. Signed-off-by: Kevin Hao Signed-off-by: Bruce Ashfield --- .../linux/linux-yocto_5.0.bbappend| 24 +-- 1 file changed, 12 insertions(+), 12 deletions(-) diff --git

[yocto] [PATCH 1/4] meta-yocto-bsp: introduce 5.0 bbappend

2019-03-06 Thread bruce . ashfield
From: Bruce Ashfield Although the hardware reference boards are not using the 5.x kernel yet, we generate a baseline bbappend for future work. Signed-off-by: Bruce Ashfield --- .../linux/linux-yocto_5.0.bbappend| 27 +++ 1 file changed, 27 insertions(+) create

[yocto] [PATCH 0/4] meta-yocto-bsp/poky: update kernel to 5.0

2019-03-06 Thread bruce . ashfield
From: Bruce Ashfield This is a follow on to my oe-core series that introduces the 5.0 kernel. Once that is merged (and all outstanding issues resolved), these can be applied to make the default 5.0 for poky and the reference BSPs. The removal of 4.18 from master will follow once everything is

Re: [yocto] INHIBIT_SYSROOT_STRIP

2019-03-06 Thread Scott Rifenbark
Dimitris, Good find... I will see about documenting this. Scott On Wed, Mar 6, 2019 at 8:12 AM Dimitris Tassopoulos wrote: > Hi all, > > this is not a request for help. > > Today, I've found a very nice option which is not documented > which is the INHIBIT_SYSROOT_STRIP and is used in the

[yocto] INHIBIT_SYSROOT_STRIP

2019-03-06 Thread Dimitris Tassopoulos
Hi all, this is not a request for help. Today, I've found a very nice option which is not documented which is the INHIBIT_SYSROOT_STRIP and is used in the sysroot_strip() inside the poky/meta/classes/staging.bbclass. I had an issue with a recipe that had a few binaries that I wanted to add to

Re: [yocto] [thud]: Issues with git sub modules

2019-03-06 Thread Alexander Kanavin
Yocto master has got a lot of fixing around gitsm fetcher (particularly creation of symlinks seems to be gone), so if you could try that and report, that would be appreciated. Alex On Wed, 6 Mar 2019 at 15:20, philippe gislard wrote: > > Hello everyone, > > Our use case is the following: > - We

Re: [yocto] using git am to apply git patch in the workdir of any package+

2019-03-06 Thread Alexander Kanavin
The supported recommended workflow for this things is with devtool. Please try especially 'devtool modify' and 'devtool upgrade'. The latter will rebase patches for you, regardless of how they were made. Alex On Wed, 6 Mar 2019 at 15:18, Pandey, Kamal wrote: > Hello, > > I am trying to modify

Re: [linux-yocto] [PATCH 0/3] [kernel-cache] [yocto-5.0] Enable the v5.0 kernel support for the reference BSPs

2019-03-06 Thread Bruce Ashfield
Thanks Kevin, This is now merged. Bruce On Wed, Mar 6, 2019 at 7:13 AM Kevin Hao wrote: > > Hi, > > - Fix the kernel config check warnings for the new kernel. > - Fix the serial malfunction on the beaglebone board. > > > Kevin Hao (3): > mpc8315e-rdb: Enable the CONFIG_MTD_PHYSMAP >

[yocto] [thud]: Issues with git sub modules

2019-03-06 Thread philippe gislard
Hello everyone, Our use case is the following: - We are building firmwares using yocto on machines that have no internet access - We have a mirror that we are feeding with tarballs generated by a machine connected to internet - We want to port our BSP to yocto thud Until now (we used krogoth)

[yocto] using git am to apply git patch in the workdir of any package+

2019-03-06 Thread Pandey, Kamal
Hello, I am trying to modify the src code of a package named say x, For this I type the command $bitbake x -c devshell. This leads me to the git repo of the x package(if it is a git repo). Now I do my changes, commit the changes, and create a patch out of it using git format-patch. Now I want

[linux-yocto] [PATCH 2/3] beaglebone: Update the audio options

2019-03-06 Thread Kevin Hao
With the commit f2055e145f29 ("ASoC: ti: Merge davinci and omap directories"), some of the audio options are removed from the kernel. Use the new options for the audio support. Signed-off-by: Kevin Hao --- bsp/beaglebone/beaglebone.cfg | 7 +++ 1 file changed, 3 insertions(+), 4

[linux-yocto] [PATCH 3/3] beaglebone: Switch to the 8250 omap driver

2019-03-06 Thread Kevin Hao
In the v5.0 kernel, the SERIAL_OMAP driver doesn't work anymore. So switch to the 8250 omap driver for the serial support. Signed-off-by: Kevin Hao --- bsp/beaglebone/beaglebone.cfg | 8 +--- 1 file changed, 5 insertions(+), 3 deletions(-) diff --git a/bsp/beaglebone/beaglebone.cfg

[linux-yocto] [PATCH 1/3] mpc8315e-rdb: Enable the CONFIG_MTD_PHYSMAP

2019-03-06 Thread Kevin Hao
This is needed by the CONFIG_MTD_PHYSMAP_OF. Signed-off-by: Kevin Hao --- bsp/fsl-mpc8315e-rdb/fsl-mpc8315e-rdb.cfg | 1 + 1 file changed, 1 insertion(+) diff --git a/bsp/fsl-mpc8315e-rdb/fsl-mpc8315e-rdb.cfg b/bsp/fsl-mpc8315e-rdb/fsl-mpc8315e-rdb.cfg index 57ebaabb6583..cb7c40d37c22 100644

[linux-yocto] [PATCH 0/3] [kernel-cache] [yocto-5.0] Enable the v5.0 kernel support for the reference BSPs

2019-03-06 Thread Kevin Hao
Hi, - Fix the kernel config check warnings for the new kernel. - Fix the serial malfunction on the beaglebone board. Kevin Hao (3): mpc8315e-rdb: Enable the CONFIG_MTD_PHYSMAP beaglebone: Update the audio options beaglebone: Switch to the 8250 omap driver bsp/beaglebone/beaglebone.cfg