summaryrefslogtreecommitdiffstats
Commit message (Collapse)AuthorAgeFilesLines
* binutils: Enable threading when gold is enabled and is not default linkerKhem Raj2017-03-171-1/+1
| | | | | | | | | | | | Currently we enable threaded linking feature of gold linker only when its used as default ld. There is no need to restrict it when its not default linker either. As long as gold is enabled, which is the case here, we should be able to do threaded linking. (From OE-Core rev: 759eed2b02e0a7b5c8b19d4b087d9151c009eed4) Signed-off-by: Khem Raj <raj.khem@gmail.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* go: Fix packaging for target goKhem Raj2017-03-171-7/+1
| | | | | | | | | | We need all packaging tasks when building go for target (From OE-Core rev: 8f504a7737d5e6be6ec61f9ce8728a2c74102a8a) Signed-off-by: Khem Raj <raj.khem@gmail.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* mesa-gl: Drop MESA_CRYPTO from PACKAGECONFIGKhem Raj2017-03-171-1/+1
| | | | | | | | | with mesa 17 crypto packageconfig has been removed (From OE-Core rev: 7df24c84999048f863428f4e442922e60ce776a5) Signed-off-by: Khem Raj <raj.khem@gmail.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* mesa: Contain configure search for llvmKhem Raj2017-03-171-1/+1
| | | | | | | | | | | | | | | | | | | | | Configure has an unbridled check for llvm and when distro provided llvm is installed on build host it will use that from /usr/bin to poke for llvm libs and configs. This would result in a subtle errors however do_qa_configure catches it as a host include/lib contamination during configure checks ERROR: mesa-gl-2_17.0.1-r0 do_configure: This autoconf log indicates errors, it looked at host include and/or library paths while determining system capabilities. Rerun configure task after fixing this. This is correct because when configure detects build host provided llvm then it add the include/lib paths to compiler cmdline which are looking into /usr/include and /usr/lib (From OE-Core rev: df53927b9c07bc45ce8a756217c07ce306ed5bbe) Signed-off-by: Khem Raj <raj.khem@gmail.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* package_manager: fix "exlcude" vs. "exclude" typoPaul Gortmaker2017-03-171-1/+1
| | | | | | | | | | | | | | | | | | | | | Which results in: -------------------------------- 0557: package_exclude = self.d.getVar('PACKAGE_EXCLUDE') *** 0558: exclude_pkgs = (bad_recommendations.split() if bad_recommendations else []) + (package_exlcude.split() if package_exclude else []) 0559: 0560: output = self._invoke_dnf((["--skip-broken"] if attempt_only else []) + 0561: (["-x", ",".join(exclude_pkgs)] if len(exclude_pkgs) > 0 else []) + 0562: (["--setopt=install_weak_deps=False"] if self.d.getVar('NO_RECOMMENDATIONS') == 1 else []) + Exception: NameError: name 'package_exlcude' is not defined ERROR: cube-builder-initramfs-1.0-r0 do_rootfs: Function failed: do_rootfs --------------------------------- Cc: Alexander Kanavin <alexander.kanavin@linux.intel.com> (From OE-Core rev: cee1bdc09f4bbfedcd7cac06b48ba9d195c29e62) Signed-off-by: Paul Gortmaker <paul.gortmaker@windriver.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* kexec-tools: Add patches to enable format-securityJussi Kukkonen2017-03-174-1/+123
| | | | | | | | | Also remove the override from security_flags.inc (From OE-Core rev: 33d084a66a371fb10e26a0a23c639c69ddd3f1e5) Signed-off-by: Jussi Kukkonen <jussi.kukkonen@intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* cmake: Backport fix to enable -Wformat-securityJussi Kukkonen2017-03-173-1/+34
| | | | | | | | | | Backport build fix that removes -Wformat-security for specific tests. Enable "-Wformat-security" for cmake in security_flags.inc. (From OE-Core rev: b00f9c77ebd211578ba133c28abcbc5752305e25) Signed-off-by: Jussi Kukkonen <jussi.kukkonen@intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* sysklogd: use update-alternatives for more manpagesPaul Gortmaker2017-03-171-0/+3
| | | | | | | | | | | | To fix: file /usr/share/man/man8/syslogd.8 conflicts between attempted installs of inetutils-doc-1.9.4-r0.core2_64 and sysklogd-doc-1.5.1-r0.core2_64 (From OE-Core rev: d08cfe3d3de01c529dda1a60f42870dd3132c256) Signed-off-by: Paul Gortmaker <paul.gortmaker@windriver.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* net-tools: use update-alternatives for more manpagesPaul Gortmaker2017-03-171-1/+2
| | | | | | | | | | | | To fix: file /usr/share/man/man1/dnsdomainname.1 conflicts between attempted installs of inetutils-doc-1.9.4-r0.core2_64 and net-tools-doc-1.60+26-r0.core2_64 (From OE-Core rev: 412d6b31b23b30f71b8acf2ecd37463f770cd8be) Signed-off-by: Paul Gortmaker <paul.gortmaker@windriver.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* util-linux: use update-alternatives for more manpagesPaul Gortmaker2017-03-171-1/+3
| | | | | | | | | | | | | | | | | To fix: file /usr/share/man/man1/eject.1 conflicts between attempted installs of util-linux-doc-2.29.1-r0.core2_64 and eject-doc-2.1.5-r1.core2_64 and file /usr/share/man/man1/logger.1 conflicts between attempted installs of util-linux-doc-2.29.1-r0.core2_64 and inetutils-doc-1.9.4-r0.core2_64 (From OE-Core rev: a65e69d006bceacb042b377f2cd0dd8a3e72ea62) Signed-off-by: Paul Gortmaker <paul.gortmaker@windriver.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* which: fix it so the manpage will respect alternativesPaul Gortmaker2017-03-172-0/+6
| | | | | | | | | | | | To fix: file /usr/share/man/man1/which.1 conflicts between attempted installs of debianutils-doc-4.8.1-r0.core2_64 and which-doc-2.21-r3.core2_64 (From OE-Core rev: ba304046307cd741694b25215b562d5f05c9c7a5) Signed-off-by: Paul Gortmaker <paul.gortmaker@windriver.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* gdb: don't bundle bfd.info -- leave that to binutils.Paul Gortmaker2017-03-171-1/+2
| | | | | | | | | | | | | | | | We see: file /usr/share/info/bfd.info conflicts between attempted installs of gdb-doc-7.12.1-r0.core2_64 and binutils-doc-2.28-r0.core2_64 You can't really have gdb and not binutils, so there is no need to do alternatives here ; just clobber the one from gdb and let the binutils one be the default. (From OE-Core rev: 19a825a578e2e705e5502982b787cff54d021359) Signed-off-by: Paul Gortmaker <paul.gortmaker@windriver.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* dnf: add /usr/bin/dnf symlink that points to /usr/bin/dnf-2Alexander Kanavin2017-03-173-3/+11
| | | | | | | | | | | All documentation refers to dnf binary as 'dnf' yet make install does not create one - it's done by Fedora's spec file when building the rpm. Let's replicate this behavior. (From OE-Core rev: 456c4a8ffc9a292d7a3e036d92baf4a8f14d1f45) Signed-off-by: Alexander Kanavin <alexander.kanavin@linux.intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* selftest/signing.py: verify that images can be created from signed packagesAlexander Kanavin2017-03-171-0/+8
| | | | | | | (From OE-Core rev: e53b93181ea1723ddeeb75c4195e9412e64721c0) Signed-off-by: Alexander Kanavin <alexander.kanavin@linux.intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* lib/oe/package_manager: import rpm signing key to rpmdbMarkus Lehtonen2017-03-171-2/+10
| | | | | | | | | | | | | Import the gpg key used in rpm signing into rpmdb. This makes it possible again to create images when rpm signing is enabled. Also, instruct dnf to enforce signature check if rpm signing is enabled. (From OE-Core rev: f30c1653cc5ef9daf594cbd3faad329b9fa08ab7) Signed-off-by: Markus Lehtonen <markus.lehtonen@linux.intel.com> Signed-off-by: Alexander Kanavin <alexander.kanavin@linux.intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* rpm: add support for remote package feeds via PACKAGE_FEED_URIS variableAlexander Kanavin2017-03-173-1/+60
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | I've used a previous patch (which was never merged) by Humberto Ibarra <humberto.ibarra.lopez@intel.com> as a model for how to do runtime testing of this feature (e.g. we need to boot an image, run dnf on it, and check that it is indeed able to access the remote repo over http). Here's his original commit message: ===== Testing that feeds specified with PACKAGE_FEED_URIS var are set correctly has two parts. First a build with this var set is required, and then smart update needs to be issued in the running taget. The previous is not a common selftest practice because this is a simple test, but requires building and running a specific image, which takes a lot of time. testimage is not a good fit either, since the images tested there do not have the PACKAGE_FEED_URIS var set. For this test, the runtime-test module is being used, which is a selftest module but runs a testimage command. The var and test environment were set in runtime-perf.py and the actual test is done in a new testcase added to meta-selftest layer. ===== [YOCTO #10872] (From OE-Core rev: 3a9e2fdef9316e24b52ce99ac355fc2b09786c72) Signed-off-by: Alexander Kanavin <alexander.kanavin@linux.intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* package.bbclass: Add SKIP_FILEDEPS to list of package specific variablesPeter Kjellerstedt2017-03-171-1/+1
| | | | | | | | | | | Changes to SKIP_FILEDEPS should change the sstate checksum. To make that happen, it needs to be listed in the list of package specific variables, therefore add it. (From OE-Core rev: 4d9fb8414300c0adc003f2d77041713a17b49bd4) Signed-off-by: Peter Kjellerstedt <peter.kjellerstedt@axis.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* runqemu: only boot ramfs when specifiedRobert Yang2017-03-171-1/+9
| | | | | | | | | | | | | | | | This can fix a problem: IMAGE_FSTYPES += "iso" $ bitbake core-image-minimal $ runqemu qemux86 It may boot core-image-minimal-initramfs rather than core-image-minimal, this is not what we want usually. This patch makes it avoid booting ramfs when there are other choices, or when it is specified, for example, "runqemu qemux86 ramfs" (From OE-Core rev: 614bde6774f4dfd414066bbaf75ed422943e37ab) Signed-off-by: Robert Yang <liezhi.yang@windriver.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* meta-yocto-bsp: bump to the latest linux stable kernel for the non-x86 BSPsKevin Hao2017-03-167-21/+33
| | | | | | | | | | Bump to the latest stable kernel for 4.1, 4.4, 4,9 and 4.10. Also set the default kernel to 4.10. (From meta-yocto rev: fbb8276e16976b5188efe5a9ee9bdda1ff44d931) Signed-off-by: Kevin Hao <kexin.hao@windriver.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* bitbake: tests/data: Add inactive remove override testRichard Purdie2017-03-161-0/+7
| | | | | | | | | | In 2bc4d35fb32defc59cd6ed1fc87e35924c201a5c we fixed cases where an inactive remove override was influecing the value of a variable. This adds a test case for this issue. (Bitbake rev: 1ff9b3c669fa187f152de7b8b57d14c2468d926c) Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* runqemu: add -h and --helpRobert Yang2017-03-161-2/+3
| | | | | | | | | | | | | | | | Fixed: $ runqemu -h runqemu - INFO - Assuming MACHINE = -h runqemu - INFO - Running MACHINE=-h bitbake -e... [snip] Exception: FSTYPE is NULL! [YOCTO #10941] (From OE-Core rev: 6b9dd7a589537b12da648be50298cf7d36461797) Signed-off-by: Robert Yang <liezhi.yang@windriver.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* runqemu: improve when no machine specifiedRobert Yang2017-03-161-0/+6
| | | | | | | | | | | | | | | | | Fixed: $ runqemu core-image-minimal [snip] Exception: FSTYPE is NULL! [snip] Get DEPLOY_DIR_IMAGE from "bitbake -e" to make it work. [YOCTO #10471] (From OE-Core rev: ca551b72a020782f164703765b97156000b908d2) Signed-off-by: Robert Yang <liezhi.yang@windriver.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* packagegroup-core-lsb: avoid rebuilding when changing layer configPaul Eggleton2017-03-161-0/+2
| | | | | | | | | | | | | | | It's regrettable that code in here is referring to BBFILE_COLLECTIONS, but it is, and the result is that this packagegroup will rebuild simply by adding or removing a layer which may be completely unrelated to whether you've got meta-qt4 or not. Add BBFILE_COLLECTIONS to vardepsexclude for the function to avoid this. (This was flagged up when testing the new yocto-compat-layer script - it understandably but undesirably reports it as a change caused by a layer). (From OE-Core rev: 10dc69467677a4ce2a26aa670bbb9c1d7d783a0e) Signed-off-by: Paul Eggleton <paul.eggleton@linux.intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* classes/base: reformat HOSTTOOLS errorPaul Eggleton2017-03-161-1/+1
| | | | | | | | | | Adjust the message slightly to make it clearer, in particular mentioning the HOSTTOOLS variable. (From OE-Core rev: e022b27d189c1dcc7b3baea2b99dba8d724e6e2b) Signed-off-by: Paul Eggleton <paul.eggleton@linux.intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* kexec-tools: Remove unused patchJussi Kukkonen2017-03-161-88/+0
| | | | | | | | | The patch was removed from SRC_URI as merged upstream in 587778e24c9. (From OE-Core rev: 818dced4e4409c112b35022b86b830b0c2a2a7da) Signed-off-by: Jussi Kukkonen <jussi.kukkonen@intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* gstreamer1.0-vaapi: Remove unused patchJussi Kukkonen2017-03-161-43/+0
| | | | | | | | | | | | This patch has seemingly never been applied in the recipe (even when it lived in meta-intel). I don't think we should have unused patches in the repo: If the patch is useful it could be reintroduced so that the binaries are packaged into a separate package. (From OE-Core rev: cd33ae2f21547354e1ef9776b2c4ebcea4eb7e99) Signed-off-by: Jussi Kukkonen <jussi.kukkonen@intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* gstreamer1.0-omx: Remove unused patchJussi Kukkonen2017-03-161-30/+0
| | | | | | | | | The patch was only used in the ancient and recently removed git recipe. (From OE-Core rev: 2d2d4c31d04f5f29250a307c1f3da739ab351ecd) Signed-off-by: Jussi Kukkonen <jussi.kukkonen@intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* opkg-utils: Remove unused patchesJussi Kukkonen2017-03-162-56/+0
| | | | | | | | | | | | | | | 0001-update-alternatives-warn-when-multiple-providers-hav.patch was removed from SRC_URI without mention in commit 60c9a9704. 001-Makefile-use-defined-bindir-and-mandir-as-installati.patch was removed from SRC_URI in d6b04e121. Current opkg does not need either patch. (From OE-Core rev: 789ec510495ca6eab379ec829e3013c977236966) Signed-off-by: Jussi Kukkonen <jussi.kukkonen@intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* gcc: Remove unused patchJussi Kukkonen2017-03-161-290/+0
| | | | | | | | | CVE-2016-4490 applied to gcc < 6.1.1, our version is 6.3 (From OE-Core rev: d8329861bf6f48f6e541a04062b8d1f373dfcd78) Signed-off-by: Jussi Kukkonen <jussi.kukkonen@intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* python-native: Remove unused patchJussi Kukkonen2017-03-161-27/+0
| | | | | | | | | | avoid_parallel_make_races_on_pgen.patch was removed from SRC_URI as handled in upstream in db9508891b6. (From OE-Core rev: 7e2a5a213535bfac14f0b2e3a3b7857b7fdcaffc) Signed-off-by: Jussi Kukkonen <jussi.kukkonen@intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* python: Remove unused patchesJussi Kukkonen2017-03-162-71/+0
| | | | | | | | | | CVE-2016-5636.patch and avoid_parallel_make_races_on_pgen.patch were removed from SRC_URI as handled upstream in adf4266524d0d. (From OE-Core rev: 53c0d1f18d4a11b0130e54466c91320acf4f5b18) Signed-off-by: Jussi Kukkonen <jussi.kukkonen@intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* python3: Remove unused patchesJussi Kukkonen2017-03-162-75/+0
| | | | | | | | | | CVE-2016-5636.patch and use_packed_importlib.patch were removed from SRC_URI as handled in upstream in b192bc02bbf91. (From OE-Core rev: 71c539483350a4b45fb5d397d29b6ebcfc863e2f) Signed-off-by: Jussi Kukkonen <jussi.kukkonen@intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* xf86-input-mouse: Remove unused patchJussi Kukkonen2017-03-161-21/+0
| | | | | | | | | The patch has not been used since the ancient git version was removed. (From OE-Core rev: 292f519dad5ed9e4389f2a3ad2307c168328a038) Signed-off-by: Jussi Kukkonen <jussi.kukkonen@intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* readline: Remove unused patchJussi Kukkonen2017-03-161-34/+0
| | | | | | | | | | config-dirent-symbols.patch was removed from SRC_URI as "already applied in upstream" in 983a4986947. (From OE-Core rev: 43e764a54458c9c6665bb7734b1fc7e7956bffdc) Signed-off-by: Jussi Kukkonen <jussi.kukkonen@intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* qemu: Remove uuid PACKAGECONFIGJussi Kukkonen2017-03-161-2/+1
| | | | | | | | | | --enable-uuid no longer exists: There's a uuid implementation in libqemuutil. (From OE-Core rev: 9da623d569ae552b1772a3b3a06df3cbf76cd573) Signed-off-by: Jussi Kukkonen <jussi.kukkonen@intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* bitbake.conf: Drop pip3 from HOSTTOOLS_NONFATALRichard Purdie2017-03-161-1/+1
| | | | | | | | | Now that pip3-native is used by build-appliance, we should no longer need this host tool. (From OE-Core rev: 096f943d4b7a7cf5d4c3d45f34be5ddcd2475790) Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* build-appliance-image: ensure pod2man present in BAJuro Bystricky2017-03-161-1/+1
| | | | | | | | | | | | | | | | | | "pod2man" went missing from BA, but it is required. This patch fixes the Toaster error: <...> ERROR: These tools appear to be unavailable in PATH, please install them in order to proceed: pod2man <...> [YOCTO#11144] (From OE-Core rev: 562c184d52db2182eafde3cf9866606145784deb) Signed-off-by: Juro Bystricky <juro.bystricky@intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* build-appliance-image: fix build errorsJuro Bystricky2017-03-161-0/+2
| | | | | | | | | | | | Remove any symlinks before creating new ones to avoid potential build errors such as: FileExistsError: [Errno 17] File exists: '../../usr/src/kernel' -> ... ' (From OE-Core rev: 376aa835dd70e646a00706272db6f5ac7f419ce7) Signed-off-by: Juro Bystricky <juro.bystricky@intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* build-appliance-image: use pip3-nativeJuro Bystricky2017-03-161-2/+4
| | | | | | | | | | | | | Do not rely on pip3 being installed on the host. Use pip3-native instead. [YOCTO#10909] [YOCTO#11022] (From OE-Core rev: 0c349f06b6b026e9bbd3e9a8188e3d8645fd00d9) Signed-off-by: Juro Bystricky <juro.bystricky@intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* python3-pip: support native buildsJuro Bystricky2017-03-161-0/+7
| | | | | | | | | | | | Add native pip3 support. [YOCTO#11049] [YOCTO#11022] (From OE-Core rev: cb2073658305b605cccc60439b62c1dc515d9a8d) Signed-off-by: Juro Bystricky <juro.bystricky@intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* runqemu: independent network and rootfs setupJuro Bystricky2017-03-161-0/+4
| | | | | | | | | | | | | Presently, runqemu sets up rootfs as part of network setup. In case there is no network desired we will end up without rootfs as well. This patch sets up network and rootfs independently. It is also possible to bypass setup of rootfs if QB_ROOTFS is set to "none". (From OE-Core rev: 006ab8c6bcfe9d065c215cab15289357cefc9259) Signed-off-by: Juro Bystricky <juro.bystricky@intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* yocto-compat-layer: improve error handling in signature creationPatrick Ohly2017-03-161-11/+9
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | When "bitbake -k -S none world" failed, the error printed by yocto-compat-layer.py contained the stack trace multiple times and did not contain the stderr output from bitbake, making the error hard to understand and debug: INFO: ====================================================================== INFO: ERROR: test_signatures (common.CommonCompatLayer) INFO: ---------------------------------------------------------------------- INFO: Traceback (most recent call last): File "/fast/work/poky/scripts/lib/compatlayer/__init__.py", line 144, in get_signatures stderr=subprocess.PIPE) File "/usr/lib/python3.4/subprocess.py", line 620, in check_output raise CalledProcessError(retcode, process.args, output=output) subprocess.CalledProcessError: Command 'bitbake -k -S none world' returned non-zero exit status 1 During handling of the above exception, another exception occurred: Traceback (most recent call last): File "/fast/work/poky/scripts/lib/compatlayer/cases/common.py", line 51, in test_signatures curr_sigs = get_signatures(self.td['builddir'], failsafe=True) File "/fast/work/poky/scripts/lib/compatlayer/__init__.py", line 149, in get_signatures raise RuntimeError(msg) RuntimeError: Traceback (most recent call last): File "/fast/work/poky/scripts/lib/compatlayer/__init__.py", line 144, in get_signatures stderr=subprocess.PIPE) File "/usr/lib/python3.4/subprocess.py", line 620, in check_output raise CalledProcessError(retcode, process.args, output=output) subprocess.CalledProcessError: Command 'bitbake -k -S none world' returned non-zero exit status 1 Loading cache...done. Loaded 1328 entries from dependency cache. NOTE: Resolving any missing task queue dependencies NOTE: Runtime target 'zlib-qat' is unbuildable, removing... Missing or unbuildable dependency chain was: ['zlib-qat'] ... Summary: There were 5 ERROR messages shown, returning a non-zero exit code. The yocto-compat-layer.log was incomplete, it only had the first part without the command output. stderr was missing due to stderr=subprocess.PIPE. Instead of the complicated try/except construct it's better to check the return code ourselves and raise just a single exception. The output (both on stderr and in the yocto-compat-layer.log) now is: INFO: ====================================================================== INFO: ERROR: test_signatures (common.CommonCompatLayer) INFO: ---------------------------------------------------------------------- INFO: Traceback (most recent call last): File "/fast/work/poky/scripts/lib/compatlayer/cases/common.py", line 51, in test_signatures curr_sigs = get_signatures(self.td['builddir'], failsafe=True) File "/fast/work/poky/scripts/lib/compatlayer/__init__.py", line 147, in get_signatures raise RuntimeError(msg) RuntimeError: Generating signatures failed. This might be due to some parse error and/or general layer incompatibilities. Command: bitbake -k -S none world Output: Loading cache...done. Loaded 1328 entries from dependency cache. NOTE: Resolving any missing task queue dependencies ERROR: Nothing PROVIDES 'qat16' (but /fast/work/meta-intel/common/recipes-extended/openssl-qat/openssl-qat_0.4.9-009.bb DEPENDS on or otherwise requires it) ERROR: qat16 was skipped: incompatible with machine qemux86 (not in COMPATIBLE_MACHINE) ... Missing or unbuildable dependency chain was: ['openssl-qat-dev'] ... Summary: There were 5 ERROR messages shown, returning a non-zero exit code. (From OE-Core rev: 5b9ac62ab535d2791b9713857e1016f49f53dd8d) Signed-off-by: Patrick Ohly <patrick.ohly@intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* sanity.bbclass: modify check for shellJuro Bystricky2017-03-161-1/+3
| | | | | | | | | | | | | | | | | Due to the recently implemented update-alternatives for bash binary, sanity checker may end up with a (false-positive) error such as: Error, /bin/sh links to /bin/bash.bash, must be dash or bash This patch modifies the test: presence of "/bash" or "/dash" in shell binary name results in pass. [YOCTO#11108] (From OE-Core rev: ef51746cdd12e6b08109e9bd90a0a465c3f9f93c) Signed-off-by: Juro Bystricky <juro.bystricky@intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* selftest: Disable SSTATE_MIRRORS for sstate signing testRichard Purdie2017-03-161-0/+2
| | | | | | | | | | | | | | | | | | | Building ed into an sstate mirror, then leaving it enabled for oe-selftest -r signing.Signing.test_signing_sstate_archive results in: NOTE: recipe ed-1.14.1-r0: task do_populate_lic_setscene: Started WARNING: ed-1.14.1-r0 do_populate_lic_setscene: Failed to fetch URL file://29/sstate:ed::1.14.1:r0::3:290bbc39f3b25cc27028dafce4b5aa48_populate_lic.tgz.sig;downloadfilename=29/sstate:ed::1.14.1:r0::3:290bbc39f3b25cc27028dafce4b5aa48_populate_lic.tgz.sig, attempting MIRRORS if available ERROR: ed-1.14.1-r0 do_populate_lic_setscene: Fetcher failure: Unable to find file file://29/sstate:ed::1.14.1:r0::3:290bbc39f3b25cc27028dafce4b5aa48_populate_lic.tgz.sig;downloadfilename=29/sstate:ed::1.14.1:r0::3:290bbc39f3b25cc27028dafce4b5aa48_populate_lic.tgz.sig anywhere. The paths that were searched were: /media/build1/poky/build/test-sstate /media/build1/poky/build/test-sstate WARNING: ed-1.14.1-r0 do_populate_lic_setscene: Cannot verify signature on sstate package /media/build1/poky/build/test-sstate/29/sstate:ed::1.14.1:r0::3:290bbc39f3b25cc27028dafce4b5aa48_populate_lic.tgz NOTE: recipe ed-1.14.1-r0: task do_populate_lic_setscene: Succeeded so we need to disable SSTATE_MIRRORS for this test. (From OE-Core rev: 2ce9962851fe58c099599679340fd87e90f426ec) Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* bitbake.conf: whitelist socat as non-fatal host toolMikko Ylinen2017-03-161-1/+1
| | | | | | | | | | | | | oe-git-proxy depends on socat host tool but it's not whitelisted and triggers a 'binary not in PATH' error. Whitelist socat but make it a HOSTTOOLS_NONFATAL since it's not a hard dependency. (From OE-Core rev: 97f979ee61a06349139ccc47feaf051bdbcf0e16) Signed-off-by: Mikko Ylinen <mikko.ylinen@linux.intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* bitbake: runqueue: minor typo fixAndre McCurdy2017-03-151-1/+1
| | | | | | | (Bitbake rev: f2c151cd345788a135452f63f622a2bc0b10c2d4) Signed-off-by: Andre McCurdy <armccurdy@gmail.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* wic: selftest: account for occasional newline in debugfs file namesMaciej Borzecki2017-03-141-4/+21
| | | | | | | | | | | | | | | | | | | | Debugfs output may contain a newline in file names in 'ls -p' output. Make sure that output is correctly split into lines by matching '/\n' and newlines are removed from file names. Fixes the following error appearing in AB tests: Traceback (most recent call last): File "/home/pokybuild/yocto-autobuilder/yocto-worker/nightly-oe-selftest/build/meta/lib/oeqa/selftest/wic.py", line 388, in test_exclude_path files = [line.split('/')[5] for line in res.output.split('\n')] File "/home/pokybuild/yocto-autobuilder/yocto-worker/nightly-oe-selftest/build/meta/lib/oeqa/selftest/wic.py", line 388, in <listcomp> files = [line.split('/')[5] for line in res.output.split('\n')] IndexError: list index out of range (From OE-Core rev: 477805b913a6c4b4b630e42f08cd9e59f1e4e254) Signed-off-by: Maciej Borzecki <maciej.borzecki@rndity.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* go: add native recipes for 1.8Khem Raj2017-03-144-9/+15
| | | | | | | (From OE-Core rev: 13a5c3dac4b5b0ccb4c5dfebf79b468acd8e1983) Signed-off-by: Khem Raj <raj.khem@gmail.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* go: Enable on muslKhem Raj2017-03-143-6/+0
| | | | | | | | | Working fine for musl targets now (From OE-Core rev: 1bab5be8133f62cdae251e66db6f472c3c37297c) Signed-off-by: Khem Raj <raj.khem@gmail.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* openssl: actually apply Use-SHA256-not-MD5-as-default-digest.patchRoss Burton2017-03-141-0/+1
| | | | | | | | | | | | | | | This patch was added to fix a CVE, but wasn't actually added to SRC_URI: CVE: CVE-2004-2761 The MD5 Message-Digest Algorithm is not collision resistant, which makes it easier for context-dependent attackers to conduct spoofing attacks, as demonstrated by attacks on the use of MD5 in the signature algorithm of an X.509 certificate. (From OE-Core rev: 8791800f84321b3f46772bc2d9e4f754e6213946) Signed-off-by: Ross Burton <ross.burton@intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
generated by cgit v1.2.3-54-g00ecf (git 2.39.0) at 2024-11-13 14:08:30 +0000