summaryrefslogtreecommitdiffstats
Commit message (Collapse)AuthorAgeFilesLines
* ref-manual: Added more to migration 2.2 runqemu ported to python.Scott Rifenbark2016-10-191-0/+75
| | | | | | | | | | Provided more detail on what the user can do with configuration files to use the changed runqemu. (From yocto-docs rev: 5dee8ceca290fdc8f3b41e0eba6565494190ce4f) Signed-off-by: Scott Rifenbark <srifenbark@gmail.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* ref-manual: Updated the 2.2 Migration section with review changes.Scott Rifenbark2016-10-191-55/+119
| | | | | | | (From yocto-docs rev: 4af78f942bedb55e46280bc0fc878f174e15b479) Signed-off-by: Scott Rifenbark <srifenbark@gmail.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* ref-manual: Added links for migration BitBake change.Scott Rifenbark2016-10-191-1/+4
| | | | | | | | | | I did not put in the links for a couple commits for some of the 2.2 bitbake changes. Put in the links. (From yocto-docs rev: a806463a07ab07ce9da23d6bb73cb981b85b668e) Signed-off-by: Scott Rifenbark <srifenbark@gmail.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* ref-manual: Fixed missing title for migration section.Scott Rifenbark2016-10-191-0/+2
| | | | | | | (From yocto-docs rev: 81645a11c4e27daa30891265e9a1ea2c3c2682cc) Signed-off-by: Scott Rifenbark <srifenbark@gmail.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* ref-manual: Added the 2.2 Migration guide section.Scott Rifenbark2016-10-191-0/+427
| | | | | | | (From yocto-docs rev: 668e32419ba59d975a196967e620c384009426a4) Signed-off-by: Scott Rifenbark <srifenbark@gmail.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* ref-manual: Added note to RM_OLD_IMAGE indicating redundancyScott Rifenbark2016-10-191-0/+7
| | | | | | | | | | | The way these old image files are staged now makes removing them the default behavior. Thus, this variable has become redundant. I added a note indicating such. (From yocto-docs rev: e1db620fdf741b46e54cf1a3715597f81a811818) Signed-off-by: Scott Rifenbark <srifenbark@gmail.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* ref-manual: Changed BB_SETSCENE_VERIFY_FUNCTION nameScott Rifenbark2016-10-191-1/+1
| | | | | | | | | | | The BB_SETSCENE_VERIFY_FUNCTION variable has effectively changed names to be BB_SETSCENE_VERIFY_FUNCTION2. I made the one instance of it correct here. (From yocto-docs rev: c2864dace370d7a43234f4728b33f25082e628e3) Signed-off-by: Scott Rifenbark <srifenbark@gmail.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* build-appliance-image: Update to master head revisionRichard Purdie2016-10-191-1/+1
| | | | | | (From OE-Core rev: 327e4bf5a84d5b49ccc65927df622c9ef6302d55) Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* bitbake: toaster: Update default release to Mortybrian avery2016-10-151-1/+1
| | | | | | | | | | | Set Morty to be the default release in toaster for the Morty release when creating new projects. (Bitbake rev: 00f79096f639ce3a9c0b7c72cfb36f14e264733d) Signed-off-by: brian avery <brian.avery@intel.com> Signed-off-by: Michael Wood <michael.g.wood@intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* bitbake: toaster: Update poky fixture for Morty releasebrian avery2016-10-151-6/+6
| | | | | | | | | | | | | Update the poky fixture to the Morty release. This removes the master branch from the release and limits it to the morty branch. Normally, we would also support at least one past branch but the change from Python 2.7 -> Python 3 makes that infeasible. (Bitbake rev: 2674ca33b900f4f3f16be504d7c67d0fc69c1c2d) Signed-off-by: brian avery <brian.avery@intel.com> Signed-off-by: Michael Wood <michael.g.wood@intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* bitbake: toaster: Update oe-core fixture for Morty releasebrian avery2016-10-151-8/+8
| | | | | | | | | | | | | Update the oe-core fixture to the Morty release. This removes the master branch from the release and limits it to the morty branch. Normally, we would also support at least one past branch but the change from Python 2.7 -> Python 3 makes that infeasible. (Bitbake rev: 93f1e6c3d022b1f12a230879160efa941cb1e250) Signed-off-by: brian avery <brian.avery@intel.com> Signed-off-by: Michael Wood <michael.g.wood@intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* linux-yocto: Update genericx86* SRCREVs for linux-yocto 4.4 Upgrades to ↵Alejandro Hernandez2016-10-151-4/+4
| | | | | | | | | | Linux 4.4.22 (From meta-yocto rev: 231154919669d30f1f82d4fc9e3fbd47408e6ec5) Signed-off-by: Alejandro Hernandez <alejandro.hernandez@linux.intel.com> Signed-off-by: Ross Burton <ross.burton@intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* linux-yocto: Update genericx86* SRCREVs for linux-yocto 4.1 Upgrades to ↵Alejandro Hernandez2016-10-151-4/+4
| | | | | | | | | | Linux 4.1.33 (From meta-yocto rev: 6d0a183706cfe89367d4d1eeb11472411e3d2341) Signed-off-by: Alejandro Hernandez <alejandro.hernandez@linux.intel.com> Signed-off-by: Ross Burton <ross.burton@intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* README.hardware: update Edgerouter sectionEd Bartosh2016-10-151-56/+6
| | | | | | | | | | | | | Updated image creation instructions. Used wic images instead of manually putting rootfs and kernel to SD card. [YOCTO #8719] (From meta-yocto rev: 2b030a6061a33334bec63fce23447cbbe1846c86) 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>
* edgerouter.conf: produce wic images for EdgerouterEd Bartosh2016-10-151-1/+5
| | | | | | | | | | | | | Added wic images to the list of default image types for Edgerouter machine. Added required wic dependencies. [YOCTO #8719] (From meta-yocto rev: 7abb3ec529bd7754fc15ecf30e078d90d8014569) 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>
* poky-tiny.conf: set QB_DEFAULT_FSTYPE to IMAGE_FSTYPESRobert Yang2016-10-151-0/+2
| | | | | | | | | | | | | | Its IMAGE_FSTYPES is cpio.gz, not the default ext4 which is set in qemuboot.bbclass. Now we can boot it by: $ runqemu tmp/deploy/images/qemux86/ nographic [YOCTO #7477] (From meta-yocto rev: 4c9792bbc8ac09417787838609aa5d466e3d0c77) 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>
* README.hardware: update Beaglebone sectionEd Bartosh2016-10-151-48/+6
| | | | | | | | | | | | | Updated image creation instructions. Used wic images instead of manually partitioning SD card. [YOCTO #8719] (From meta-yocto rev: aaa23941f228f08573b0e4901e8bf3fd5f1c97e3) 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>
* bitbake: bb.event: fix infinite loop on print_ui_queueAníbal Limón2016-10-151-2/+2
| | | | | | | | | | | | | | | | | | | | | | | | | If bitbake ends before _uiready and bb.event.LogHandler was add to the bitbake logger it causes an infinite loop when logging something. The scenario is print_ui_queue is called at exit and executes the log handlers [2] one of them is bb.event.LogHandler this handler appends the same entry to ui_queue causing the inifine loop [3]. In order to fix a new copy of the ui_queue list is created when iterate ui_queue. [YOCTO #10399] [1] https://bugzilla.yoctoproject.org/show_bug.cgi?id=10399#c0 [2] http://git.openembedded.org/bitbake/tree/lib/bb/event.py?id=41d9cd41d40b04746c82b4a940dca47df02514fc#n156 [3] http://git.openembedded.org/bitbake/tree/lib/bb/event.py?id=41d9cd41d40b04746c82b4a940dca47df02514fc#n164 (Bitbake rev: 46fecca9d531a07788b5cac8b2dc6a8267d8b6d0) Signed-off-by: Aníbal Limón <anibal.limon@linux.intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* binutils: Fix gas error with cfi_section inconsistenciesKhem Raj2016-10-152-0/+98
| | | | | | | | | | | | | | This error is visible when using clang but not when using gcc this has been reported and fixed upstream. llvm bug https://llvm.org/bugs/show_bug.cgi?id=29017 binutils bug https://sourceware.org/bugzilla/show_bug.cgi?id=20648 (From OE-Core rev: e5a81575f11dc2a0ec9ee4184514750d2dbd09aa) 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>
* libxml2: Make tests non-executableJussi Kukkonen2016-10-151-0/+5
| | | | | | | | | | | | | | The XML W3C conformance test suite contains thousands of xml files all marked executable. We dutifully try to strip all these files of debug info in do_package. "chmod -x" improves build time by ~40 seconds. (From OE-Core rev: eb9cdf6b9277d23d1696233fccc4689e6030644c) 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>
* bind: fix two CVEsZheng Ruoqin2016-10-153-0/+215
| | | | | | | | | | | | | | Add two CVE patches from upstream git: https://www.isc.org/git/ 1.CVE-2016-2775.patch 2.CVE-2016-2776.patch (From OE-Core rev: 5f4588d675e400f13bb6001df04790c867a95230) Signed-off-by: zhengruoqin <zhengrq.fnst@cn.fujitsu.com> Signed-off-by: Ross Burton <ross.burton@intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* rpm: prevent race in tempdir creationMarkus Lehtonen2016-10-153-24/+44
| | | | | | | | | | | | | | This patch fixes an extramely rare race condition in creation of rpmdb temporary directory. The "rpmdb-more-verbose-error-logging" patch is still left in place, just for the case. [YOCTO #9416] (From OE-Core rev: 84de3283fa2a2908d367eb58953903ae685b0298) 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>
* insane.bbclass: fix package_qa_check_arch() for mips64-o32Robert Yang2016-10-151-4/+6
| | | | | | | | | | | | | | | | | | | | | | | | | | | Fixed: MACHINE = "qemumips64" DEFAULTTUNE = "mips64-o32" $ bitbake linux-yocto ERROR: linux-yocto-4.8+gitAUTOINC+03bf3dd731_674818dad5-r0 do_package_qa: QA Issue: Bit size did not match (32 to 64) linux-yocto on /work/qemumips64-poky-linux/linux-yocto/4.8+gitAUTOINC+03bf3dd731_674818dad5-r0/packages-split/kernel-module-parport/lib/modules/4.8.0-yocto-standard/kernel/drivers/parport/parport.ko [arch] The mips64-n32 works since it would set ABIEXTENSION to "n32" so that TARGET_OS is linux-gnun32, and it will skip the check, but "mips64-o32" doesn't set ABIEXTENSION to "o32", "n32" or "32", so the error happend. Skip the check if mips64.*32 matches DEFAULTTUNE can fix the problem. Another way to fix the problem is define ABIEXTENSION to "o32" or "32" for mips64-o32, but that may make things confused since "o32" is purely 32 bit. [YOCTO #10305] (From OE-Core rev: 4e61d8d6f4619dbfaeb5ca642449de7cf4b3e92d) 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>
* arch-mips.inc: remove duplicates from PACKAGE_ARCHSRobert Yang2016-10-151-1/+1
| | | | | | | | | | | | | | | | | | | Fixed: MACHINE = "qemumips64" DEFAULTTUNE = "mips64-o32" $ bitbake linux-yocto ERROR: OE-core's config sanity checker detected a potential misconfiguration. Either fix the cause of this error or at your own risk disable the checker (see sanity.conf). Following is the list of potential problems / advisories: Error, the PACKAGE_ARCHS variable contains duplicates. The following archs are listed more than once: mips64-o32 (From OE-Core rev: e57d70e6803c63823ae3a7c7971fc06db3748b68) 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>
* ppp: fix building with linux-4.8Jackie Huang2016-10-152-0/+45
| | | | | | | | | | | | | | | | | | | | | | Fix a build error when using the linux-4.8 headers that results in: In file included from pppoe.h:87:0, from plugin.c:29: ../usr/include/netinet/in.h:211:8: note: originally defined here struct in6_addr ^~~~~~~~ In file included from ../usr/include/linux/if_pppol2tp.h:20:0, from ../usr/include/linux/if_pppox.h:26, from plugin.c:52: ../usr/include/linux/in6.h:49:8: error: redefinition of 'struct sockaddr_in6' struct sockaddr_in6 { ^~~~~~~~~~~~ (From OE-Core rev: 68e917aa778742da104c038a6e1ffa789fe95410) Signed-off-by: Jackie Huang <jackie.huang@windriver.com> Signed-off-by: Ross Burton <ross.burton@intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* Revert "linux-libc-headers: fix in/if.h includes"Jackie Huang2016-10-152-87/+0
| | | | | | | | | | | This issue is fixed in the ppp recipe. This reverts commit 7c6b78ac8e2b176f77178c3dd12d8455be10845d. (From OE-Core rev: efc92a63d40b909864505d3d6d22ce74cd6a847b) Signed-off-by: Ross Burton <ross.burton@intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* populate_sdk_ext: explicitly set DL_DIRRoss Burton2016-10-151-0/+2
| | | | | | | | | | | | | | | | | | | | | | | | The eSDK generation assumes that DL_DIR is downloads/ under the build directory, and puts files such as a freshly buily uninative tarball in there expecting bitbake will find it later. Whilst ${TOPDIR}/downloads/ is in fact the default value for DL_DIR in bitbake.conf, and any instances of DL_DIR are removed from the original local.conf, there is still the possibility that other layers could contain a site.conf that assigns DL_DIR. If this happens the errors are quite mysterious as it fails to find the uninative tarball and so the hashes all change, and eSDK building fails. Ensure that this cannot happen by explicitly assigning the DL_DIR that we require, instead of assuming that the default value will be used. [ YOCTO #10439 ] (From OE-Core rev: bc2e6f5eab47e869dbc4a3eacfe759b9b1cacaee) Signed-off-by: Ross Burton <ross.burton@intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* sqlite3: Revert ad601c7962 from 3.14.1 amalgamation packageJianxun Zhang2016-10-152-1/+60
| | | | | | | | | | | | | | | | | | | | | | It turns out this change between 3.12.2 and 3.13 introduces a 2% increase of build time based on statistic data in bz10367. The added patch is forged by diffing the new sqlite3.c generated from reverting the change in raw source of sqlite3 project, and then manually migrate the delta to a sqlite3.c from the 3.14.1 tarball package because what recipes reference is actually a generated C code (amalgamation) release package and we cannot apply the real change to 3.14.1 cleanly due to so many changes happened. Fixes [YOCTO #10367] (From OE-Core rev: dda0c80019b181a5e323a82d346f86c6fffb6756) Signed-off-by: Jianxun Zhang <jianxun.zhang@linux.intel.com> Signed-off-by: Ross Burton <ross.burton@intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* linux-yocto.inc: ensure do_kernel_link_images runs before do_stripAndre McCurdy2016-10-151-1/+1
| | | | | | | | | | | | | If the do_kernel_link_images task is enabled, then it needs to run before do_strip. The addtask statement for do_strip makes that explicit. For consistency, make it explicit in the addtask statement for do_kernel_link_images too. (From OE-Core rev: 1296cc0538efe64d666868fd28c5b195ec9c08ff) 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>
* binutils: fix for MIPS "Can't find matching LO16 reloc" errorsAndre McCurdy2016-10-152-0/+66
| | | | | | | | | | | | Patch taken from Binutils Bugzilla: https://sourceware.org/bugzilla/show_bug.cgi?id=20649 (From OE-Core rev: a31eff6894099ee1d0ce7ccf2972f7276ca12743) 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>
* libgpg-error: Make case generic for MIPSZubair Lutfullah Kakakhel2016-10-151-2/+2
| | | | | | | | | | | | | | | | | The tuples for MIPS r6 onwards are - mipsisa32r6el - mipsisa32r6 - mipsisa64r6el - mipsisa64r6 The default case passes it forward which isn't handled well and causes a build error. Rework the case statement to make it generic. (From OE-Core rev: 49dc626182694d4dd92ed921a8fa2d9cd9f49635) Signed-off-by: Zubair Lutfullah Kakakhel <Zubair.Kakakhel@imgtec.com> Signed-off-by: Ross Burton <ross.burton@intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* live-vm-common.bbclass: Allow to use different kernel image than ↵Martin Jansa2016-10-151-2/+6
| | | | | | | | | | | | | | KERNEL_IMAGETYPE for /vmlinuz * syslinux config hardcodes kernel image as /vmlinuz add warning message when the selected image doesn't exist and allow to select different image with VM_DEFAULT_KERNEL variable (qemuboot.bbclass is using QB_DEFAULT_KERNEL) (From OE-Core rev: e6b21d1b3716ee6f4aec1674e56f06b2963a7968) Signed-off-by: Martin Jansa <Martin.Jansa@gmail.com> Signed-off-by: Ross Burton <ross.burton@intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* image_types.bbclass: add dependency do_image_wic -> do_bootimgEd Bartosh2016-10-151-0/+5
| | | | | | | | | | | | | | | | | | To produce certain types of images wic uses do_bootimg results to assemble final image. For example, it copies BOOT/EFI directory produced by do_bootimg to boot partition for every EFI image. The tricky part of this is that do_bootimg task is not always run, so we can't always make do_image_wic depend on do_bootimg. We only need to do it if do_bootimg present in task graph. Thank to Cristopher Larson for this fix. (From OE-Core rev: 1a961b4becf677c9eb07c5b24a8ddb75044663d1) 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>
* libxcb: use python3 to build itRobert Yang2016-10-152-0/+65
| | | | | | | | | | | Backport Fix-inconsistent-use-of-tabs-vs.-space.patch to make it can be built by python3. (From OE-Core rev: c488656825accf4543754cb712256a775d5a92e7) 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>
* xcb-proto: fix for python3Robert Yang2016-10-153-1/+294
| | | | | | | | | | Backport two patches to make it py3 friendly. (From OE-Core rev: 647ff3bed1823b53a41a5c2640ffc5f4d50d1e11) 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>
* xcb-proto: create .pyc files for python2Robert Yang2016-10-151-0/+7
| | | | | | | | | | | | Its Makefile's do_install creates .pyc files for python3, now also create them for python2 so that they will be recorded by manifest, and can be cleaned correctly. (From OE-Core rev: 3007f8b365270c35fdb1829d83affd98d8d5475a) 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>
* package_tar: avoid chdir warnings and restore cwd after packagingRobert Yang2016-10-151-0/+5
| | | | | | | | | | | Fixed: WARNING: attr-2.4.47-r0 do_package_write_tar: Task do_package_tar changed cwd to /path/to/attr/2.4.47-r0/packages-split/attr-locale-sv (From OE-Core rev: 3753d07c9ff33b9a97aca61ad312b0e283c4c68d) 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>
* source-highlight: use with-boost-libdirRobert Yang2016-10-151-1/+1
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | Without with-boost-libdir, it checks lib64 libx32 lib lib64 in sysroot/usr/ and set it as boost lib path if it exist, this is unreliable when build with multilib. Fixed when switch baselib from lib64 to lib, for example, when we build qemux86-64 + multilib setting, the baselib is lib64, and when disable multilib, it would be lib, then we may see the error when do_configure since lib64 may exist during build source-highlight: configure: error: Could not find a version of the Boost::Regex library! Steps to reproduce: MACHINE = "qemux86-64" require conf/multilib.conf MULTILIBS = "multilib:lib32" DEFAULTTUNE_virtclass-multilib-lib32 = "x86" $ bitbake world Then: MACHINE = "qemux86-64" $ bitbake source-highlight (From OE-Core rev: 98f521fff9bbeb1f7f40a009620884ec664992d7) 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>
* insane.bbclass: Additional "mips" and "mipsel" machine definitionsJuro Bystricky2016-10-151-0/+2
| | | | | | | | | | | | | | Add "mips" and "mipsel" to "machdata" table. Although there is a way to add entries to the "machdata" table from a BSP without modifying the insane.bbclass directly, MIPS is already supported in poky and as such the relevant entries should be present in insane.bbclass. (From OE-Core rev: 3ba03d1affa6f647e9a03c8ba4389606a0da8e8b) Signed-off-by: Juro Bystricky <juro.bystricky@intel.com> Signed-off-by: Ross Burton <ross.burton@intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* kernel-arch.bbclass: Add xtensa and arc into valid_archs tableJuro Bystricky2016-10-151-1/+1
| | | | | | | | | | | Both "arc" and "xtensa" are valid Linux architectures, add them into valid_archs table. (From OE-Core rev: 20d511cd1b7fe4891f7842be12f13a92da433c46) Signed-off-by: Juro Bystricky <juro.bystricky@intel.com> Signed-off-by: Ross Burton <ross.burton@intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* libxrender: remove spurious build dependencyRoss Burton2016-10-151-1/+1
| | | | | | | (From OE-Core rev: 225c6657938b2bb6ef14a8493a4f9623ce745f4b) Signed-off-by: Ross Burton <ross.burton@intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* libxext: remove spurious dependenciesRoss Burton2016-10-151-1/+1
| | | | | | | (From OE-Core rev: 93b91ae84a8c4b479da2f6fdf1f45db7da730a20) Signed-off-by: Ross Burton <ross.burton@intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* libxext: remove stale git recipeRoss Burton2016-10-151-24/+0
| | | | | | | (From OE-Core rev: 8af49df09496c00a4afbe01beb86938eac3489dd) Signed-off-by: Ross Burton <ross.burton@intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* cmake: improve CMAKE_SYSTEM_PROCESSOR assignment in nativesdkRoss Burton2016-10-151-2/+4
| | | | | | | | | | | | | | The previous string manipulations would result in the wrong string being used for machines such as intel-corei7-64 as the sysroot was split at the first hyphen (so would result in corei7 instead of corei7-64). Change the logic so that it looks for processor-distro-os and uses the whole of the processor field. (From OE-Core rev: ce24958d644f2218d5415be574a5b7e1ee8c9b2d) Signed-off-by: Ross Burton <ross.burton@intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* cmake: also set CMAKE_FIND_ROOT_PATH_MODE_PACKAGERoss Burton2016-10-151-0/+2
| | | | | | | | | | | The other CMAKE_FIND_ROOT_PATH_MODE_* variables were already set to ONLY, but PACKAGE was left out. Fix this so that cmake doesn't look on the host for cmake modules when it should only be looking in the target sysroot. (From OE-Core rev: 2df2372a31b02eab933e4a7aa6d5f8ca48e02c04) Signed-off-by: Ross Burton <ross.burton@intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* base-files: fix profile error under < /dev/nullRichard Tollerton2016-10-151-2/+4
| | | | | | | | | | | | | | Previous attempts to constrain execution of `resize` to only TTYs did not properly handle situations when `tty` would return the string "not a tty". The symptom is "/etc/profile: line 34: test: too many arguments". Fix this by utilizing the exit code of `tty`. Also use `case` instead of `cut` to eliminate a subshell. (From OE-Core rev: e67637e4472ff3a1e2801b84ee3d69d4e14b9efc) Signed-off-by: Richard Tollerton <rich.tollerton@ni.com> Signed-off-by: Ross Burton <ross.burton@intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* x86-base: Update version to 4.8Saul Wold2016-10-151-1/+1
| | | | | | | | | | | This update will avoid confusion with other parts of OE-Core that set the kernel version to 4.8 for qemux86* and genericx86*. (From OE-Core rev: 7f8c36d8aa00da109e842c790c6a0ab7a849de72) 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>
* pixbufcache: handle gdk-pixbuf not being presentRoss Burton2016-10-151-2/+4
| | | | | | | | | | | | | | | | | | | | | | It's possible - albeit unlikely - that gdk-pixbuf isn't present in the sysroot when a recipe inheriting this class is and the sysroot is finalised. One example would be if the sstate archive has librsvg but not gdk-pixbuf: librsvg will be extracted from the sstate but gdk-pixbuf will be built to "fill in the gap". In this situation the setscene completion hook installed by pixbufcache.bbclass will attempt to execute gdk-pixbuf-query-loaders, but that binary hasn't been installed by gdk-pixbuf yet. Also add gdk-pixbuf-native to DEPENDS in native builds to ensure that the binaries we expect will be present, as it's possible to build loaders without linking to GdkPixbuf. [ YOCTO #10420 ] (From OE-Core rev: 03cdb3366ded46cd760656e4cda0be37c1f82109) Signed-off-by: Ross Burton <ross.burton@intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* librsvg: remove redundant assignmentRoss Burton2016-10-151-2/+0
| | | | | | | | | | PIXBUFCACHE_SYSROOT_DEPS was removed in oe-core b41108, so remove this assignment to avoid confusing people reading the recipe. (From OE-Core rev: fcfd3e76eb52353345aa9a1f7ec0f9795e607493) Signed-off-by: Ross Burton <ross.burton@intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* Remove RM_OLD_IMAGE, it's no longer usefulJoshua Lock2016-10-158-38/+1
| | | | | | | | | | | | | | | | Since the move to put image deployment under sstate control in d54339d4b1a7e884de636f6325ca60409ebd95ff old images are automatically removed before a new image is deployed (the default behaviour of the sstate logic). RM_OLD_IMAGE is therefore no longer required to provide this behaviour, remove the variable and its users. (From OE-Core rev: 93631befe8b962bf99524746b49f4ebca336175c) Signed-off-by: Joshua Lock <joshua.g.lock@intel.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-06-21 22:17:37 +0000