Re: [OE-core] [PATCH v2 2/3] image_overlay.bbclass: Add possibility to install overlays to image

rdeps] += "OVERLAY_ROOT_DIRS" + +SSTATETASKS += "do_install_overlay" Except this isn't an sstate task? There is no setscene task variant of the main task. There are no sstate variables set either... Cheers, Richard -- Logo <http://www.smile.fr/> 20 rue des Jardins 92600 A

Re: [OE-core] [PATCH v2 0/3] Permit to install files from an overlay in images recipes

ation package" can only add new conf files, it can't alter existing files. Regards Jérémy -- Logo <http://www.smile.fr/> 20 rue des Jardins 92600 Asnières-sur-Seine www.smile.fr <http://www.smile.fr/> *Jérémy ROSEN* Architecte technique Email : jeremy.ro...@smile.fr <mai

Re: [OE-core] [PATCH v2] scripts: add new script 'native'

"native" might be a bit too generic... could I suggest oe_native-run or bitbake-native ? something that says it's yocto-galaxy specific and can be autocompleted with a reasonable prefix... Jérémy Rosen On 30/09/2016 17:02, Ed Bartosh wrote: Added 'native' convenience shell scr

Re: [OE-core] [PATCH v2 0/8] Fix BUILD_* family of variables

to be accepted to allow backporting, maybe it's worth rushing it... Ross On 12 September 2016 at 16:19, Jérémy Rosen <jeremy.ro...@smile.fr <mailto:jeremy.ro...@smile.fr>> wrote: Any news ? On 07/09/2016 11:08, Jérémy Rosen wrote: The BUILD_* family of variables al

Re: [OE-core] [PATCH v2 0/8] Fix BUILD_* family of variables

Any news ? On 07/09/2016 11:08, Jérémy Rosen wrote: The BUILD_* family of variables allow the user to specify the name of the host compiler to use at build time. This feature is particularly important for long term maintainance. Future versions of gcc might not be compatible with old yocto

Re: [OE-core] [PATCH 0/3] systemd: add support to manage user units

It's probably worth updating the documentation too... this is a usefull feature and it deserves the exposure Regards Jeremy Rosen On 07/09/2016 11:22, Chen Qi wrote: The following changes since commit 55bb6816aca39bfa25d4f7e2158a57a5f0ac1cca: oeqa.buildperf: correct globalres time

[OE-core] [PATCH v2 8/8] libpcre: explicitely specify CCLD_FOR_BUILD for this recipe

libpcre uses CCLD_FOR_BUILD as the name of the host command to use for linking. This is not a standard autotools symbol but particular to this recipe. We need to set it explicitely Signed-off-by: Jérémy Rosen <jeremy.ro...@smile.fr> --- meta/recipes-support/libpcre/libpcre_8.39.bb | 2 ++

[OE-core] [PATCH v2 6/8] glibc: remove hard-coded reference to gcc -E

Signed-off-by: Jérémy Rosen <jeremy.ro...@smile.fr> --- meta/recipes-core/glibc/glibc/0001-locale-fix-hard-coded-reference-to-gcc-E.patch | 39 +++ meta/recipes-core/glibc/glibc_2.24.bb | 3 ++- 2 files c

[OE-core] [PATCH v2 7/8] rpm: manually cleanup sysck

down the line This patch manually removes the files from the recipe. Signed-off-by: Jérémy Rosen <jeremy.ro...@smile.fr> --- meta/recipes-devtools/rpm/rpm_5.4.16.bb | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/meta/recipes-devtools/rpm/rpm_5.4.16.bb b/meta/recipes-de

[OE-core] [PATCH v2 4/8] busybox: allow overriding compiler name in KConfig

The KConfig infrastructure needs to build HOST binaries in order to provide its infratstructure. Yocto needs to force the HOSTCC and HOSTCPP variables to BUILD_CC and BUILD_CPP to make sure that the proper compiler is used when compiling host binaries --- meta/recipes-core/busybox/busybox.inc | 2

[OE-core] [PATCH v2 5/8] sanity: fix hardcoded references to gcc

Signed-off-by: Jérémy Rosen <jeremy.ro...@smile.fr> --- meta/classes/sanity.bbclass | 14 +++--- 1 file changed, 7 insertions(+), 7 deletions(-) diff --git a/meta/classes/sanity.bbclass b/meta/classes/sanity.bbclass index 202b5db..f17e2d4 100644 --- a/meta/classes/sanity.bbclass

[OE-core] [PATCH v2 3/8] linux-libc-headers: allow overriding compiler name in KConfig

The KConfig infrastructure needs to build HOST binaries in order to provide its infratstructure. Yocto needs to force the HOSTCC and HOSTCPP variables to BUILD_CC and BUILD_CPP to make sure that the proper compiler is used when compiling host binaries ---

[OE-core] [PATCH v2 0/8] Fix BUILD_* family of variables

o modify yocto's builders to use the BUILD_* variable in order to have some early warning wrt gcc polution in recipes, but seeing the various recipes I had to patch, I would expect such a change to trigger a high number of build failures. Jérémy Rosen (8): cross: export CC family from BUILD_* for

