linux/poky.git/meta/conf/bitbake.conf, branch uninative-1.9

nativesdk-glibc: Split glibc and libcrypt to use libxcrypt instead

2018-04-07T21:34:45+00:00

Fedora28[1] has decided to go ahead and use libxcrypt to replace libcrypt from glibc despite the change not having merged into glibc upstream yet. This breaks the use of uninative in OE on fedora28 since binaries there are now using new symbols only found in libxcrypt. libxcrypt is meant to be backwards compatible with libcrypt but not the reverse. Since this will impact OE in the next release cycle, this changes nativesdk only to use this new model and adds libxcrypt to work in that case. This allows us to build a uninative which is compatible with fedora28 and previous other OSes. In order to work, recipes will now need to depend on virtual/crypt where they use libcrypt since its now a separate library and we can't depend on it from glibc to preseve backwards compatibility since glibc needs to build first. For now, only the problematic nativesdk recipes have been fixed up. For target use, the default provider remains glibc for now. Assuming this change is merged into upstream glibc, we will need to roll this change out for the target but we will do this in the next release cycle when we can better deal with the resulting bugs. [1] https://fedoraproject.org/wiki/Changes/Replace_glibc_libcrypt_with_libxcrypt Original patch from Charles-Antoine Couret , tweaked by RP to add virtual provides, SkipRecipe for libxcrypt and other minor tweaks. (From OE-Core rev: c1573cb7faeb296fe7077a60d02443d5ed5bded0) Signed-off-by: Charles-Antoine Couret Signed-off-by: Richard Purdie

risc-v: Pin oldest kernel to 4.15 for the new kid

2018-03-15T13:27:19+00:00

(From OE-Core rev: fd3d98fd5690dab391c27a71e26f74e0f9a25f3a) Signed-off-by: Khem Raj Signed-off-by: Ross Burton Signed-off-by: Richard Purdie

bitbake.conf: Add xattr to DISTRO_FEATURES_NATIVE

2018-02-06T11:06:27+00:00

Commit db1f1adace58763c35774e3fdfeaac5c3ca646fd disabled 'xattr' from DISTRO_FEATURES when native packages are built, whereas for target packages it was retained. This changed eg. mtd-utils-native to build without extended attributes (capabilities) support from there on. Thus even setcap was called succesfully for a binary during pkg_postinst on build host, the capabilities did not exist on target rootfs due to now xattr-less host-side mkfs utility. Adding xattr to DISTRO_FEATURES_NATIVE restores previous behaviour, fixing the discontinuity in capability propagation to target device rootfs. (From OE-Core rev: 2ad3b8ae1c56a46bf14fc6bc4c34e4b3a568d741) Signed-off-by: Niko Mauno Signed-off-by: Ross Burton Signed-off-by: Richard Purdie

bitbake.conf: Add comm to HOSTTOOLS

2018-01-30T11:50:12+00:00

This mitigates following issues during u-boot do_compile() step -- otherwise, if comm is not available, they are quietly ignored: .../scripts/check-config.sh: line 33: comm: command not found .../scripts/check-config.sh: line 39: comm: command not found Since 'comm' is provided by coreutils package, adding it to HOSTTOOLS was considered a lower impact fix compared to adding coreutils-native buildtime dependency to u-boot recipe. (From OE-Core rev: 6dc33687de9edd4269cbaf85e30945771f61f313) Signed-off-by: Niko Mauno Signed-off-by: Richard Purdie

meta: don't use deprecated functions from utils.bbclass

2018-01-30T11:50:11+00:00

These functions were moved to meta/lib/oe in 2010 and the base_* functions in utils.bbclass were intended to be a short-term compatibility layer. They're still used in a few places, so update the callers to use the new functions. (From OE-Core rev: c97acbd034532895ce57c6717ed1b3ccc7900b0d) Signed-off-by: Ross Burton Signed-off-by: Richard Purdie

bitbake.conf: add STAMPS_DIR to BB_HASHBASE_WHITELIST

2018-01-29T08:49:50+00:00

This allows scripts/bitbake-whatchanged to calculate the dependency changes correctly since it needs to set different STAMPS_DIR during the comparation. (From OE-Core rev: 8547f1e29104b75299f1056524da4a058a029940) Signed-off-by: Ming Liu Signed-off-by: Richard Purdie

bitbake.conf: Set AUTOREV to have a vardepvalue

2018-01-06T22:32:22+00:00

If you have a recipe which does not include SRCPV in PV but does set SRCREV = "${AUTOREV}" and you run do_fetch, then change the repo to a new commit then run do_unpack, do_unpack will fail since the new commit doesn't exist in the repo that was fetched. The problem is the revision chosen is not represented in the do_fetch task hash. It if were, the fetch would rerun first and the commit would be present. It works when PV includes SRCPV since that does contain the chosen commit from the AUTOREV. The solution is to include the SRCPV value into the representation of AUTOREV used for checksum calculation purposes. Add a selftest for this issue. (From OE-Core rev: 7b8ee9285a197784d51e339f1603240f49435846) Signed-off-by: Richard Purdie

bitbake.conf: set more conservative default for IMAGE_FSTYPES_DEBUGFS

2017-12-10T22:45:19+00:00

Setting IMAGE_FSTYPES_DEBUGFS to the same value as IMAGE_FSTYPES can lead to creating a large number of DEBUGFS filesystem images, many of which may not make much sense (or may not even be buildable). (From OE-Core rev: a41f7cdf0cbc56a283d5c845c36d88a0208bf386) Signed-off-by: Andre McCurdy Signed-off-by: Ross Burton Signed-off-by: Richard Purdie

bitbake.conf: Adds ipv6 to DISTRO_FEATURES_NATIVE

2017-10-16T22:53:45+00:00

Before we introduced DISTRO_FEATURES_NATIVE on commit: db1f1adace58763c35774e3fdfeaac5c3ca646fd ipv6 was enabled by default on DISTRO_FEATURES via DISTRO_FEATURES_LIBC hence for example python-native was built with ipv6 support. After this, ipv6 was automatically disabled on DISTRO_FEATURES. On some packages (python) this may cause errors when they try to download something on their do_compile stage. This patch adds ipv6 to DISTRO_FEATURES_NATIVE leaving it as it was before, to avoid errors like the one mentioned above [YOCTO #11978] (From OE-Core rev: a09184bf47323b63d9548d17cc1e4e694cb605a9) Signed-off-by: Alejandro Hernandez Signed-off-by: Richard Purdie

bitbake.conf: add ssh to HOSTTOOLS_NONFATAL

2017-10-16T22:52:44+00:00

We changed to make tools required by testimage to be included conditionally. This resulted in users who use ssh for git fetching having failures. Add ssh to HOSTTOOLS_NONFATAL to make things work for the above situation. [YOCTO #12227] (From OE-Core rev: 50e7619aebae5351e9a41fe1b909a31b9e383f0a) Signed-off-by: Chen Qi Signed-off-by: Ross Burton Signed-off-by: Richard Purdie