[yocto] QA issue [configure-unsafe] when compiling vlc

2019-06-05 Thread Ori Pessach
Hi, I'm trying to compile vlc 3.0.6 as part of my image from the recipe found here: https://layers.openembedded.org/layerindex/recipe/4796/ When bitbake configures the source, I get the following error: ERROR: vlc-3.0.6-r0 do_configure: QA Issue: This autoconf log indicates errors, it looked at

[yocto] [meta-anaconda][PATCH] anaconda_oe.py: add ldconfig to DISTRO_FEATURES

2019-06-05 Thread Chen Qi
'ldconfig' is a required distro feature for anaconda, so add it before running any builds, otherwise, we get build failure due to lack of 'ldconfig'. Signed-off-by: Chen Qi --- lib/oeqa/selftest/cases/anaconda_oe.py | 1 + 1 file changed, 1 insertion(+) diff --git a/lib/oeqa/selftest/cases/anac

[yocto] warning: #warning _FORTIFY_SOURCE requires compiling with optimization (-O)

2019-06-05 Thread Robert Berger
Hi, I can see in some examples: warning: #warning _FORTIFY_SOURCE requires compiling with optimization (-O) which can be fixed by passing the proper CFLAGS. Unfortunately the warning is only visible in log files. 1) Is there a way to show compiler warnings when you bitbake on the console (wi

Re: [yocto] Fwd: Potential (?) systemd YOCTO problems

2019-06-05 Thread Morné Lamprecht
On Tue, Jun 04, 2019 at 11:34:15PM +0200, Zoran Stojsavljevic wrote: (I did not find it anywhere in the manuals, maybe I missed the paragraph - please, advice where it is?). This is where I found it previously: https://www.yoctoproject.org/docs/2.7/dev-manual/dev-manual.html#using-systemd-excl

Re: [yocto] [meta-gplv2][PATCH] elfutils: ignore new error from gcc-9

2019-06-05 Thread Burton, Ross
Pushed, thanks. Ross On Wed, 5 Jun 2019 at 08:56, Martin Jansa wrote: > > Signed-off-by: Martin Jansa > --- > recipes-devtools/elfutils/elfutils_0.148.bb | 4 > 1 file changed, 4 insertions(+) > > diff --git a/recipes-devtools/elfutils/elfutils_0.148.bb > b/recipes-devtools/elfutils/elfu

[yocto] git fetcher - AUTOREV and best practices

2019-06-05 Thread Maciej Pijanowski
Hello, As explained in the mega manual [1], when using the git:// fetcher, setting the SRCREV to ${AUTOREV} will result in building the latest commit from given git branch (master, if not specified otherwise). Using AUTOREV feature in recipe has following implications as far as I can see: - the

Re: [yocto] [Yocto][multilib] No Manifest file generated from: lib32-alsa-lib

2019-06-05 Thread Måns Zigher
So it looks like I should include armv7ahf-neon-mx8mm to PACKAGE_EXTRA_ARCHS but I am unsure how to do that any ideas? /Måns Den ons 5 juni 2019 kl 14:05 skrev Måns Zigher : > > Looking in the env dump I can see that meta-freescale is overwriting > the PACKAGE_ARCH in a alsa-lib_%.bbappend > > PA

Re: [yocto] [Yocto][multilib] No Manifest file generated from: lib32-alsa-lib

2019-06-05 Thread Måns Zigher
Looking in the env dump I can see that meta-freescale is overwriting the PACKAGE_ARCH in a alsa-lib_%.bbappend PACKAGE_ARCH_imx = "${MACHINE_SOCARCH}" /Måns Den ons 5 juni 2019 kl 14:04 skrev Måns Zigher : > > So running bitbake -e lib32-alsa-lib I can see the following > > # $SSTATE_MANMACH [2

Re: [yocto] [Yocto][multilib] No Manifest file generated from: lib32-alsa-lib

