linux/poky.git/meta, branch yocto-2.2.2

uninative: Update to 1.7 uninative release

2017-09-06T15:54:37+00:00

This updates to a newer glibc and updates patchelf to include a bugfix to work with gold. (From OE-Core rev: a2ab288bd002ebb6e64d46e941fb122e1157ff49) (From OE-Core rev: 32d172c25072251d6cc7fdd40929d76b5f1f5059) Signed-off-by: Richard Purdie Signed-off-by: Armin Kuster Signed-off-by: Richard Purdie

yocto-uninative: Update to the 1.6 release

2017-09-06T15:54:37+00:00

This release includes fixes for Windows/Mingw support. (From OE-Core rev: b5f471b74b2da533abfad2601b221fa806fcf3b2) (From OE-Core rev: 267e10420cac19ac3c1194d32993c3407bdc90f6) Signed-off-by: Joshua Lock Signed-off-by: Ross Burton Signed-off-by: Richard Purdie Signed-off-by: Armin Kuster Signed-off-by: Richard Purdie

yocto-uninative: Update to the 1.5 release

2017-09-06T15:54:37+00:00

This upgrades to a version of patchelf which works on newer distros and doesn't inflate binaries in crazy ways. (From OE-Core rev: b857ec92564ee3f23adf88d2675d920aff13e141) (From OE-Core rev: 1496ae0ab32315537649dea7e5a22a16fae0a528) Signed-off-by: Richard Purdie Signed-off-by: Armin Kuster Signed-off-by: Richard Purdie

python3-native: Avoid use of getentropy/getrandom

2017-09-06T15:54:37+00:00

getentropy/random() is only available in glibc 2.25+ and uninative may relocate binaries onto systems that don't have this function. For now, force the code to the older codepaths until we can come up with a better solution for this kind of issue. (From OE-Core rev: 92bda0024d85ae78345665cc2f9646c9881ed61b) (From OE-Core rev: 2dc6ee0c520442418fa14cf3fe12b059209e9ab7) Signed-off-by: Richard Purdie

python-numpy: Fix issues with recent glibc versions

2017-09-06T15:53:39+00:00

Fix issues building on recent glibc versions (for python*-numpy-native). (From OE-Core rev: 08a46b2477c1ea0e76695b51b59dc1bb46b1b521) Signed-off-by: Richard Purdie

qemu: Backport a patch for recent glibc versions

2017-09-06T15:53:39+00:00

This fixes compile failures of qemu-native with new versions of glibc. Patch is taken from upstream. (From OE-Core rev: b1b7a46f0febe7ac17ec46ecdf88b4120a7d75c4) Signed-off-by: Richard Purdie

connman: Fix for CVE-2017-12865

2017-09-04T16:38:09+00:00

