summaryrefslogtreecommitdiffstats
Commit message (Collapse)AuthorAgeFilesLines
* libinput: Upgrade 1.6.0 -> 1.6.1Jussi Kukkonen2017-02-231-2/+2
| | | | | | | | | | | | Small release with mostly bug fixes. (From OE-Core rev: 87e7cb3cd28fb0ebae57620a12c653e6c4e650bb) (From OE-Core rev: dc77835daf26b94ce6d84888e83e1348d31a6a5c) Signed-off-by: Jussi Kukkonen <jussi.kukkonen@intel.com> Signed-off-by: Ross Burton <ross.burton@intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* xkeyboard-config: Upgrade 2.19 -> 2.20Jussi Kukkonen2017-02-231-2/+2
| | | | | | | | | | | | Layout updates from the last 16 months. (From OE-Core rev: 22ae7375bb03531349060f11a4f2bfc99d851e52) (From OE-Core rev: 452160980af60807c8ed51eabd291b4bf3ce8348) Signed-off-by: Jussi Kukkonen <jussi.kukkonen@intel.com> Signed-off-by: Ross Burton <ross.burton@intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* xf86-input-libinput: Upgrade 0.23.0 -> 0.24.0Jussi Kukkonen2017-02-231-2/+2
| | | | | | | | | | | | Small release with mostly tablet improvements. (From OE-Core rev: 15b0f0421b9f0b23ccbcdd18428eff100c622b91) (From OE-Core rev: ac4cd6757479f6f92a7ada96f275d71e924c4d92) Signed-off-by: Jussi Kukkonen <jussi.kukkonen@intel.com> Signed-off-by: Ross Burton <ross.burton@intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* xauth: Upgrade 1.0.9 -> 1.0.10Jussi Kukkonen2017-02-231-2/+2
| | | | | | | | | | | | Small bug fix release. (From OE-Core rev: 62ffef15d288f566e6bd93b1af4bd5ab6c6ea8b1) (From OE-Core rev: 0d8980e3ea4e61145875b08d7d2acba3df0816ba) Signed-off-by: Jussi Kukkonen <jussi.kukkonen@intel.com> Signed-off-by: Ross Burton <ross.burton@intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* presentproto: Upgrade 1.0 -> 1.1Jussi Kukkonen2017-02-231-4/+2
| | | | | | | | | | | | Small release with mostly build system fixes. (From OE-Core rev: 638af9cff97cf3ead79226b616e29f9135cbf53d) (From OE-Core rev: 549669a7bace51fd9e44b4629cb4ce7c65e98ffe) Signed-off-by: Jussi Kukkonen <jussi.kukkonen@intel.com> Signed-off-by: Ross Burton <ross.burton@intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* util-macros: Upgrade 1.19.0 -> 1.19.1Jussi Kukkonen2017-02-231-2/+2
| | | | | | | | | | | | Tiny release to fix build with new xmlto. (From OE-Core rev: ef523527b68eef0ce1fdacac87b4eee27677589b) (From OE-Core rev: 8a52a4a64727f573fa11951ee0d387cc977a8b25) Signed-off-by: Jussi Kukkonen <jussi.kukkonen@intel.com> Signed-off-by: Ross Burton <ross.burton@intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* vte: Upgrade 0.44.2 -> 0.46.1Jussi Kukkonen2017-02-231-4/+4
| | | | | | | | | | | | | | | | New release requires libpcre 2. Enable gnutls by default to remove an annoying warning on every vte widget. core-image-sato already has gnutls so this shouldn't be a big deal. (From OE-Core rev: c9b65168a6e5ca329c013d5932567eb6cca770f3) (From OE-Core rev: 03f707ba1134b9706aed85665dc5f61aebbd5fb7) Signed-off-by: Jussi Kukkonen <jussi.kukkonen@intel.com> Signed-off-by: Ross Burton <ross.burton@intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* gmp: Update to 6.1.2Khem Raj2017-02-235-3/+2
| | | | | | | | | | (From OE-Core rev: a341bc666c6d25741bbe879ccf0ade8da6ba4373) (From OE-Core rev: ba962c8cd4f39f72028662db4cb8505befe64206) 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>
* gdb: Upgrade to 7.12.1Khem Raj2017-02-235-46/+2
| | | | | | | | | | | | Drop already applied patches (From OE-Core rev: 233641857bdc4071e5cb9a25206def880eb2754d) (From OE-Core rev: 3393364d1b365226d15042f20f0e6c56a439225b) 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>
* musl: Update to latestKhem Raj2017-02-231-1/+1
| | | | | | | | | | | | | | | | | | | | | | here is shortlog * d6601f0a avoid unbounded strlen in gettext functions * dbbb3734 fix use of uninitialized pointer in gettext core * 01e6bbec fix bindtextdomain logic error deactivating other domains * 6894f847 fix spurious EINTR errors from multithreaded set*id, etc. * 1f53e7d0 fix crashes in x32 __tls_get_addr * 27b3fd68 fix crash from corrupted tls module list after failed dlopen * 809ff8cf treat base 1 as an error in strtol-family functions * 786fda87 fix getopt[_long] clobbering of optopt on success * 150747b4 reduce impact of REG_* namespace pollution in x86[_64] signal.h (From OE-Core rev: 6f42e7be18e0896aac357ce2aedaa3b32b2ad98e) (From OE-Core rev: 72146e579e2df3b1132776a81b47e842dc262229) 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>
* libpcre2: add it for newer vteRobert Yang2017-02-232-0/+121
| | | | | | | | | | | | | | | | | | | | There are two major versions of the PCRE library. The newest version, PCRE2, was released in 2015 and is at version 10.22. The original, very widely deployed PCRE library, originally released in 1997, is at version 8.40, and the API and feature set are stable, future releases will be for bugfixes only. All new future features will be to PCRE2, not the original PCRE 8.x series. The newer vte depends on libpcre2, so add it. (From OE-Core rev: f7165d379cb67c4d4918a8a3e9509d3d823d61da) (From OE-Core rev: 69c4d94dd6b825c710c6e76fe77e5255ddd1183d) Signed-off-by: Robert Yang <liezhi.yang@windriver.com> Signed-off-by: Ross Burton <ross.burton@intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* tremor: removeRoss Burton2017-02-233-151/+0
| | | | | | | | | | | | Now that Tremor isn't enabled by default in oe-core's GStreamer plugins and has been added to meta-multimedia, it can be removed from oe-core. (From OE-Core rev: 30f5c80943f69884b3d7323b540c8bb0f1efd8fd) (From OE-Core rev: a8b476e7d6a5bf43cceb8c7b2610c9b66fe2f33e) Signed-off-by: Ross Burton <ross.burton@intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* slang: rewrite recipe to run autoconfRoss Burton2017-02-236-335/+31
| | | | | | | | | | | | | | | | | | | | | | | | | | | | I discovered that we were not running autoreconf (and cannot due to the unconvential file structure upstream), so manually run autoconf and move the generated configure to the right place as we do already for gnu-configize. Update no-x.patch (now that it is actually being used) so that it doesn't break the build. Patch out the use of INST_LIB_DIR in slsh/Makefile.in as this is the *target* path, so is inappropriate to link to. This means we can remove the custom do_install() which was working around the problem. Remove all rpath patches (now overwritten by autoconf) and replace with just passing RPATH='' via oe_runmake. Remove the library search path patches (now overwritten by autoconf) and replace with passing explicit pointers to the sysroot in the options. [ YOCTO #10969 ] (From OE-Core rev: 48fe39b09fbac973ba188938ab2a080f71ee8d68) (From OE-Core rev: 3506898dbd62bb028349b83e1538a7ea665c3d1c) Signed-off-by: Ross Burton <ross.burton@intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* depmodwrapper-cross/qemuwrapper-cross: Drop unneeded binutils dependencyRichard Purdie2017-02-232-0/+4
| | | | | | | | | | | | | | By default these pull in binutils-cross since they're a cross tool and pull in any native tool requirements. In reality they don't need such tools at build time or runtime since they're scripts. Therefore clear the dependency and save on some processing time. (From OE-Core rev: 63796765122e2eee2b78930797d571acb5c244d1) (From OE-Core rev: 50feffd0917b0ab408b34ded9c2f741a9c4e5b74) Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* gcc-cross: Avoid races with gcc_stash_builddirRichard Purdie2017-02-231-1/+1
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | Its sad we need to do this but do_install and do_populate_sysroot appear to change the files in ${B} and this breaks if something works in parallel like gcc_stash_builddir. We've seen a few too many race errors on the autobuilder which appear to be from this so make things run in sequence deterministically for now. An example failure was this from do_populate_sysroot whilst stash_builddir was running in parallel: ERROR: gcc-cross-initial-arm-6.3.0-r0 do_populate_sysroot: split_and_strip_files: 'file /home/pokybuild/yocto-autobuilder/yocto-worker/nightly-arm-lsb/build/build/tmp/work/x86_64-linux/ gcc-cross-initial-arm/6.3.0-r0/sysroot-destdir/home/pokybuild/yocto-autobuilder/yocto-worker/ nightly-arm-lsb/build/build/tmp/work/x86_64-linux/gcc-cross-initial-arm/6.3.0-r0/recipe-sysroot-native/ usr/bin/arm-poky-linux-gnueabi.gcc-cross-initial-arm/arm-poky-linux-gnueabi-gcov' failed Exception: subprocess.CalledProcessError: Command '('patchelf-uninative', '--set-interpreter', '/home/pokybuild/yocto-autobuilder/yocto-worker/nightly-arm-lsb/build/build/tmp/sysroots-uninative/ x86_64-linux/lib/ld-linux-x86-64.so.2', '/home/pokybuild/yocto-autobuilder/yocto-worker/nightly-arm-lsb/ build/build/tmp/work/x86_64-linux/gcc-cross-initial-arm/6.3.0-r0/sstate-build-populate_sysroot/ recipe-sysroot-native/usr/bin/arm-poky-linux-gnueabi.gcc-cross-initial-arm/arm-poky-linux-gnueabi-gcov')' returned non-zero exit status 1 Subprocess output: missing section headers (From OE-Core rev: 75b76eb08c7e344142f0326605aeb6b24e61e38e) (From OE-Core rev: 7265e99d0b4b662ca7f23d480f2845a309ac57fc) Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* binconfig.bbclass: fix get_binconfig_mangle()Robert Yang2017-02-231-2/+2
| | | | | | | | | | | | | | | | | | | | | | | The command was: s += " -e 's:-L${libdir}:-LOELIBDIR:;'" s += " -e 's:-I${includedir}:-IOEINCDIR:;'" s += " -e 's:OELIBDIR:${STAGING_LIBDIR}:;'" s += " -e 's:OEINCDIR:${STAGING_INCDIR}:;'" s += " -e 's:-I${WORKDIR}:-I${STAGING_INCDIR}:'" s += " -e 's:-L${WORKDIR}:-L${STAGING_LIBDIR}:'" The STAGING_LIBDIR and STAGING_INCDIR now contains WORKDIR, so the result would be incorrect like: TCL_INCLUDE_SPEC='-IFIXMESTAGINGDIRTARGET/usr/include/recipe-sysroot/usr/include/tcl8.6' Note, the "/usr/include/recipe-sysroot" is not needed. Move the last two sed commands ahead will fix the problem. (From OE-Core rev: 42e4e36de37b8e06a2ff56172d04d3ffeccfbfae) Signed-off-by: Robert Yang <liezhi.yang@windriver.com> Signed-off-by: Ross Burton <ross.burton@intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* native.bbclass: populate native recipe with it's filesSaul Wold2017-02-231-0/+5
| | | | | | | | | | | | | | This allows a native package's recipe-sysroot-native to be populated with that packages native image files. This in turns allows it to be used by scripts or other tools without creating un-necessary DEPENDS. An example of this is systemtap-native and the crosstap script. (From OE-Core rev: 7f6b4359e1f2d9d748d23305a2af73c0efba5928) Signed-off-by: Saul Wold <sgw@linux.intel.com> Signed-off-by: Ross Burton <ross.burton@intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* kernel.bbclass: do_deploy requires depmodwrapperRobert Yang2017-02-231-0/+2
| | | | | | | | | | | Fixed: run.do_deploy.27809: line 155: depmodwrapper: command not found (From OE-Core rev: 96b7eceefb3e99848d1c16d7c5da123056dcdc24) Signed-off-by: Robert Yang <liezhi.yang@windriver.com> Signed-off-by: Ross Burton <ross.burton@intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* devtool: upgrade: fix error of import recipeutilsLuck Hoang2017-02-231-0/+4
| | | | | | | | | | | upgrade.py imports oe.recipeutils in meta/lib/ but path to oe.recipeutils is not provided. This fails populate_sdk_ext. (From OE-Core rev: 5f140359f859fea9cfe8c8d9c9584bceec875adb) Signed-off-by: Luck Hoang <huyht1205@gmail.com> Signed-off-by: Ross Burton <ross.burton@intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* terminal.bbclass: export configure varsRobert Yang2017-02-231-1/+1
| | | | | | | | | | | | | | So that we can easily reproduce configure by: $ $CACHED_CONFIGUREVARS ./configure $CONFIGUREOPTS $EXTRA_OECONF [YOCTO #9423] (From OE-Core rev: a851f57de63fe527e04f2296245e9720c40f9c2e) Signed-off-by: Robert Yang <liezhi.yang@windriver.com> Signed-off-by: Ross Burton <ross.burton@intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* useradd-staticids: fix typo for '--expiredate'Peter Bergin2017-02-231-1/+1
| | | | | | | | | | | | | | | | | | | There is a typo in the useradd-staticids.bbclass that causes error during do_install. If build was configured to use usedadd-staticids and the recipe included (for example): USERADD_PARAM_${PN} = "--expiredate '' testUser" Due to the typo this added the wrong option '--expiredata ' that caused an error. (From OE-Core rev: 9d26a2f9f52ae9df6aa5e0ee20683ada35c32af1) Signed-off-by: Peter Bergin <peter@berginkonsult.se> Signed-off-by: Ross Burton <ross.burton@intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* arch-arm*.inc: squash whitespace within TUNE_FEATURES stringsAndre McCurdy2017-02-235-143/+143
| | | | | | | | | | | | | | | | | | | | | | | | TUNE_FEATURES is include in BUILDCFG_VARS, so any whitespace is visible to the user during the build process. Remove the extra whitespace added during the 2.1 development cycle: http://git.openembedded.org/openembedded-core/commit/?id=f774b44fa007a2a756ada892ede832b1251d940c For consistency, squash whitespace within PACKAGE_EXTRA_ARCHS strings too. Whitespace within TUNE_FEATURES strings in the tune-cortexa*.inc files has been fixed in a separate commit: http://git.openembedded.org/openembedded-core/commit/?id=5610c6397ee098dd998b7417b343494de77179f9 (From OE-Core rev: 3cd0c5ef748ad072f1bd9a8d42157e9643bf97eb) (From OE-Core rev: 971e43270173afb08f21ffac16a4157f7e611b81) 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>
* scripts/buildstats-diff: fix epoch numbers in --ver-diffMarkus Lehtonen2017-02-231-1/+1
| | | | | | | | | | | | | Incorrect data was printed (recipe name instead of epoch number) when displaying changes in epoch. (From OE-Core rev: 5e2b1bfb684dc76963f692172f7457c2249c3266) (From OE-Core rev: d3f4ec2ad5e83f52f7d3824cfe1f5a64f2d81bcf) Signed-off-by: Markus Lehtonen <markus.lehtonen@linux.intel.com> Signed-off-by: Ross Burton <ross.burton@intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* lib/oe/patch: Support xz-compressed patchesDominic Sacré2017-02-231-1/+1
| | | | | | | | | | | | | | Add .xz to the list of extensions recognized by patch_path(), so that compressed patches ending in .patch.xz or .diff.xz are automatically applied. (From OE-Core rev: f1a2c45765d14d3ca09657ad1f6b526554af2bb6) (From OE-Core rev: f50fd7f247d5bb05bc7d1109c574a682067688da) Signed-off-by: Dominic Sacré <dominic.sacre@gmx.de> Signed-off-by: Ross Burton <ross.burton@intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* bitbake.conf: Point KERNELORG_MIRROR to cdn.kernel.orgDominic Sacré2017-02-231-1/+1
| | | | | | | | | | | | | | | Use cdn.kernel.org to distribute the server load and improve download speeds. Leave www.kernel.org in MIRRORS as a fallback. See https://www.kernel.org/introducing-fastly-cdn.html (From OE-Core rev: 7c81b680a3cc4602c9c153398103d5477d7fd894) (From OE-Core rev: 4f09ec0e7b51cc599d6a46d41f77d6fb07a6d445) Signed-off-by: Dominic Sacré <dominic.sacre@gmx.de> Signed-off-by: Ross Burton <ross.burton@intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* oeqa/runtime/context.py: Fix use of getTarget() with testexportMariano Lopez2017-02-233-3/+16
| | | | | | | | | | | | | | | | The idea on getTarget is to use kwargs to send custom variables to different targets, instead of this, a new variable was added (just used for custom targets) and this broke testexport. So in order to fix it, just add the custom variable to kwargs. This fixes the use of getTarget() in testexport class that was introduced in 1dc8010afd71fe46fb28bb86fb7c07a5fbd3d7cf. (From OE-Core rev: cf138029a1f18f991fc7a28c81d85884942e9d56) Signed-off-by: Mariano Lopez <mariano.lopez@linux.intel.com> Signed-off-by: Ross Burton <ross.burton@intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* oeqa: fix typoHumberto Ibarra2017-02-234-12/+12
| | | | | | | | | | | | | The word 'uninstall' was spelled incorrectly in various parts of oeqa files. (From OE-Core rev: af365e025030436f83b233fa51ecc9c58c58ce3c) (From OE-Core rev: 9d25188e873645b849584b51a77b86588a51d4ba) Signed-off-by: Humberto Ibarra <humberto.ibarra.lopez@intel.com> Signed-off-by: Ross Burton <ross.burton@intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* image_types_wic: fix expansion errorEd Bartosh2017-02-231-1/+1
| | | | | | | | | | | | | | | | | | | Variable WKS_SEARCH_PATH was not fully expanded when used directly in this expression: WKS_FULL_PATH = "${@wks_search('${WKS_FILES}'.split(), '${WKS_SEARCH_PATH}') or ''}" This caused expansion error: bb.data_smart.ExpansionError: Failure expanding variable WKS_FULL_PATH, .... which triggered exception SyntaxError: invalid syntax (WKS_FULL_PATH, line 1) Calling d.getVar instead of directly referencing variables should fix the issue. (From OE-Core rev: 20f8fddd28fe46d7e694804de3d894cdf9f7c636) Signed-off-by: Ed Bartosh <ed.bartosh@linux.intel.com> Signed-off-by: Ross Burton <ross.burton@intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* layer.conf: bump version for change in eSDK selftest behaviourJoshua Lock2017-02-191-1/+1
| | | | | | | | | | | | | Since 59a99cd8 "oeqa/sdk: Updates sanity tests for minimal eSDK" we can now run oe-selftests against a minimal eSDK. We need to increase the layer version so that we can detect this change in behaviour in our automated testing. (From OE-Core rev: def3800c7e58d9d1b54ea1df27b190a0f6d1d544) Signed-off-by: Joshua Lock <joshua.g.lock@intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* ref-manual: Expanded kernel task descriptions.Scott Rifenbark2017-02-191-32/+120
| | | | | | | | | | | | Fixes [YOCTO #9376] Expanded many of the brief descriptions for the kernel-related tasks. (From yocto-docs rev: ee9e54aa9f148e5438cd9bdf7e55d7fa43cc3ec5) Signed-off-by: Scott Rifenbark <srifenbark@gmail.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* dev-manual: Minor corrections to maintaining Open Source lic. comp.Scott Rifenbark2017-02-191-10/+12
| | | | | | | | | | | The section "Maintaining Open Source License Compliance During Your Product's Lifecycle" had a vew minor typo things (e.g. duplicated word and some formatting issues). I fixed these. (From yocto-docs rev: 67beb658445e79129d8aae1739bb33c000367107) Signed-off-by: Scott Rifenbark <srifenbark@gmail.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* ref-manual: Updated NO_RECOMMENDATIONS glossary entryScott Rifenbark2017-02-191-1/+1
| | | | | | | | | | | | | Fixes [YOCTO #11010] The second example was incorrect in the glossary entry. Instead of "1" an image name place holder was in the example. I put "1" in there. (From yocto-docs rev: 00ab787d0d90da5c6d384c3669e804c9b2baca53) Signed-off-by: Scott Rifenbark <srifenbark@gmail.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* documentation: Updated "latest manual" note on title pageScott Rifenbark2017-02-199-54/+224
| | | | | | | | | | | | | | | Fixes [YOCTO #10076] The note on the title page for each manual was brief regarding where to find the latest version of the manual. I updated the note to have more detailed information on finding current, alternate, and latest versions of the manual based on YP releases. (From yocto-docs rev: 0ec81465296a7a78309d3039af4d00caa52d2285) Signed-off-by: Scott Rifenbark <srifenbark@gmail.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* selftest/containerimage.py: Add container IMAGE_FSTYPES testRandy Witt2017-02-193-0/+99
| | | | | | | | | | | | | | | | | | This test checks to make sure only the files expected exist in a container image. Currently only ROOTFS_BOOTSTRAP_INSTALL, gets added to all images without the user specifying it. But this test should help if a developer in the future ever silently adds more than just ROOTFS_BOOTSTRAP_INSTALL, and that the developer can make sure it also gets removed from a container image. [YOCTO #9502] (From OE-Core rev: 4f5e5321fafe491f91d78a35d11afc0dc0527d4b) Signed-off-by: Randy Witt <randy.e.witt@linux.intel.com> Signed-off-by: Ross Burton <ross.burton@intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* image-container.bbclass: Error if not using linux-dummyRandy Witt2017-02-191-0/+18
| | | | | | | | | | | | | | | | | | | In the typical case of a container, the user doesn't particularly care about the kernel version used. Since using linux-dummy prevents building a kernel in the most common case, alert the user if they choose a container image, but don't also specify linux-dummy. In the cases the user actually does want to build against particular kernel headers, etc, they can override by setting IMAGE_CONTAINER_NO_DUMMY = "1". [YOCTO #9502] (From OE-Core rev: f0645e172bb839803d616f19307e1e81e0d204c0) Signed-off-by: Randy Witt <randy.e.witt@linux.intel.com> Signed-off-by: Ross Burton <ross.burton@intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* image-container.bbclass: Add the "container" IMAGE_FSTYPESRandy Witt2017-02-193-0/+7
| | | | | | | | | | | | | The "container" fstype does very little other than pick tar.bz2 as the actual image type and disable installation of ROOTFS_BOOTSTRAP_INSTALL. [YOCTO #9502] (From OE-Core rev: e45f074b792a43aa2fd84a5a3f0e20bf1d88ad7e) Signed-off-by: Randy Witt <randy.e.witt@linux.intel.com> Signed-off-by: Ross Burton <ross.burton@intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* oeqa/selftest/bbtests: Update after changes to dependency graph file generationRichard Purdie2017-02-191-3/+3
| | | | | | (From OE-Core rev: 36a7470cacfe56931948ee865bd9ef46a7303ced) Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* bitbake: runqueue: Fix collapsed setscene dependency treeRichard Purdie2017-02-191-1/+4
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | When we removed the postinst sstate dependency handling code from setscene_depvalid, we noticed things being installed into the old style sysroot for rootfs tasks which should not have been there, causing a performance regression. Analysis revealed that setscene dependencies were "bubbling" over sstate tasks when they should have been stopping there. The 'continue' added by this patch avoids this issue and eusures sstate tasks remain contained to their specific chains. There was another bug in the code this exposed where the acconting for tasks as they were removed from sq_revdeps was not correct. In fixing this, what looks like a workaround in another test can then be simplified. After this change, populate_sysroot tasks are no longer depending on package_write_rpm tasks for example, which would make no sense. A before/after analysis of image dependencies only revealed improved dependencies after this change. Recipe specific sysroots did highlight the issue here since the behaviour of the sysroot dependencies (and processing with depvalid) was not matching what bitbake itself was doing, with bitbake being incorrect. Failures were 'safe' in that too many dependencies would get installed. (Bitbake rev: 5ef2cb50041fa7106c8de170af73d2a54cb0b1f0) Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* bitbake: bitbake-layers: Handle exception raised bytinfoil.prepare()Aníbal Limón2017-02-191-10/+3
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | The tinfoil.prepare method can raise Exceptions when is parsing initial data so add this call inside try, finally to avoid get blocked for don't call tinfoil.shutdown(). The tinfoil_init function was remove because isn't make sense now since tinfoil.prepare() needs to be inside try, finally closures. Example of raised exception and gets blocked: $ bitbake-layers add-layer ~/repos/meta-openembedded/meta-python/ Traceback (most recent call last): File "/home/alimon/repos/poky/bitbake/bin/bitbake-layers", line 83, in main tinfoil.prepare(True) ... File "/home/alimon/repos/poky/bitbake/lib/bb/tinfoil.py", line 268, in run_command raise TinfoilCommandFailed(result[1]) bb.tinfoil.TinfoilCommandFailed: Traceback (most recent call last): File "/home/alimon/repos/poky/bitbake/lib/bb/command.py", line 81, in runCommand result = command_method(self, commandline) ... File "/home/alimon/repos/poky/bitbake/lib/bb/cooker.py", line 1314, in handleCollections raise CollectionError("Errors during parsing layer configuration") bb.cooker.CollectionError: Errors during parsing layer configuration (Bitbake rev: 61ebe9a026652e32f9482f66fc3fe7a8672fc093) Signed-off-by: Aníbal Limón <anibal.limon@linux.intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* bitbake: tinfoil: ensure PATH includes bitbake's bin directoryPaul Eggleton2017-02-191-0/+13
| | | | | | | | | | | | | | | | | The runqueue expects to be able to run 'bitbake-worker' from PATH, but for example in the OE extensible SDK, tinfoil is used within devtool where this isn't the case (we're not exposing bitbake to the user, thus bitbake's bin directory isn't in PATH). This fixes devtool modify usage within the extensible SDK which has apparently been broken since the tinfoil2 changes went in. Fixes [YOCTO #11034]. (Bitbake rev: 52d87e4a58a52174e8e0b6297abaac8fd93ffcc3) Signed-off-by: Paul Eggleton <paul.eggleton@linux.intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* bitbake: fetch2: Add NFS Stale file exception handlingKhem Raj2017-02-191-0/+12
| | | | | | | | | | | | | | | | | | | | - In some cases the file descriptor is held by nfs client and none of os.path.* is catching that, it could mean that error is not doled out because client has cached the stat info. In this case we are out of luck. Needed to catch IOError, which would be causing the Stale error. - In download method, update_stamp is invoked md5sum validation which is found to be throwing Stale errors. - Added error handling to fix the stale errors. (Bitbake rev: 5a53e7d7b017769a6eb0f0a6335735a1fe51a5ec) Signed-off-by: Balaji Punnuru <balaji_punnuru@cable.comcast.com> Signed-off-by: Khem Raj <raj.khem@gmail.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* bitbake: fetch2: Rename "setup_revisons" to "setup_revisions"Robert P. J. Day2017-02-196-6/+6
| | | | | | | | | | For spelling's sake, rename Python routine "setup_revisons" to "setup_revisions." (Bitbake rev: 4df59b027c02ef39d72476251ccd3fd62fc20bf6) Signed-off-by: Robert P. J. Day <rpjday@crashcourse.ca> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* bitbake: fetch2: Correct two examples of typo "revsion."Robert P. J. Day2017-02-192-2/+2
| | | | | | | (Bitbake rev: 05f5421b2e44cd58c5912848de43d5884d070150) Signed-off-by: Robert P. J. Day <rpjday@crashcourse.ca> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* bitbake: cooker: detect malformed BBMASK expressions which begin with a ↵Andre McCurdy2017-02-191-0/+5
| | | | | | | | | | | | separator When constructing an older style single regex, it's possible for BBMASK to end up beginning with '|', which matches and masks _everything_. (Bitbake rev: 56ad67017e601c7e0f6085ca84e29c28d8d4519f) Signed-off-by: Andre McCurdy <armccurdy@gmail.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* bitbake: cooker: Rewrite dependency dot file generationRichard Purdie2017-02-192-62/+49
| | | | | | | | | | | | | | | | | | | | | | | | The package-depends.dot and pn-depends.dot files are inaccurate, missing out key dependencies such those made via the [depends] flags. As such they can be misleading to the user. They mainly exist for historical reasons, coming from a time before we had task based execution. This commit removes the two dated file formats and replaces them with a recipe-depends.dot which is a flattened version of task-depends.dot. The old format files are removed if present so that the user can't get confused about why data might not match between files. The code is also rewritten to use 'with f: f.write()' syntax as is more commonly used now. Also update the docs to match the change. (Bitbake rev: d3e182bc18ff2894f1efc8aad3d508dd432c996e) Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* bitbake: doc: Replace depexp UI with taskexp and cleanup UI listsRichard Purdie2017-02-192-2/+2
| | | | | | | | | The depexp UI has been replaced with taskexp, also remove old references to goggle and hob. (Bitbake rev: 814c2b232ea5f88b5ad5031fb9d389c9c594aa01) Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* bitbake: ui: Replace depexp with taskexpRichard Purdie2017-02-191-25/+9
| | | | | | | | | | | | | | The data displayed by the depexp UI is buggy, bitbake can't convey accurate runtime dependency information. Convert the UI to become taskexp ("Task Explorer") which provides a graphical way of exploring the task-depends.dot file. This data is accurate and being able to visualise the data is an often requested feature as standard dot file viewers can't usualy cope. (Bitbake rev: 416a496edc692982af2feec768ac4df8fb799853) Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* wget: Upgrade 1.19 -> 1.19.1Richard Purdie2017-02-191-2/+2
| | | | | | | | This fixes musl build issues and avoids autobuilder failures. (From OE-Core rev: 3a31d04b49efdc4d899d7da9f16e1899256f497d) Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* rootfspostcommands: remove shadow backup files instead of trying to sortPatrick Ohly2017-02-191-8/+20
| | | | | | | | | | | | | Backup are files sometimes are inconsistent and then cannot be sorted (YOCTO #11043), and more importantly, are not needed in the initial rootfs, so they get deleted. Fixes: [YOCTO #11007] (From OE-Core rev: e5628c80a52f3caeea9d9dc7f67d1b8a61222aef) Signed-off-by: Patrick Ohly <patrick.ohly@intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* linux-yocto-rt/4.9: update to 4.9-rt6Bruce Ashfield2017-02-193-4/+4
| | | | | | | | | Updating the SRCREVs to make Paul Gortmaker's port of 4.9-rt6 active. (From OE-Core rev: b3e3ef85f5fd64473cae4aa72243665ac1e618e9) Signed-off-by: Bruce Ashfield <bruce.ashfield@windriver.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-14 19:36:16 +0000