2019-06-05 Thread Måns Zigher
So running bitbake -e lib32-alsa-lib I can see the following # $SSTATE_MANMACH [2 operations] # set? /home/extzig/Workspace/mozart-workspace/layers/poky/meta/classes/sstate.bbclass:54 # "${SSTATE_PKGARCH}" # set sstate.bbclass:94 [__anon_105__home_extzig_Workspace_mozart_workspace_layers_

Re: [yocto] [Yocto][multilib] No Manifest file generated from: lib32-alsa-lib

2019-06-05 Thread Måns Zigher
I have the following manifest files find . -name "manifest*-lib32-alsa-lib*" ./manifest-mimx8mm-lib32-alsa-lib.packagedata ./manifest-armv7ahf-neon-mx8mm-lib32-alsa-lib.package_write_rpm ./manifest-armv7ahf-neon-mx8mm-lib32-alsa-lib.package but find_sstate_manifest called from package_manager ./

Re: [yocto] [Yocto][multilib] No Manifest file generated from: lib32-alsa-lib

2019-06-05 Thread Måns Zigher
I think this looks wrong "manifest-x86_64_x86_64-nativesdk-lib32-alsa-lib.package_write_rpm" I have not intentionally added lib32-alsa-lib to the nativesdk part so I am not sure why it expects to find that? /Måns Den ons 5 juni 2019 kl 12:46 skrev Måns Zigher : > > When checking the build for lib

Re: [yocto] [Yocto][multilib] No Manifest file generated from: lib32-alsa-lib

2019-06-05 Thread Måns Zigher
When checking the build for lib32-alsa-lib there is no rpm package created deploy-rpms/armv7ahf_neon_mx8mm# ls lib32-alsa-conf-1.1.5-r0.armv7ahf_neon_mx8mm.rpm lib32-alsa-server-1.1.5-r0.armv7ahf_neon_mx8mm.rpm lib32-libasound2-1.1.5-r0.armv7ahf_neon_mx8mm.rpm lib32-libasound-dbg-1.1.5-r0.armv7ahf

Re: [yocto] fitImage kernel compression type

2019-06-05 Thread Måns Zigher
Have you looked at https://git.yoctoproject.org/cgit.cgi/poky/plain/meta/classes/kernel-fitimage.bbclass? I cannot see that there is an option for determining the compression. It appears as if it looks specifically for bin-file. I am no expert regarding fitimage format so I cannot say what the best

[yocto] fitImage kernel compression type

2019-06-05 Thread Pierluigi Greto
Hello everyone, I'm building an fitImage and I would like to set the kernel compression type. Yocto is automatically creating the linux.bin but I cannot find any variable to specify the kernel compression type. I would like to have a gzip compressed kernel. Is possible to specify the compressi

[yocto] [Yocto][multilib] No Manifest file generated from: lib32-alsa-lib

2019-06-05 Thread Måns Zigher
Hi, I am trying to build an SDK where I have multilib enabled in my local.conf but I am encountering this error message WARNING: strix-sdk-1.0-r0 do_populate_sdk: Manifest /workdir/builds/imx8mm/tmp/sstate-control/manifest-x86_64_x86_64-nativesdk-lib32-alsa-lib.package_write_rpm not found in mimx

[yocto] -vfp arm tuning missing in builds and WORKDIR

2019-06-05 Thread Dhanush K.S
Currently the SDK that is being built, builds successfully but does not contain the vfp arm tuning part included. Overriding the “TARGET_FPU” variable in the local.conf and setting it to *“vfp-neon”*, does reflect in the Build Configuration section, but that still has no difference in the SDK being

[yocto] [meta-gplv2][PATCH] elfutils: ignore new error from gcc-9

2019-06-05 Thread Martin Jansa
Signed-off-by: Martin Jansa --- recipes-devtools/elfutils/elfutils_0.148.bb | 4 1 file changed, 4 insertions(+) diff --git a/recipes-devtools/elfutils/elfutils_0.148.bb b/recipes-devtools/elfutils/elfutils_0.148.bb index a03b74e..1f07a28 100644 --- a/recipes-devtools/elfutils/elfutils_0.1