[OE-core] [PATCH v2 1/8] cross: export CC family from BUILD_* for cross compilers

. Signed-off-by: Jérémy Rosen <jeremy.ro...@smile.fr> --- meta/classes/cross.bbclass | 12 1 file changed, 12 insertions(+), 0 deletions(-) diff --git a/meta/classes/cross.bbclass b/meta/classes/cross.bbclass index 81d1c9d..8d1e779 100644 --- a/meta/classes/cross.bbclass +++ b/meta/c

[OE-core] [PATCH v2 2/8] linux-yocto: allow overriding compiler name in KConfig

The KConfig infrastructure needs to build HOST binaries in order to provide its infratstructure. Yocto needs to force the HOSTCC and HOSTCPP variables to BUILD_CC and BUILD_CPP to make sure that the proper compiler is used when compiling host binaries --- meta/classes/kernel.bbclass | 1 + 1 file

Re: [OE-core] [PATCH 1/8] [autotools] export CCLD_FOR_BUILD

On 24/08/2016 21:56, Burton, Ross wrote: On 24 August 2016 at 12:28, Jérémy Rosen <jeremy.ro...@smile.fr <mailto:jeremy.ro...@smile.fr>> wrote: ok, so CC_FOR_BUILD seems to be a common convention and CCLD_FOR_BUILD seems only used by our patch for pcre. Fixing i

Re: [OE-core] [PATCH 3/8] [rpm] force a configure before make distclean

On 24/08/2016 16:13, Mark Hatle wrote: Make often has a rule looking at the time stamp of specific files and re-running specific autotools if they are 'out of date'. That COULD be the cause of the errant call to gcc? that would make sense... I have not observed the above occurring -- but

Re: [OE-core] [PATCH 1/8] [autotools] export CCLD_FOR_BUILD

(Adding original patch author to mail) On 24/08/2016 13:05, Jérémy Rosen wrote: [...] +export CCLD_FOR_BUILD = "${BUILD_CCLD}” if its used by just one recipe then its not worth abstracting it out. Perhaps fixing https://github.com/openembedded/openembedded-core/blob/master/meta/re

Re: [OE-core] [PATCH 1/8] [autotools] export CCLD_FOR_BUILD

On 24/08/2016 02:50, Khem Raj wrote: On Aug 23, 2016, at 12:25 AM, Jérémy Rosen <jeremy.ro...@smile.fr> wrote: The autotools class already export most *_FOR_BUILD from bitbake's BUILD_* variables. Somehow the variable CCLD_FOR_BUILD was missing At least libpcre uses that va

Re: [OE-core] [PATCH 7/8] [sanity] fix hardcoded references to gcc

On 23/08/2016 17:40, Jérémy Rosen wrote: On 23/08/2016 17:11, Burton, Ross wrote: On 23 August 2016 at 15:53, Burton, Ross <ross.bur...@intel.com <mailto:ross.bur...@intel.com>> wrote: I think this is because BUILD_CC by default contains whitespace, and bb.utils

Re: [OE-core] [PATCH 5/8] [linux-libc-headers] allow overriding compiler name in KConfig

[...] If this is broken, it needs to be fixed upstream. I agree. now a days we have more than gcc available as system C compiler perhaps your patch might be upstream worthy. As stated elsewhere, I now have a proper way to override the variables without patching the build system. V2 of

Re: [OE-core] [PATCH 3/8] [rpm] force a configure before make distclean

