linux/poky.git/meta/classes, branch pyro

populate_sdk_base: depend on nativesdk-glibc-locale

2018-04-02T16:06:24+00:00

If we're building a SDK and we're using glibc so may be installing locales, add a build-dependency on natiesdk-glibc-locale so the locales we need will exist. (From OE-Core rev: 8d6869a0a89d8cf3c6e57723fab2750ba2c885db) (From OE-Core rev: 19fce2a6f76227de88e267f65f0e124645ea280e) Signed-off-by: Ross Burton Signed-off-by: Richard Purdie

populate_sdk: install UTF-8 locales in SDKs

2018-04-02T16:06:24+00:00

As glibc 2.27 can't read older locale-archives, SDKs using glibc 2.27 on hosts using glibc earlier than 2.27 won't be able to find any locales, so bitbake won't start and Python can't use UTF-8. So by default install all locales into the SDK. Special-case Extensible SDKs by installing no locales as they ship glibc in a buildtools, and that will have the locales. Locale installation requires cross-localedef, so add that to DEPENDS. Also remove the explicit en_US addition in buildtools-tarball as it is now redundant. (From OE-Core rev: 96896568d197cd06302713c24c0f7d91bfaea6c1) (From OE-Core rev: af9eb2ef36cb5bfd87ea61ff3390949810097c9b) Signed-off-by: Ross Burton Signed-off-by: Richard Purdie

uninative: Add compatiblity version check

2018-03-15T22:47:53+00:00

If glibc is newer on the host than in uninative, the failure mode is pretty nasty for clusters where the sstate is shared, including the Yocto Project autobuilder. This check aborts the use of uninative in such scenarios where a newer glibc version appears and avoids corruption of sstate caches. We use ldd to check the glibc version since that is included in libc-bin (or equivalent) which locales use so it should always be present. (From OE-Core rev: 8147911a951c7b0508f9c2aef93480d65b4362c0) Signed-off-by: Richard Purdie

testimage: Pass the logger into OERuntimeTestContextExecutor.getTarget()

2018-03-04T11:11:59+00:00

I have no idea why we didn't do this but it means the code has nowhere to log to unless we do this. This means we can then use the logger to log data to the task logs. (From OE-Core rev: 1054965a2d44df2617127c0c47e34adc62c1bf4d) (From OE-Core rev: 93aaa0cf4f792f76d76f9f79be7fbbe59d01e910) Signed-off-by: Richard Purdie Signed-off-by: Armin Kuster Signed-off-by: Richard Purdie Signed-off-by: Armin Kuster Signed-off-by: Richard Purdie

package_rpm.bbclass: Fix matching of architecture independent packages

2018-03-04T11:11:58+00:00

OE-Core changes the architecture independent RPM packages to use "noarch" instead of "all". This change has been included in the commit below: ,---- | commit 341810aff923ace6b1cc1e15e19383c4f8773b51 | Author: Alexander Kanavin | Date: Mon Jan 9 16:37:28 2017 +0200 | | package_rpm.bbclass: make architecture-independent .rpm packages | "noarch" instead of "all" | | Too many places in dnf/rpm4 stack make that assumption; let's not | fight against it. | | Signed-off-by: Alexander Kanavin `---- This is causing problems with machines that has "all" inside the machine name. Reported-by: Alexandru Palalau (From OE-Core rev: 445ac7b3198885c67622b4303b010a85c3e3e61e) Signed-off-by: Otavio Salvador Signed-off-by: Ross Burton (cherry picked from commit 3e4ddeab65d4d2e4aaf03d442c2a1a8c7a2ce8a2) Signed-off-by: Armin Kuster Signed-off-by: Richard Purdie

image_types_wic.bbclass: Ensure '-c image_wic' works

2018-03-04T11:11:58+00:00

