linux/poky.git/meta/conf, branch 2.5_M2

tcmode-default.inc: drop preferred version of gzip-native

2018-01-31T17:01:20+00:00

* gzip was recently upgraded from 1.8 to 1.9, now all the builds show: NOTE: preferred version 1.8 of gzip-native not available (for item gzip-native) NOTE: versions of gzip-native available: 1.9 * drop the setting, because nobody is probably going to use older gzip-native than 1.4 when there is only 1.9 available in oe-core (From OE-Core rev: a0988c3374e964170d1d24fc230306b887432d31) Signed-off-by: Martin Jansa Signed-off-by: Ross Burton Signed-off-by: Richard Purdie

tcmode-default.inc: bump LINUXLIBCVERSION to 4.14%

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

* linux-libc-headers were updated without updating PREFERRED_VERSION causing following messages being shown in every single build: NOTE: preferred version 4.12% of nativesdk-linux-libc-headers not available (for item nativesdk-linux-libc-headers) NOTE: versions of nativesdk-linux-libc-headers available: 4.14.13 NOTE: preferred version 4.12% of linux-libc-headers not available (for item linux-libc-headers) NOTE: versions of linux-libc-headers available: 4.14.13 NOTE: preferred version 4.12% of linux-libc-headers not available (for item linux-libc-headers-dev) NOTE: versions of linux-libc-headers available: 4.14.13 NOTE: preferred version 4.12% of nativesdk-linux-libc-headers not available (for item nativesdk-linux-libc-headers-dev) (From OE-Core rev: df07a95f270492dba9fa04f917617b1aaee123b9) Signed-off-by: Martin Jansa 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

maintainers: update

2018-01-19T12:37:13+00:00

Some people are no longer working on oe-core, so reassign their packages. (From OE-Core rev: d4c7091362569af08ea67d57925ffb91579ce3bd) Signed-off-by: Ross Burton Signed-off-by: Richard Purdie

tune-i686: Add new tune for better support of 686-class CPUs.

2018-01-18T12:50:37+00:00

There isn't currently any tune available for i686 x86 optimizations. The tune for i586 doesn't enable i686 specific optimizations, and the one for core2 enables things that won't work on a i686 CPU (like SSE3). Make the tune for core2 inherits from this one and move there the setting of X86ARCH32. (From OE-Core rev: c08f76ba0654e43074b6b964f728765918dbfb09) Signed-off-by: Carlos Alberto Lopez Perez Signed-off-by: Richard Purdie

maintainers.inc: add missing entries for gst-validate, gst-examples and meson

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

(From OE-Core rev: ad9a2ed069d6521710a73f942ea59ef91846f681) Signed-off-by: Alexander Kanavin 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

maintainers.inc: assign python recipes to Derek Straka

2018-01-05T11:55:35+00:00

(From OE-Core rev: 6072fa8b0d5c80d24e74510223838f7ccacbf3f1) Signed-off-by: Alexander Kanavin Signed-off-by: Richard Purdie