On 23/08/2016 19:16, Mark Hatle wrote: On 8/23/16 11:54 AM, Burton, Ross wrote: On 23 August 2016 at 08:25, Jérémy Rosen <jeremy.ro...@smile.fr <mailto:jeremy.ro...@smile.fr>> wrote: - ( cd ${S}/syck ; set +e ; rm -- -l* ; make distclean ) || : + ( cd ${S}/s

Re: [OE-core] [PATCH 7/8] [sanity] fix hardcoded references to gcc

On 23/08/2016 17:11, Burton, Ross wrote: On 23 August 2016 at 15:53, Burton, Ross > wrote: I think this is because BUILD_CC by default contains whitespace, and bb.utils.which looks for "gcc ". I added a strip() to

Re: [OE-core] [PATCH 2/8] [cross] export CC family from BUILD_* for cross compilers

correctly set and they will not honor the host compiler name provided by the BUILD_* variables. Signed-off-by: Jérémy Rosen <jeremy.ro...@smile.fr <mailto:jeremy.ro...@smile.fr>> --- meta/classes/cross.bbclass | 12 1 file changed, 12 in

Re: [OE-core] [PATCH 8/8] [glibc] remove hard-coded reference to gcc -E

On 23/08/2016 16:03, Burton, Ross wrote: On 23 August 2016 at 08:25, Jérémy Rosen <jeremy.ro...@smile.fr <mailto:jeremy.ro...@smile.fr>> wrote: +-open F, "cat C-translit.h.in <http://C-translit.h.in> | gcc -E - |" || die "Cannot preprocess

Re: [OE-core] [PATCH 4/8] [linux-yocto] allow overriding compiler name in KConfig

On 23/08/2016 15:41, Bruce Ashfield wrote: On Tue, Aug 23, 2016 at 9:36 AM, Bruce Ashfield <bruce.ashfi...@gmail.com <mailto:bruce.ashfi...@gmail.com>> wrote: On Tue, Aug 23, 2016 at 3:25 AM, Jérémy Rosen <jeremy.ro...@smile.fr <mailto:jeremy.ro..

Re: [OE-core] [PATCH 4/8] [linux-yocto] allow overriding compiler name in KConfig

On 23/08/2016 15:36, Bruce Ashfield wrote: On Tue, Aug 23, 2016 at 3:25 AM, Jérémy Rosen <jeremy.ro...@smile.fr <mailto:jeremy.ro...@smile.fr>> wrote: The KConfig infrastructure hardwires the compiler name to gcc, which breaks the BUILD_CC feature. This is needed eve

[OE-core] [PATCH 4/8] [linux-yocto] allow overriding compiler name in KConfig

The KConfig infrastructure hardwires the compiler name to gcc, which breaks the BUILD_CC feature. This is needed even when cross compiling because make *config rely on the kconfig infrastructure --- meta/recipes-kernel/linux/linux-yocto.inc

[OE-core] [PATCH 2/8] [cross] export CC family from BUILD_* for cross compilers

. Signed-off-by: Jérémy Rosen <jeremy.ro...@smile.fr> --- meta/classes/cross.bbclass | 12 1 file changed, 12 insertions(+), 0 deletions(-) diff --git a/meta/classes/cross.bbclass b/meta/classes/cross.bbclass index 81d1c9d..8d1e779 100644 --- a/meta/classes/cross.bbclass +++ b/meta/c

[OE-core] [PATCH 8/8] [glibc] remove hard-coded reference to gcc -E

Signed-off-by: Jérémy Rosen <jeremy.ro...@smile.fr> --- meta/recipes-core/glibc/glibc/0001-locale-fix-hard-coded-reference-to-gcc-E.patch | 23 +++ meta/recipes-core/glibc/glibc_2.24.bb | 6 ++ 2 files changed, 25 inse

[OE-core] [PATCH 6/8] [busybox] allow overriding compiler name in KConfig

The KConfig infrastructure hardwires the compiler name to gcc, which breaks the BUILD_CC feature. This is needed even when cross compiling because make *config rely on the kconfig infrastructure --- meta/recipes-core/busybox/busybox.inc | 5 +

[OE-core] [PATCH 7/8] [sanity] fix hardcoded references to gcc

Signed-off-by: Jérémy Rosen <jeremy.ro...@smile.fr> --- meta/classes/sanity.bbclass | 14 +++--- 1 file changed, 7 insertions(+), 7 deletions(-) diff --git a/meta/classes/sanity.bbclass b/meta/classes/sanity.bbclass index 202b5db..f17e2d4 100644 --- a/meta/classes/sanity.bbclass

[OE-core] [PATCH 5/8] [linux-libc-headers] allow overriding compiler name in KConfig

The KConfig infrastructure hardwires the compiler name to gcc, which breaks the BUILD_CC feature. This is needed even when cross compiling because make *config rely on the kconfig infrastructure --- meta/recipes-kernel/linux-libc-headers/linux-libc-headers.inc

[OE-core] [PATCH 0/8] Fix BUILD_* family of variables

e actual work. It would also be interesting to modify yocto's builders to use the BUILD_* variable in order to have some early warning wrt gcc polution in recipes, but seeing the various recipes I had to patch, I would expect such a change to trigger a high number of build failures. Jérémy Rose

[OE-core] [PATCH 1/8] [autotools] export CCLD_FOR_BUILD

The autotools class already export most *_FOR_BUILD from bitbake's BUILD_* variables. Somehow the variable CCLD_FOR_BUILD was missing At least libpcre uses that variable and will use gcc instead of BUILD_CCLD to link binaries Signed-off-by: Jérémy Rosen <jeremy.ro...@smile.fr> --- meta/c

[OE-core] [PATCH 3/8] [rpm] force a configure before make distclean

distclean succeeds Signed-off-by: Jérémy Rosen <jeremy.ro...@smile.fr> --- meta/recipes-devtools/rpm/rpm_5.4.16.bb | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/meta/recipes-devtools/rpm/rpm_5.4.16.bb b/meta/recipes-devtools/rpm/rpm_5.4.16.bb index 84adef6..6b82c6d

Re: [OE-core] what means IMAGE_ROOTFS_EXTRA_SPACE_append += "+ 3000000"?

On 17/08/2016 16:01, Robert P. J. Day wrote: as in, what's with the "+" in that "+ 300" value? i've never seen that before, and i took a quick look under classes/ to try to figure out what's happening, but i'm still confused. you're reading too much into this "+ 300" will append

[OE-core] [PATCH 1/1] init-live : make it easier to add custom boot targets

in init.sh were hardcoded to install and install-efi this patch checks if a shell script with the same name as the label is available instead of using a hardcoded list. Any recipe can add such file and this provide a new boot target to the live image Signed-off-by: Jérémy Rosen <jeremy