summaryrefslogtreecommitdiffstats
path: root/meta
Commit message (Collapse)AuthorAgeFilesLines
* valgrind: correct the comparison logic in vg_regtestMaxin B. John2017-03-271-2/+2
| | | | | | | | | | | | | | | do_diffs in the vg_regtest script compares the actual test output against the expected test output and returns 0 if it matches. Previous upgrade modified the return value of do_diffs() and that resulted in ptest failures. [YOCTO #8471] (From OE-Core rev: fa5f7b5090468da0ed1e30160e68362c97350c47) Signed-off-by: Maxin B. John <maxin.john@intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* valgrind: vg_regtest.in: fix perl scriptMaxin B. John2017-03-271-4/+29
| | | | | | | | | | | | @PERL@ in vg_regtest.in causes recipe specific sysroot based perl to be present in the vg_regtest script, making it unusable in the target. Use /usr/bin/perl instead of @PERL@ to fix it. (From OE-Core rev: 7a0caa23965185ac8268ae1da2f61fc7ca6de682) Signed-off-by: Maxin B. John <maxin.john@intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* boost: various cleanupsRoss Burton2017-03-271-6/+4
| | | | | | | | | | | | | Re-order some assignments to be logically arranged. Remove the set -ex statements as they serve no purpose. Pass --debug-configuration to see what configuration steps boost is taking. (From OE-Core rev: 2dc4796f02ecdc99ee3c51c668e8d9090e68a655) Signed-off-by: Ross Burton <ross.burton@intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* boost: port boost-python to Python 3Ross Burton2017-03-273-19/+287
| | | | | | | | | | | | | | | | | As Python 3 is the default Python version, change Boost to build against Python 3 instead of Python 2 if enabled. It's not simple to support both, so this means that support for building boost-python against Python 2 has been removed. This involves backporting a number of patches upstream to fix Python 3 support, and telling Boost precisely where to find the Python headers and libraries so that it doesn't try to invoke the host Python to determine these values. [ YOCTO #11104 ] (From OE-Core rev: 0f5418eb0ce12811b16d2e3c28c28140a509f685) Signed-off-by: Ross Burton <ross.burton@intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* tzdata: update to 2017bArmin Kuster2017-03-271-2/+2
| | | | | | | (From OE-Core rev: 07aee884efee75568b4a7b7d6bbfe3255ed65ef5) Signed-off-by: Armin Kuster <akuster@mvista.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* tzcode: update to 2017bArmin Kuster2017-03-271-4/+4
| | | | | | | | | | | | | | | | | | | | Briefly: Haiti has resumed DST. Changes to past and future time stamps Haiti resumed observance of DST in 2017. (Thanks to Steffen Thorsen.) Changes to past time stamps Liberia changed from -004430 to +00 on 1972-01-07, not 1972-05-01. Use "MMT" to abbreviate Liberia's time zone before 1972, as "-004430" is one byte over the POSIX limit. (Problem reported by Derick Rethans.) (From OE-Core rev: 70ff7cfa8a7ffb537da19aeca026032bab55a00d) Signed-off-by: Armin Kuster <akuster@mvista.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* targetcontrol.py: use logger.info to replace of bb.noteRobert Yang2017-03-272-6/+11
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | The bb.note prints multiple same lines when invoke this class again, but if we set mainlogger.propagate = False, nothing would be printed, according to logging's document: https://docs.python.org/3/library/logging.html Note If you attach a handler to a logger and one or more of its ancestors, it may emit the same record multiple times. In general, you should not need to attach a handler to more than one logger - if you just attach it to the appropriate logger which is highest in the logger hierarchy, then it will see all events logged by all descendant loggers, provided that their propagate setting is left set to True. A common scenario is to attach handlers only to the root logger, and to let propagation take care of the rest. We may need avoid using bb.note or bb.warn in oeqa since it attaches multiple log handlers which may cause confusions This patch only sets "mainlogger.propagate = False" in selftest/runqemu.py and use logger.info to replace bb.note in targetcontrol.py to minimize the impact. [YOCTO #10249] (From OE-Core rev: b139790422bc8e0d80bad063bb78bc1632731bc1) Signed-off-by: Robert Yang <liezhi.yang@windriver.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* selftest/runqemu.py: add it to test runqemuRobert Yang2017-03-271-0/+136
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | Usage: $ oe-selftest -r runqemu Current test cases: $ runqemu nographic qemux86-64 $ runqemu nographic qemux86-64 ext4 $ runqemu nographic qemux86-64 iso $ runqemu nographic core-image-minimal $ runqemu nographic core-image-minimal vmdk $ runqemu nographic core-image-minimal vdi $ runqemu nographic tmp/deploy/images/qemux86-64 $ runqemu nographic tmp/deploy/images/qemux86-64 hddimg $ runqemu nographic qemux86-64 slirp $ runqemu nographic qemux86-64 slirp qcow2 $ runqemu nographic tmp/deploy/images/qemux86-64/core-image-minimal-qemux86-64.qemuboot.conf $ runqemu nographic tmp/deploy/images/qemux86-64/core-image-minimal-qemux86-64.ext4 Need more later: - Test initramfs - Test nfs - Test when set DEPLOY_DIR_IMAGE and OECORE_NATIVE_SYSROOT - And others which similate runqemu runs on SDK and eSDK. [YOCTO #10249] (From OE-Core rev: e7073cb4786411bb71645e7d7cbc1c510910c4cc) Signed-off-by: Robert Yang <liezhi.yang@windriver.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* qemurunner.py: fix handling of runqemuparamsChen Qi2017-03-271-3/+3
| | | | | | | | | | The launch() doesn't need runqemuparams, we need handle it in start(). (From OE-Core rev: 16400f2b8bffc4cae0263bb597522071299b46ca) Signed-off-by: Chen Qi <Qi.Chen@windriver.com> Signed-off-by: Robert Yang <liezhi.yang@windriver.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* oeqa/targetcontrol.py: modify it to test runqemuRobert Yang2017-03-273-18/+43
| | | | | | | | | | | | | | | | | | Modify the following files to test runqemu: targetcontrol.py utils/commands.py utils/qemurunner.py We need simulate how "runqemu" works in command line, so when test "runqemu", the targetcontrol.py, utils/commands.py and utils/qemurunner.py don't have to find the rootfs or set env vars. [YOCTO #10249] (From OE-Core rev: 9305d816bdf8837ea3a407091cb7f24a9a3ae8dc) Signed-off-by: Robert Yang <liezhi.yang@windriver.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* qemurunner: configurable timeout for run_serial()Patrick Ohly2017-03-273-12/+17
| | | | | | | | | | | | | | | | | | | Some commands might need to run longer than the default timeout of five seconds. If that occurred, run_serial() returned with a status code of zero (sic!) and no other indication of what went wrong. Now the timeout is configurable (with five still the default) and an explicit warning ("<<< run_serial(): command timed out after 5 seconds without output >>>") gets appended at the end of the data returned to the caller. While at it, the logic for checking for the timeout was updated a bit because both implementations could overshoot the timeout when entering select() right before the final deadline. (From OE-Core rev: accf0362f964cc9d6330b6e52e83d748d890521f) Signed-off-by: Patrick Ohly <patrick.ohly@intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* xserver-nodm-init: option to remove cursorTrevor Woerner2017-03-272-1/+4
| | | | | | | | | | | Add a PACKAGECONFIG option to allow the user to disable the mouse cursor/pointer in the X server. This might be useful where a touchscreen is used. (From OE-Core rev: 680940250c9a1c7b43229c5e4f4fed5cc3e31033) Signed-off-by: Trevor Woerner <twoerner@gmail.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* staging: Remove uninstalled dependencies from sysrootsRichard Purdie2017-03-241-0/+28
| | | | | | | | | | | | | | | | | Currently, if something is added to a sysroot, its hash remains unchanged, and it continues to be buildable, it doesn't get removed from the sysroot. This patch handles the case where something is removed from DEPENDS or [depends]. It does introduce its own issue where something could get removed even though some other task in parallel may have the same requirement. This case should be extrememly rare and fixing the more common DEPENDS removal is likely the bigger win though. (From OE-Core rev: 06227bc5e533841ab12cde84a6ed6f8b8ddeb5cb) Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* staging: Update extend_recipe_sysroot vardepsexclude after code changesRichard Purdie2017-03-241-1/+1
| | | | | | | | Changed were made to the code but not reflected in vardepsexclude, fix this. (From OE-Core rev: e59dc6985e22e7ac30b6afa81d448fbc372f5dab) Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* staging: Drop BB_SETSCENE_VERIFY_FUNCTION2Richard Purdie2017-03-241-13/+0
| | | | | | | | | | | | | | | | | The original description for this was: """ Since we clean out do_populate_sysroot if do_configure runs, don't allow do_populate_sysroot_setscene functions if we're going to run do_configure. """ With RSS, we don't need to clean do_populate_sysroot any more. Since we no longer do that, this function also has no purpose any longer and can also be removed. (From OE-Core rev: 637c6d17b4a812379cbab64d340660092e046965) Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* staging: Drop do_configure clean prefuncRichard Purdie2017-03-241-8/+0
| | | | | | | | | With recipe specific sysroots its now pointless to do this, may as well save the cpu cycles. (From OE-Core rev: b70c8e91e6c4240e95e8b22bcc36525a5a0703f9) Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* staging: Drop BB_SETSCENE_VERIFY_FUNCTION since it was replacedRichard Purdie2017-03-241-15/+0
| | | | | | | | | | BB_SETSCENE_VERIFY_FUNCTION2 replaced BB_SETSCENE_VERIFY_FUNCTION and due to our minimum bitbake requirements there is no point in retaining the older version any more. (From OE-Core rev: f08d6ccda5db9fdc81d53370aea1f599718897da) Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* musl: Fix issues in relative symlink creationAmarnath Valluri2017-03-242-11/+53
| | | | | | | | | | | Make use of lnr/ln -r while creating relative symlinks than guessing the relalive path. (From OE-Core rev: 8205b92631bc1dcb3419c709ef5a98b2b3cd9d70) Signed-off-by: Amarnath Valluri <amarnath.valluri@intel.com> Signed-off-by: Ross Burton <ross.burton@intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* base-files: Replace hardcoded root paths with appropriate bitbake variablesAmarnath Valluri2017-03-241-2/+3
| | | | | | | | | | | /bin, /sbin, /lib are replaced with ${base_bindir}, ${base_sbindir} and ${base_libdir}. (From OE-Core rev: 9b490e61938e06fda881b2213565c4de1f740f98) Signed-off-by: Amarnath Valluri <amarnath.valluri@intel.com> Signed-off-by: Ross Burton <ross.burton@intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* libvorbis: Contain gcc specific compiler flags using configure optionKhem Raj2017-03-242-1/+59
| | | | | | | | (From OE-Core rev: b6cdbf50e5c26c406e4ddecd66202ff7324f5468) Signed-off-by: Khem Raj <raj.khem@gmail.com> Signed-off-by: Ross Burton <ross.burton@intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* db: Fix atomic function namespace clash with clang builtinsKhem Raj2017-03-242-0/+46
| | | | | | | | | | Rename local function to avoid conflicts with compiler intrinsics (From OE-Core rev: fcfbbae9fdda539665a1e8bfe292f917bd5a1927) Signed-off-by: Khem Raj <raj.khem@gmail.com> Signed-off-by: Ross Burton <ross.burton@intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* native.bbclass: clear MACHINE_FEATURESAndre McCurdy2017-03-241-0/+1
| | | | | | | | | | | | | Try to avoid native recipes accidentally being dependent on MACHINE_FEATURES. This simple change doesn't prevent MACHINE_FEATURES set via MACHINE_FEATURES_BACKFILL sneaking through, but it's better than nothing. (From OE-Core rev: 96c20c9df714cdf3f0e9461ec566c4f5d3bdb5f1) Signed-off-by: Andre McCurdy <armccurdy@gmail.com> Signed-off-by: Ross Burton <ross.burton@intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* core-image.bbclass: update available IMAGE_FEATURESTrevor Woerner2017-03-241-0/+4
| | | | | | | | | | Update the list of available IMAGE_FEATURES with the sub-features of 'debug-tweaks' and add 'splash'. (From OE-Core rev: 1e46220bb3901476266846447ff40533c9bffa1d) Signed-off-by: Trevor Woerner <twoerner@gmail.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* firmware: use ${nonarch_base_libdir} for firmware installation.Amarnath Valluri2017-03-241-3/+3
| | | | | | | | | | Replace hardcoded '/lib' in kernel firmware installation path with ${nonarch_base_libdir}. (From OE-Core rev: 616c9ae8e73c9b69c8ff23c64ac4c2ace1a45af0) Signed-off-by: Amarnath Valluri <amarnath.valluri@intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* expect: resolve string formatting issuesAlexander Kanavin2017-03-243-1/+30
| | | | | | | | | [YOCTO #9542] (From OE-Core rev: b5fd2874cfe199703e7a5d12fa708e12ff0a2ad1) Signed-off-by: Alexander Kanavin <alexander.kanavin@linux.intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* package_manager.py: respect OPKGLIBDIRMartin Jansa2017-03-241-7/+14
| | | | | | | | | | | | | | | | | | | * respect it for incremental rootfs generation * add lists_dir option to opkg.conf * also fix setting info_dir and status_file when they use default value, the problem is that self.opkg_dir is already prefixed with rootfs directory, comparing it with /var/lib/opkg always returned false and the options were appended to config file unnecessary * with opkg 0.3.4 we can use VARDIR prefix added in: commit d2a8e23dc669adc398f4bb8bcfcabfcf925708f7 Author: Florin Gherendi <floring2502@gmail.com> Date: Mon Dec 19 12:25:38 2016 +0200 libopkg: make the /var and /etc directories configurable at compile time. (From OE-Core rev: b14c11d062872c3dcf95e03b61017005dea5b754) Signed-off-by: Martin Jansa <Martin.Jansa@gmail.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* rootfs.py: Respect OPKGLIBDIR variableMartin Jansa2017-03-241-1/+3
| | | | | | | | | | | | | * when OPKGLIBDIR doesn't have the default /var/lib value it will silently fail to copy package database from normal rootfs to debugfs rootfs and then when trying to install *-dbg complimentary packages it won't install anything, because installed_pkgs.txt file generated from debugfs is empty (From OE-Core rev: bebdb056c8bd0efc056f07b275a154e5d5a3aa2b) Signed-off-by: Martin Jansa <Martin.Jansa@gmail.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* uninative-tarball: glibc-gconv-{utf-16, cp1252} for binutils windresNathan Rossi2017-03-241-0/+3
| | | | | | | | | | | | | | The windres binutils binary which is used for Windows resource files requires utf-16 and cp1252 encoding support in order to correctly generate resource files with strings. As such when using uninative to build mingw resources for a nativesdk target the windres binary is executed on the native host, thus using the uninative libc and gconv modules. (From OE-Core rev: 778fb2342da55e202cfb7af04bbf120c1b68620a) Signed-off-by: Nathan Rossi <nathan@nathanrossi.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* rpm: add a "rpm-build" PROVIDESAlexander Kanavin2017-03-231-0/+2
| | | | | | | | | | | | rpm 5.x was packaging build tools separately, so we need to unbreak things that relied on that. [YOCTO #11167] (From OE-Core rev: 3b5ac72bdf76ac8ff98dc3c882a4edc77c6e2c33) Signed-off-by: Alexander Kanavin <alexander.kanavin@linux.intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* sign_rpm.bbclass: do not set/use RPM_GPG_PUBKEYAlexander Kanavin2017-03-233-9/+3
| | | | | | | | | | | | | This is entirely unnecessary (we can ask the signer backend to export the key to a file when needed), and was causing confusing selftest failures due to the variable being set from two different places. [YOCTO #11191] (From OE-Core rev: 74ea979044368dc28c24325e7e77471b70aa8fe8) Signed-off-by: Alexander Kanavin <alexander.kanavin@linux.intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* oeqa: use WORKDIR/oe-testimage-repo to look for RPM packagesAlexander Kanavin2017-03-231-1/+1
| | | | | | | | | | | | | Using RPM deploy dir was causing errors when pre-built images were used with these steps: https://wiki.yoctoproject.org/wiki/Quality_Assurance_yocto_project [YOCTO #11173] (From OE-Core rev: f633abed51ed19522340b1d923ffc12ed7e291d6) Signed-off-by: Alexander Kanavin <alexander.kanavin@linux.intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* oe-selftest: add test_rawcopy_plugin test caseEd Bartosh2017-03-231-0/+16
| | | | | | | | | | | | This test case builds wic image using rawcopy plugin running wic directly. [YOCTO #10618] (From OE-Core rev: acbeaa37554f3546b036ff8ef9aebfe00f2537c6) Signed-off-by: Ed Bartosh <ed.bartosh@linux.intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* selftest: pylinted wic test suite.Ed Bartosh2017-03-231-24/+28
| | | | | | | | | Fixed long lines, indentation and one unused variable. (From OE-Core rev: a6dbe6e1630067164881c8d7efb44cb650cd043c) Signed-off-by: Ed Bartosh <ed.bartosh@linux.intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* oe-selftest: test wic rawcopy pluginEd Bartosh2017-03-231-0/+16
| | | | | | | | | | | | | | | Added test_rawcopy_plugin_qemu test case and wks template. This test builds ext4 rootfs image, copies it to the root partition of the wic image using rawcopy plugin and boots wic image in qemu. [YOCTO #10618] (From OE-Core rev: db1f511228e26aaeeff452427637942747bbf42b) Signed-off-by: Ed Bartosh <ed.bartosh@linux.intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* sstate: Ensure installation directory is empty before executionRichard Purdie2017-03-221-0/+5
| | | | | | | | | | | | | | | | | | When you enable the systemd DISTRO_FEATURE, opkg-native contains systemd units which have a relocation fixme list. When systemd isn't in DISTRO_FEATURES, there are no fixmes required. Unfortunately as sstate isn't cleaning up its installation directory before use, if you install the systemd version, then install the non-systemd version from sstate, it would leave behind the fixme file from the systemd version and breakage results as it would try and fixup files which don't exist. The solution is to ensure the unpack/install directory is clean before use. It does raise other questions about opkg-native, systemd and DISTRO_FEATURES but there is an underlying sstate issue here too which would cause missing file failures. (From OE-Core rev: d1d55041e38b12d40f896834b56475ea19a6047f) Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* oeqa/selftest/devtool: Enable missing cleanupRichard Purdie2017-03-221-1/+1
| | | | | | | | | Not sure why this cleanup is disabled but it clearly should be running so enable it. (From OE-Core rev: 83867079182d8b9e981935da2b254947a89097bb) Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* externalsrc: Use git add -A for compatibility with all git versionsRichard Purdie2017-03-221-1/+1
| | | | | | | | | | | | | | | | | | | | | | | | | I've been debugging a selftest failure on Centos7. The problem turns out to be the elderly git version (1.8.3.1) on those systems. It means that the system doesn't correctly checksum changed files in the source tree, which in turn means do_compile fails to run and this leads to the following selftest failure: ====================================================================== FAIL [141.373s]: test_devtool_buildclean (oeqa.selftest.devtool.DevtoolTests) ---------------------------------------------------------------------- Traceback (most recent call last): File "/home/pokybuild/yocto-autobuilder/yocto-worker/nightly-oe-selftest/build/meta/lib/oeqa/selftest/devtool.py", line 530, in test_devtool_buildclean assertFile(tempdir_mdadm, 'mdadm') File "/home/pokybuild/yocto-autobuilder/yocto-worker/nightly-oe-selftest/build/meta/lib/oeqa/selftest/devtool.py", line 497, in assertFile self.assertTrue(os.path.exists(f), "%r does not exist" % f) AssertionError: False is not true : '/tmp/devtoolqag88s39z8/mdadm' does not exist The solution is to use -A on the git add commandline which matches the behaviour in git 2.0+ versions and resolves the problem. (From OE-Core rev: 964e8b8cae4b28e21ade12b5effb494e459b1f0f) Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* wic: selftest: add tests for --fixed-size partition flagsMaciej Borzecki2017-03-221-0/+63
| | | | | | | | | | | | wic has a new flag for setting a fixed parition size --fixed-size. Add tests that verify if partition is indeed sized properly and that errors are signaled when there is not enough space to fit partition data. (From OE-Core rev: 84c2184546779ece3eb23c5628e4c9d177568043) Signed-off-by: Maciej Borzecki <maciej.borzecki@rndity.com> Signed-off-by: Ross Burton <ross.burton@intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* wic: selftest: do not assume bzImage kernel imageMaciej Borzecki2017-03-221-1/+2
| | | | | | | | | | | Instead of assuming that bzImage is available, query bitbake enviroment for KERNEL_IMAGETYPE. (From OE-Core rev: d3e1d25a06dd4cb3ec80ea63352de24e50552481) Signed-off-by: Maciej Borzecki <maciej.borzecki@rndity.com> Signed-off-by: Ross Burton <ross.burton@intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* wic: selftest: avoid COMPATIBLE_HOST issuesMaciej Borzecki2017-03-221-1/+40
| | | | | | | | | | | | | | | | | Wic tests will unconditionally attempt to build images that may require dependencies that are incompatible with current target. Resolve this by consulting HOST_ARCH first (which defaults to TARGET_ARCH) before proceeding to build images that may be incompatible. A convenience decorator only_for_arch() can be used to skip test cases for specific architectures. (From OE-Core rev: ff46125082f08eb93cc549bbe1d79c3b8f9cba64) Signed-off-by: Maciej Borzecki <maciej.borzecki@rndity.com> Signed-off-by: Ross Burton <ross.burton@intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* selftest: wic: replace directdisk with wictestdisk where possibleMaciej Borzecki2017-03-221-32/+32
| | | | | | | | | | | Use wictestdisk instead of directdisk thus allowing more tests to be run on non-x86 compatible machines. (From OE-Core rev: 071785b01cdaa0d35808fa0b7308162cfebf54f1) Signed-off-by: Maciej Borzecki <maciej.borzecki@rndity.com> Signed-off-by: Ross Burton <ross.burton@intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* buildhistory.bbclass: add layer name to source recipe dataMikko Rapeli2017-03-221-0/+4
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | It is useful to know which layer provided a given recipe and its binary packages. Many projects combine a number of layers and some of them also provide same recipe names in which case bitbake can prioritize between them. buildhistory can record the decision by saving the layer from where the recipe was taken from. Also, if a project is split to sub projects which maintain recipes in different meta layers, then meta layer specific summaries of e.g. disk usage can be calculated if source recipes meta layer name is recorded for example in buildhistory. If source layer is not in build history, then layer providing the recipe can be exported from build environment using 'bitbake-layers show-recipes', but it takes a long time to execute since all recipes are parsed again and requires full source tree with correct build configuration. This patch exports the name of layer as configured in BBFILE_COLLECTIONS append of its layer.conf. 'bitbake-layers show-recipes' exports the meta layers directory path name. For several open source layers these are different, e.g. meta-openembedded/meta-perl/conf/layer.conf is perl-layer, poky/meta/conf/layer.conf is core, poky/meta-skeleton/conf/layer.conf is skeleton etc. (From OE-Core rev: d8e59d1f840e4282859ad14397d1c06516b8eb11) Signed-off-by: Mikko Rapeli <mikko.rapeli@bmw.de> Signed-off-by: Ross Burton <ross.burton@intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* ovmf: fix toolchain selectionPatrick Ohly2017-03-222-66/+50
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | For the native tools, a static patch inserted gcc/g++/ld/ar while later adding BUILD_LDFLAGS and BUILD_CFLAGS with sed. Now it's all done with sed, which has the advantage that it uses the actual compile variables. However, in practice those are the same. More importantly, picking the build tools for the target was broken. ovmf-native tried to insert TARGET_PREFIX into the tools definition file, but that variable is empty in a native recipe. As a result, "gcc" was used instead of "${HOST_PREFIX}gcc", leading to an undesirable dependency on the host compiler and potentially (probably?!) causing some of the build issues that were seen for ovmf. The new approach is to override the tool selection in ovmf-native so that the HOST_PREFIX env variable is used, which then gets exported during do_compile for the target. While at it, Python code that gets appened to do_patch only to call shell functions gets replaced with the do_patch[postfuncs] mechanism. Incremental builds now always use the tools definition from the current ovmf-native; previously, only the initial build copied the template file. Probably the entire split into ovmf-native and ovmf could be removed. This merely hasn't been attempted yet. (From OE-Core rev: 23a12d87a6e82f80f4ccc1a01c707faa89ff7abd) Signed-off-by: Patrick Ohly <patrick.ohly@intel.com> Signed-off-by: Ross Burton <ross.burton@intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* libcomps: Fix/optimize building with clangKhem Raj2017-03-222-0/+36
| | | | | | | | (From OE-Core rev: aa30853693a8b6092e1ea9785d64267858454d17) Signed-off-by: Khem Raj <raj.khem@gmail.com> Signed-off-by: Ross Burton <ross.burton@intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* go-native: Install bootstrap binaries with 1.4 suffixKhem Raj2017-03-221-6/+6
| | | | | | | | | | | | | | Currently, bin/go and bin/gofmt collide between go-native and go-bootstrap-native packages, these are scripts anyway which call the go compiler proper from right install, in this case create go1.4 and gofmt1.4 names for these scripts to avoid namespace collision (From OE-Core rev: c46faa132d39d3dc235a019d9abf6e46f74e3bae) Signed-off-by: Khem Raj <raj.khem@gmail.com> Signed-off-by: Ross Burton <ross.burton@intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* acpitests: Point Makefile CC to use OE synthesized CCKhem Raj2017-03-221-1/+1
| | | | | | | | | | | | Default CC is same as used here, there is no need to duplicate it, as a plus it helps in compiling acpitests with non-gcc cross compilers (From OE-Core rev: e23601390833fe93d58ca61a7158458dfdbd6fac) Signed-off-by: Khem Raj <raj.khem@gmail.com> Signed-off-by: Ross Burton <ross.burton@intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* openssl: Fix build with clangKhem Raj2017-03-222-2/+52
| | | | | | | | (From OE-Core rev: c8da8cec9007f77396f873f1cd56fc78bf83b19a) Signed-off-by: Khem Raj <raj.khem@gmail.com> Signed-off-by: Ross Burton <ross.burton@intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* oeqa/selftest: remove test_sanity_unsafe_binary_referencesRoss Burton2017-03-221-19/+0
| | | | | | | | | | | This test was attempting to exercise a broken test, for some reason this broke with patches under review but investigation revealed that the test itself is broken. The test has been removed, so there's no need to test it. (From OE-Core rev: 4f5f552cd6601ba244ef4efc782616bc477e1340) Signed-off-by: Ross Burton <ross.burton@intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* insane: remove broken unsafe-references-in-binaries testRoss Burton2017-03-221-42/+0
| | | | | | | | | | | | | | | | | | | This test aims to detect binaries in /bin which link to libraries in /usr/lib, for the case where the user has /usr on a separate filesystem to /. However it doesn't scan both image/ and the sysroot, so if a binary in /bin links to a library in /usr/lib that was built by the same recipe then it will error out. This test isn't enabled by default, and because of this serious bug I suspect nobody else is enabling it either. As /usr being on a separate partition to / is a very rare configuration these days I think we should delete the test: if someone cares sufficiently they should write a test that actually works. (From OE-Core rev: a6af5bbf3dad6f0951c67a0aae13ef86a8906893) Signed-off-by: Ross Burton <ross.burton@intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* package.bbclass: Add PRIVATE_LIBS to list of package specific variablesPeter Kjellerstedt2017-03-221-1/+1
| | | | | | | | | | | | Changes to PRIVATE_LIBS 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: 1a6555dfd17e180b81dec407095787d8a72a9edd) Signed-off-by: Peter Kjellerstedt <peter.kjellerstedt@axis.com> 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-19 02:31:49 +0000