The 'wic' image may use files which has been deployed (e.g in do_deploy) for some partitions that may need to be copied in a specific partition or filesystem (e.g a bootloader). When using 'bitbake -c image_wic', from a clean build, the contents of do_deploy must also be available so we need to ensure all do_deploy of the image dependencies has been complete. Reported-by: Fabio Berton (From OE-Core rev: 5e2a541f80e0f69ae00dfd96e50d2792750730cd) Signed-off-by: Otavio Salvador Signed-off-by: Richard Purdie (cherry picked from commit f387c28640cbb209b8a8ed5734b21c754d9f7663) Signed-off-by: Armin Kuster Signed-off-by: Richard Purdie

distutils-base.bbclass: Do not use -pie with hardening

2018-03-04T11:11:58+00:00

Fix build when PIE is turned on. It tries to build .so file using -pie and -shared flags together because its doing compile and link in same step CFLAGS and LDFLAGS are combined and does not work, ending in errors e.g. | /mnt/a/oe/build/tmp/work/cortexa7t2hf-neon-vfpv4-bec-linux-musleabi/python-pygpgme/0.3-r0/recipe-sysroot/usr/l ib/Scrt1.o: In function `_start_c': | /usr/src/debug/musl/1.1.16+gitAUTOINC+179766aa2e-r0/git/crt/crt1.c:17: undefined reference to `main' | collect2: error: ld returned 1 exit status This error while cryptic is due to the fact that we are building a shared library but also pass -pie flag to the link step after specify LDHSARED ( which is -shared linker flags ) we can not use -pie when doing shared libs. This is true for all the python modules inheriting setup tools Disable the pie flags thusly for all modules using setuptools since this setting is done in setuptools makefiles which are then used during module compiles Backport notes: In master, this commit is reverted in master in favor of using GCCPIE = "--enable-default-pie" in security_flags.inc. However, backporting that change introduces many merge conflicts and will be a serious maintenance issue, so I think it's safest to just backport this small change, which fixes build failures in python-cffi and likely other recipes. For completeness, this is the list of commits in OE-core master that will supersede this change: - 1c7e195c94764d680a12a49b870f04cd58860f81 "gcc: Introduce a knob to configure gcc to default to PIE" - e93765ffb5718b0fce84f0b8123963176dea95e4 "security_flags.inc: Delete pinnings for SECURITY_NO_PIE_CFLAGS" - fcfe6d4ab4460f8358e13023022a5e909941ca93 distutils,setuptools: Delete use of SECURITY_NO_PIE_CFLAGS (From OE-Core rev: 739c69e8eb464d184ef652e7e7a4d4b234a5b5f9) Signed-off-by: Khem Raj Signed-off-by: Ross Burton Signed-off-by: Martin Kelly Signed-off-by: Armin Kuster Signed-off-by: Richard Purdie

populate_sdk_ext: Set cleandirs correctly

2018-01-22T10:40:08+00:00

The current conflicting use of SDKDEPLOYDIR causes a race between do_populate_sdk and do_populate_sdk_ext potentially causing the SDK to either go missing or the build to fail. (From OE-Core rev: 2c61e60cc5fe635774e88c1e34646a32a9ad918b) Signed-off-by: Richard Purdie

lib/oe/package_manager/sdk: Ensure do_populate_sdk_ext and do_populate_sdk repos don't conflict

2018-01-22T10:40:08+00:00

(From OE-Core rev: c9c0927bb6e71253cbdd5b6b780dca829526e1d8) (From OE-Core rev: a18942b0b3b848ccfa4bc50c56a565c279da9d74) Signed-off-by: Richard Purdie

insane: consider INSANE_SKIP without package-specifier too

2018-01-20T22:52:58+00:00

this is needed for the updated linux-firmware as it needs this INSANE_SKIP support (From OE-Core rev: 618093c6b7c919f25094f56b82610bee7c97f99f) Signed-off-by: Ross Burton (cherry picked from commit 604939186cc08ab0429ebe00f3e32661847f0cf0) Adjusted for pyro context Signed-off-by: Armin Kuster Signed-off-by: Richard Purdie