dnsproxy: Fix crash on malformed DNS response If the response query string is malformed, we might access memory pass the end of "name" variable in parse_response(). [YOCTO #11959] (From OE-Core rev: fb3e30e45eea2042fdb0b667cbc2c79ae3f5a1a9) (From OE-Core rev: 55a5a609e7c25fa3e62e1975a33a9cc10448165c) Signed-off-by: Sona Sarmadi Signed-off-by: Richard Purdie Signed-off-by: Sona Sarmadi Conflicts: meta/recipes-connectivity/connman/connman_1.33.bb Signed-off-by: Armin Kuster Signed-off-by: Richard Purdie

kernel, license, sstate, rootfs.py: Remove deploy directory README

2017-08-29T22:43:50+00:00

It isn't clear that the README_-_DO_NOT_DELETE_FILES_IN_THIS_DIRECTORY.txt file in the deploy directory warrants the complexity it brings elsewhere. Let's just remove it entirely. In particular, if two do_image_complete tasks run in parallel they risk both trying to put their image into ${DEPLOY_DIR_IMAGE} at the same time. Both will contain a README_-_DO_NOT_DELETE_FILES_IN_THIS_DIRECTORY.txt file. In theory this should be safe because "cp -alf" will just cause one to overwrite the other. Unfortunately, coreutils cp also has a race[1] which means that if one copy creates the file at just the wrong point the other will fail with: cp: cannot create hard link ‘..../tmp-glibc/deploy/images/pantera/README_-_DO_NOT_DELETE_FILES_IN_THIS_D.txt’ to +‘..../tmp-glibc/work/rage_against-oe-linux-gnueabi/my-own-image/1.0-r0/deploy-my-own-image-complete/README_-_DO_NOT_DELETE_FILES_IN_THIS_DIRECTORY.txt’: File exists [1] https://debbugs.gnu.org/cgi/bugreport.cgi?bug=25680 (From OE-Core rev: 71e9e88847d7000781642ea6187ebd8f40dfdcfe) (From OE-Core rev: 20c39fdbb25c1b1867709c5bfb3ae2baef249be9) Signed-off-by: Mike Crowe Signed-off-by: Ross Burton Signed-off-by: Richard Purdie

insane.bbclass: fix override handling in RDEPENDS QA

2017-08-29T15:50:54+00:00

The package_qa_check_rdepends() in insane.bbclass has incorrectly replace its localdata OVERRIDES value with the package name. Fixing it by appending the package name to the existing OVERRIDES value. This resolves RDEPENDS QA error when setting PACKAGECONFIG using a pn- override at local.conf. Cherry picked from master 60d28dd72daee235150ab6605cbf953f1ea691df and modified to work with older bitbake where 2nd parameter in localdata.getVar was mandatory. [YOCTO #11374] (From OE-Core rev: 15fabf4d6507d2a3f9b98ad56e822eba35950662) Signed-off-by: Gan Yau Wai Signed-off-by: Ross Burton Signed-off-by: Martin Jansa Signed-off-by: Armin Kuster Signed-off-by: Richard Purdie

icecc.bbclass: prevent nativesdk builds depending on target specific KERNEL_CC

2017-08-29T15:50:54+00:00

* without this we cause nativesdk-linux-libc-headers to depend on target specific KERNEL_CC (through icecc_get_tool -> icecc_is_kernel -> KERNEL_CC -> HOST_CC_KERNEL_ARCH -> TARGET_CC_KERNEL_ARCH -> TUNE_FEATURES(thumb) as shown by bitbake-diffsigs: OE qemux86@ ~/build/oe-core $ ls /OE/build/oe-core/tmp-glibc/sstate-diff/1499859497/qemu*/*sdk*/*/*do_configure.sigdata* /OE/build/oe-core/tmp-glibc/sstate-diff/1499859497/qemuarm/x86_64-nativesdk-oesdk-linux/nativesdk-linux-libc-headers/4.10-r0.do_configure.sigdata.3a9a423878d56524e0ee8e42eba1804f /OE/build/oe-core/tmp-glibc/sstate-diff/1499859497/qemux86/x86_64-nativesdk-oesdk-linux/nativesdk-linux-libc-headers/4.10-r0.do_configure.sigdata.401071dbaa88903ece37d35a47965ff2 OE qemux86@ ~/build/oe-core $ bitbake-diffsigs /OE/build/oe-core/tmp-glibc/sstate-diff/1499859497/qemu*/*sdk*/*/*do_configure.sigdata* basehash changed from 39774238b66763c598153132e87a2c1a to aa2d66e770bf533e312536eb0a401c4c Variable TARGET_CC_KERNEL_ARCH value changed from '${@bb.utils.contains('TUNE_FEATURES', 'thumb', '-mno-thumb-interwork-marm', '', d)} TUNE_FEATURES{thumb} = Set' to '' (From OE-Core rev: 6aa5dcc472e6be971a4cef06aab5c1c125367eca) Signed-off-by: Martin Jansa Signed-off-by: Armin Kuster Signed-off-by: Richard Purdie