summaryrefslogtreecommitdiffstats
Commit message (Collapse)AuthorAgeFilesLines
* gnu-config: Deal with "make clean" breakageRichard Purdie2014-10-302-0/+10
| | | | | | | | | gnu-config can't cope with a "make clean" so disable that newly enabled functionality. (From OE-Core rev: 2b0e78267df0ad708a5c15871757ca0db178621f) Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* wpa_supplicant: Improve rebuild handlingRichard Purdie2014-10-301-0/+1
| | | | | | | | | | Due to the split level nature of the wpa_suppliant sources, the standard clean methods don't work. This change ensures it picks up on changes to configuration. (From OE-Core rev: 9183ce719463b20350d2a3de5ead64b0cc642d6e) Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* cmake: Try and improve cleaning of builds when B==SRichard Purdie2014-10-301-0/+2
| | | | | | | | | | Currently if B==S for a cmake recipe, the build will not reconfigure. This patch adds code to remove the generated cmake files, meaning cmake will then be forced to regenerate them. This forces cmake to see configuration changes it may not otherwise see. (From OE-Core rev: 01f4ed0cfbc60859aabfa5bff33ed966117a05d7) Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* base.bbclass: Enable using 'make clean' for rebuildsRichard Purdie2014-10-301-1/+14
| | | | | | | | | | | | | | When something rebuilds say due to ${baselib} changing or some other key variable, software is often not rebuilt due to the fact that make detects no dependency change. By running "make clean" when these changes occur, we can at least try and ensure the correct rebuilds happen. We use the same checksum check as autotools to decide if things have changed or not. (From OE-Core rev: d06f2c089e01b7c67699800a7a54a4225233da93) Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* autotools: Use make clean for builds not supporting B != SRichard Purdie2014-10-301-1/+5
| | | | | | | | | | | | If the build doesn't support B != S, we can try running "make clean" instead to try and clean up previous objects if the hash for the task has changed. This tries to ensure that when variables like ${baselib} change, the changes are correctly accounted for. (From OE-Core rev: c2f761e2010857e2a2aad1dccf06ec39d15c1c86) Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* wic: Update bootimg-partition to use bootimg_dirTom Zanussi2014-10-301-2/+7
| | | | | | | | | | | | | | | Update bootimg-partition to use bootimg_dir instead of img_deploy_dir, to match similar usage in other plugins. As mentioned elsewhere, plugins should use the passed-in value for bootimg_dir directly if non-null, which corresponds to a user-assigned value specified via a -b command-line param, and only fetch the value from bitbake if that value is null. (From OE-Core rev: 3822f8a7b33da56ecd9144b4bcae50734fb1af81) Signed-off-by: Tom Zanussi <tom.zanussi@linux.intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* wic: Remove special-case bootimg_dirTom Zanussi2014-10-307-57/+27
| | | | | | | | | | | | | | | | | | | | The first iterations of wic very shortsightedly catered to two specific use-cases and added special-purpose params for those cases so that they could be directly given their corresponding boot artifacts. (hdddir and staging_data_dir). As more use-cases are added, it becomes rather obvious that such a scheme doens't scale, and additionally causes confusion for plugin writers. This removes those special cases and states explicitly in the help text that plugins are responsible for locating their own boot artifacts. (From OE-Core rev: 6ba3eb5ff7c47aee6b3419fb3a348a634fe74ac9) Signed-off-by: Tom Zanussi <tom.zanussi@linux.intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* Revert "wic: set bootimg_dir when using image-name artifacts"Tom Zanussi2014-10-302-11/+5
| | | | | | | | | | | | | | | | This reverts commit 7ce1dc13f91df70e8a2f420e7c3eba51cbc4bd48. This patch broke the assumption that a non-null boot_dir means a user-assigned (-b command-line param) value. Reverting doesn't break anything, since the case it was added for doesn't use the boot_dir for anything except debugging anyhow. Fixes [YOCTO #6290] (From OE-Core rev: db90f10bf31dec8d7d7bb2d3680d50e133662850) Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* wic: Update the help text to include -D (--debug)Tom Zanussi2014-10-301-6/+15
| | | | | | | | | | The --debug option is missing from the wic help text; this adds it and at the same time rearranges the usage into a more logical arrangement. (From OE-Core rev: cf5144ef241d8f4ccaa3461ae5c9f89c2cf2f8d1) Signed-off-by: Tom Zanussi <tom.zanussi@linux.intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* wic: Use overhead factor when creating partitions from rootfs directoriesTom Zanussi2014-10-302-0/+3
| | | | | | | | | | | | | | | | | | | | | | | | | When creating partitions sized to given rootfs directories, filesystem creation could fail in cases where the calculated target partition size was too small to contain the filesystem created using mkfs. This occurred in particular when creating partitions to contain very large filesystems such as those containing sdk image artifacts. This same limition is present in the oe-core image creation classes, which can be readily see by changing IMAGE_OVERHEAD_FACTOR from the default 1.3 to 1.0 and building a sato-sdk image. It should be possible to calculate required sizes exactly given the source rootfs and target filesystem types, but for now, to address the specific problem users are hitting in such situations, we'll just do exactly what oe-core does and define and use an IMAGE_OVERHEAD_FACTOR or 1.3 in those cases. Fixes [YOCTO #6863]. (From OE-Core rev: bbaef3ff5833fc1d97b7b028d7770834f62789da) Signed-off-by: Tom Zanussi <tom.zanussi@linux.intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* wic: Don't allow mkfs to fail silently in partition commandTom Zanussi2014-10-301-6/+16
| | | | | | | | | | | | | | The return code from the mkfs command used by the partition creation command was being ignored, allowing it to silently fail and leaving users mystified as to why the resulting filesystem was corrupted. This became obvious when failures occurred when creating large e.g. sdk filesystems [YOCTO #6863]. (From OE-Core rev: 8cef3b06f7e9f9d922673f430ddb3170d2fac000) Signed-off-by: Tom Zanussi <tom.zanussi@linux.intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* bitbake: buildinfohelper: Make sure we use the orm defined value for loglevelMichael Wood2014-10-301-5/+3
| | | | | | | | | | | | | We need to consistently use LogMessage.INFO/WARNING/ERROR to make sure toaster knows how to categories these rather than passing in the "raw" loglevel value which in best case comes from python logging but worst case any value. [YOCTO 6885] (Bitbake rev: 3aa13bc1d8218c97c76581a895fa5f03ff807fbe) Signed-off-by: Michael Wood <michael.g.wood@intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* image.py: Fix error in graph sortingPascal Bach2014-10-301-1/+1
| | | | | | | | | | | | | The graph sorting algorithm for image dependencies does a look for an occurrence of a searched string instead of comparing the chunk to the searched string. This leads to the problem that ubifs is recognized as ubi aswell. This fixes this by splitting up the string into chunks. (From OE-Core rev: cec9725c540c2d54c27092e40d159694cea75b5f) Signed-off-by: Pascal Bach <pascal.bach@siemens.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* multilib.conf: set MULTILIB_GLOBAL_VARIANTS conditionallyPeter Seebach2014-10-301-1/+1
| | | | | | | | | | | | It is not entirely obvious that all reasonable configurations will have multilib.conf strictly before the file which might want to set MULTILIB_GLOBAL_VARIANTS. The x86-ish values here look like reasonable default guesses, but shouldn't override an explicit setting. (From OE-Core rev: 2645c07892abe79f73379b1ca4196f593cb3b330) Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* mklibs: Fix loader for mipselKhem Raj2014-10-303-1/+20
| | | | | | | | | | Additionally treat ld.so to be searched in sysroot Change-Id: I8b4acb821d9855a1163c7149bc8e369c7c438856 (From OE-Core rev: 4cf539e67333ba2c3fe924b092e104da53e68ca0) Signed-off-by: Khem Raj <raj.khem@gmail.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* glibc: Delete ldconfig when USE_LDCONFIG is not setKhem Raj2014-10-301-1/+2
| | | | | | | | | | | This avoids below QA error/warning /sbin/ldconfig [installed-vs-shipped] Change-Id: I028b692eefeaa6e0e0e6507ab4108caa29e41e91 (From OE-Core rev: 2b499db19cd9bd14292457716b50dc62ed90515d) Signed-off-by: Khem Raj <raj.khem@gmail.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* rm_work: Speed up rootfs/populate_sdk removalRichard Purdie2014-10-301-0/+13
| | | | | | | | | | | | | | Commands like bitbake X -c rootfs or bitbake X -c populate_sdk do not trigger rm_work to clean up the directories afterwards since it traditionally hooks onto do_build. This change means those two tasks now clean up after themselves. We use the cleandirs function attribute to handle this. [YOCTO #6413] (From OE-Core rev: 6bf06d80c2ce03dfdedac5ad8cf42ef8e36b0ecb) Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* gcc: poison default sysroot pathRichard Purdie2014-10-306-9/+9
| | | | | | | | | | | | | | | | | | | Various pieces of the code assume that the --sysroot option gets passed into the compiler tools. By having a "sane" default, we don't always spot when this occurs and this can later show up as breakage in sstate, or in usage of the external toolchain. We've long since talked about poisoning the default such that it will break unless the correct option is specified. This patch does just that. If this patch causes something to fail to build, it most likely means the various compiler flags and commands are not correctly being passed through to the underlying piece of software and that there is a real problem that needs fixing, its not the fault of this patch. (From OE-Core rev: 04b725511a505c582a3abdf63d096967f0320779) Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* ref-manual: Updates to the migrating to YP 1.7 section.Scott Rifenbark2014-10-281-56/+88
| | | | | | | | | | Some minor wording changes and a new section added for local.conf QEMU changes. Also, reordered some sections. (From yocto-docs rev: 65207b6afa6df7d82cd3482d61f10b308da6fac7) Signed-off-by: Scott Rifenbark <scott.m.rifenbark@intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* dev-manual: Updates to "Performing Automated Runtime Testing"Scott Rifenbark2014-10-281-4/+103
| | | | | | | | | | | Updated the section to account for some new variables and several more ways to run tests against expanded targets. Also added power control section. (From yocto-docs rev: a0f08466c00ae51a99d790fa6c9dccef2e0f1518) Signed-off-by: Scott Rifenbark <scott.m.rifenbark@intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* ref-manual: Added some new test variables:Scott Rifenbark2014-10-281-0/+68
| | | | | | | | | | | | * TEST_SERIALCONTROL_CMD * TEST_SERIALCONTROL_EXTRA_ARGS * TEST_POWERCONTROL_CMD * TEST_POWERCONTROL_EXTRA_ARGS (From yocto-docs rev: 25f196cc03178f07201ef183fb309721d412e971) Signed-off-by: Scott Rifenbark <scott.m.rifenbark@intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* ref-manual: Updated list of supported distros.Scott Rifenbark2014-10-281-0/+2
| | | | | | | | | Added Debian 7.5 and 7.6 to the list. (From yocto-docs rev: 35fd5d5399fe1759158aef19d7b6eb68f2a1af12) Signed-off-by: Scott Rifenbark <scott.m.rifenbark@intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* bitbake: prserv: don't wait until exit to syncBen Shelton2014-10-282-0/+21
| | | | | | | | | | | | | | | | | In the commit 'prserv: Ensure data is committed', the PR server moved to only committing transactions to the database when the PR server is stopped. This improves performance, but it means that if the machine running the PR server loses power unexpectedly or if the PR server process gets SIGKILL, the uncommitted package revision data is lost. To fix this issue, sync the database periodically, once per 30 seconds by default, if it has been marked as dirty. To be safe, continue to sync the database at exit regardless of its status. (Bitbake rev: 424df64f2e9679043f0ce2b4f7dfc59c3d404304) Signed-off-by: Ben Shelton <ben.shelton@ni.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* bitbake: utils.py: don't use len() for truth value testing.Oscar Utbult2014-10-281-1/+1
| | | | | | | (Bitbake rev: 4bdfeab7845bdcd62a4928200dd13701414a464e) Signed-off-by: Oscar Utbult <oscar@oscr.io> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* bitbake: fetch2: add .lz compression supportKoen Kooi2014-10-281-1/+5
| | | | | | | | | | See http://www.nongnu.org/lzip/lzip.html for details on the compression format. (Bitbake rev: 9027b1273b5405c7269b013604ab417771b5eafe) Signed-off-by: Koen Kooi <koen@dominion.thruhere.net> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* nativesdk-cmake: Adjust toolchain paths dynamicallyOtavio Salvador2014-10-243-0/+33
| | | | | | | | | | | This patch adds a flexible way to configure the CMake in SDKs. It adds a toolchain configuration script which supports subscripts for extensions, as for example Qt5. (From OE-Core rev: 4143f3b0ce0d0c52f5b0babc1bb16ac0ac9610eb) Signed-off-by: Otavio Salvador <otavio@ossystems.com.br> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* poky-lsb: Set LTSI as base kernel for LSBSaul Wold2014-10-241-1/+2
| | | | | | | | | | | | By doing this we will enable the LTSI kernel (3.10 at this time) for the LSB based images. [YOCTO #6853] (From meta-yocto rev: 4f828e2160942cb05c93fa6f48a5a4b590940497) Signed-off-by: Saul Wold <sgw@linux.intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* poky.conf: add Debian 7.7 to SANITY_TESTED_DISTROSRoss Burton2014-10-241-0/+1
| | | | | | | (From meta-yocto rev: bf36e7598d1718851b2d49fe77b4a46b4da3071a) Signed-off-by: Ross Burton <ross.burton@intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* local.conf.sample.extended: update for RPM_PREFER_ELF_ARCHRobert Yang2014-10-241-3/+3
| | | | | | | | | | | | Updated as the rpm upstream suggested: - RPM_PREFER_COLOR -> RPM_PREFER_ELF_ARCH - 3 -> 4 (From meta-yocto rev: 4bc3b88bbf626e412b5e3892d0b6fbe641e1cb1a) 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>
* kernel-yocto: fix branch validation for AUTOREV, non machine_meta kernelsBruce Ashfield2014-10-241-6/+8
| | | | | | | | | | | | | | | | | The simplication of do_validate_branches missed a case where a custom kernel can supply SRCREV="${AUTOREV}", and not use SRCREV_machine at all. In this case, we will incorrectly try and test the tree for a non-existent commit, and break the build. By simplying the condition of the check to look for an empty SRCREV_machine, we can skip manipulating the tree and testing for a SRCREV. (From OE-Core rev: 212a4bd9b086365c022842a2ac6a2a25bd486002) Signed-off-by: Bruce Ashfield <bruce.ashfield@windriver.com> Signed-off-by: Ross Burton <ross.burton@intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* linux-yocto/3.17: v3.17 release and configBruce Ashfield2014-10-242-12/+12
| | | | | | | | | | | | | | | | | Updating the SRCREVs to incoroprate the full 3.17 release, and also updating the meta data to match the v3.17 content: 9ba007f8d0ab meta: bump kver to v3.17-final 5c6c5fe9b0bf config: remove CONFIG_HOTPLUG 0ceecad5f15a qemu: explicitly include usb configuration fragments f6c78ada8655 gfx: convert CONFIG_TABLET_USB_WACOM to CONFIG_HID_USB_WACOM cd1dbedfa3c9 x86: Support 32 bit binaries (From OE-Core rev: 18de1328dc99b851742468a3f366e3acdcce48d4) Signed-off-by: Bruce Ashfield <bruce.ashfield@windriver.com> Signed-off-by: Ross Burton <ross.burton@intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* linux-yocto/3.10: 8250/8250_dw: fix compile failure due to stable/Yocto conflictBruce Ashfield2014-10-243-10/+10
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | Updating the SRCREVs for the following fix: 8250/8250_dw: fix compile failure due to stable/Yocto conflict As of merge 60a9d9fc565e4503dbb8705803e83d906afc4ad2, "Merge tag 'v3.10.48' into standard/base" the 8250_dw.c fails to compile due to an undeclared variable. This happens because stable brought in: ------------------------- commit 6d5e79331417886196cb3a733bdb6645ba85bc42 Author: Tim Kryger <tim.kryger@linaro.org> Date: Tue Oct 1 10:18:08 2013 -0700 serial: 8250_dw: Improve unwritable LCR workaround commit c49436b657d0a56a6ad90d14a7c3041add7cf64d upstream. [...] [wangnan: backport to 3.10.43: - adjust context - remove unneeded local var] Signed-off-by: Wang Nan <wangnan0@huawei.com> Signed-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org> ------------------------ ...which deletes the p->private_data declaration since it became unused at that point, however in Yocto, we also have this: ----------------------- commit 0e02b050c3cafbcbf9952125089a27e02d6ecea9 Author: David Daney <david.daney@cavium.com> Date: Wed Jun 19 20:37:27 2013 +0000 tty/8250_dw: Add support for OCTEON UARTS. [...] Signed-off-by: Ralf Baechle <ralf@linux-mips.org> (cherry picked from commit d5f1af7ece96cf52e0b110c72210ac15c2f65438) Signed-off-by: Darren Hart <dvhart@linux.intel.com> ----------------------- ...which _adds_ another user of the p->private_data. Here we restore the declaration in order that 8250_dw compiles. Signed-off-by: Ong Boon Leong <boon.leong.ong@intel.com> [PG: add root cause info to commit log.] Signed-off-by: Paul Gortmaker <paul.gortmaker@windriver.com> Signed-off-by: Bruce Ashfield <bruce.ashfield@windriver.com> (From OE-Core rev: 4b4d1f38ea54ef8545e726ac9e181da08a2bad05) Signed-off-by: Bruce Ashfield <bruce.ashfield@windriver.com> Signed-off-by: Ross Burton <ross.burton@intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* unifdef: remove fork, package upstreamRoss Burton2014-10-243-1026/+15
| | | | | | | | | | Instead of building specifiaclly for native a static fork of unifdef from 2007, simply package the latest tarball. (From OE-Core rev: f642a9753b33c2f35d502b6721601fc690f674ec) Signed-off-by: Ross Burton <ross.burton@intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* native.bbclass: use BUILD_* variablesRoss Burton2014-10-242-11/+12
| | | | | | | | | | | | | | Instead of replicating the logic for the host compiler naming from bitbake.conf, use the BUILD_* variables directly. Also change BUILD_CPP to use gcc -E (which native.bbclass previously used), as some recipes (e.g. grub-efi) use ${CPP} with multiple input files, which gcc -E can handle but cpp can't. (From OE-Core rev: 9237d18964ff0bf76f5c37fca21ab3974d81d0d2) Signed-off-by: Ross Burton <ross.burton@intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* rpm: realpath is required before expanding _dbpath in chrootMing Liu2014-10-243-0/+26
| | | | | | | | | | | | | | | A regression is introduced by commit 66573093: [ rpm: Fix rpm relocation macro usage ] _usr turned out to be a relative path to support dyanmic config after that, but it's being used somewhere as a indicator to locate substrings, so we must get the real path of it in advance. (From OE-Core rev: 1247955a907f51aac7efd305d26856e263c11a65) Signed-off-by: Ming Liu <ming.liu@windriver.com> Signed-off-by: Ross Burton <ross.burton@intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* kernel.bbclass: Create modules directory even if there is no modules installedHe Zhe2014-10-241-0/+1
| | | | | | | | | | | | | | | During kernel_do_install it needs to make symbol link at ${D}/lib/modules/${KERNEL_VERSION}/build, but there will not be ${D}/lib/modules/${KERNEL_VERSION} if there is no modules installed for current image, which will result in a build failure. Add "mkdir -p ${D}/lib/modules/${KERNEL_VERSION}" here to avoid this failure and the need of similar changes in other scripts that also expect it to exist. (From OE-Core rev: f2f72f8ff623d24fffbb1b0ad40bc08f05ff31dd) Signed-off-by: He Zhe <zhe.he@windriver.com> Signed-off-by: Ross Burton <ross.burton@intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* libxml2: fix CVE-2014-3660Joe MacDonald2014-10-242-0/+148
| | | | | | | | | | | | | | | | | | It was discovered that the patch for CVE-2014-0191 for libxml2 is incomplete. It is still possible to have libxml2 incorrectly perform entity substituton even when the application using libxml2 explicitly disables the feature. This can allow a remote denial-of-service attack on systems with libxml2 prior to 2.9.2. References: http://www.openwall.com/lists/oss-security/2014/10/17/7 https://www.ncsc.nl/actueel/nieuwsberichten/kwetsbaarheid-ontdekt-in-libxml2.html (From OE-Core rev: 643597a5c432b2e02033d0cefa3ba4da980d078f) Signed-off-by: Joe MacDonald <joe_macdonald@mentor.com> Signed-off-by: Ross Burton <ross.burton@intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* nfs-utils: fix start-statdRoy.Li2014-10-242-0/+31
| | | | | | | | | | | | 1. add /bin to PATH of start-statd, otherwise systemctl can not be found. 2. drop error when systemd fails to start statd.service; since if it failed, rpc.statd will be called directly. (From OE-Core rev: 048130996300e1762bc6d714ba09aac5a326843d) Signed-off-by: Roy.Li <rongqing.li@windriver.com> Signed-off-by: Ross Burton <ross.burton@intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* cross-localedef-native: provide SRCREV_FORMATJoe Slater2014-10-241-0/+4
| | | | | | | | | | | Add SRCREV_FORMAT to provide a composite version number for get_srcrev() in fetch2 code. (From OE-Core rev: 87cda76a2f004813420d7730c4f2f74839d3c2df) Signed-off-by: Joe Slater <jslater@windriver.com> Signed-off-by: Ross Burton <ross.burton@intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* archiver: fix truncation of src_revJoe Slater2014-10-241-2/+2
| | | | | | | | | | | | | In trying to eliminate AUTOINC+ from revision strings, we accidently truncated the strings to almost guarantee information from SRCREV_FORMAT, when supplied, would be lost. So, we now only delete any AUTOINC+'s from the string. (From OE-Core rev: 83c6930cdfac5a7759c4786172a5c70226e6adc4) Signed-off-by: Joe Slater <jslater@windriver.com> Signed-off-by: Ross Burton <ross.burton@intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* libaio: fix for mips64Jianchuan Wang2014-10-242-0/+43
| | | | | | | | | | | | Add mips64 support in the libaio.h - add macro PADDED/PADDEDptr/PADDEDul in the mips64 for structure iocb to be matched userland with kernel (From OE-Core rev: ce0a999efe5c9bfd4780bd2b7c24e99f580474c0) Signed-off-by: Jianchuan Wang <jianchuan.wang@windriver.com> Signed-off-by: Ross Burton <ross.burton@intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* systemd: fix libidn floating dependencyChen Qi2014-10-241-0/+1
| | | | | | | | | | WARNING: QA Issue: systemd rdepends on libidn, but it isn't a build dependency? [build-deps] (From OE-Core rev: 83be6e94f35b44baa6c363c9518f85e7670246f3) Signed-off-by: Chen Qi <Qi.Chen@windriver.com> Signed-off-by: Ross Burton <ross.burton@intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* grub: add cmdpath to grub configuration fileArindam Nath2014-10-241-1/+1
| | | | | | | | | | | | | | | | | | | | | An issue was found where when yocto is installed to a hard disk from a live USB key, no matter what boot order was selected in the BIOS menu, the grub menu of the USB key would always show up. The issue was narrowed down to the way grub configuration file gets embedded into the standalone bootx64.efi image. The commit prepends ($cmdpath) to the search path for grub.cfg, thus making sure the UEFI environment itself sets this to the correct device path. This in-turn lets the grub.cfg of the boot device to be loaded. (From OE-Core rev: 5ce73b6055ac5a47906e2e661bc5163604f5cec9) Signed-off-by: Arindam Nath <arindam.nath@amd.com> Reviewed-by: Drew Moseley <drew_moseley@mentor.com> Tested-by: Ravikiran Polepalli <Ravikiran_Polepalli@mentor.com> Signed-off-by: Ross Burton <ross.burton@intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* spdx.bbclass: improved stability, fixed SPDX compliance issues. Changes are ↵Tobias Olausson2014-10-242-52/+126
| | | | | | | | | | | | | | | | | | | | reflected in licenses.conf. The previous version could crash on dead links in the rootfs, or if the manifest directory did not exist. The generated files were also not compliant with the SPDX specification, for example file entries did not always start with the FileName tag, time stamps were incorrectly formatted etc. Stability issues are addressed by added checks, originally written by Johan Thelin <johan.thelin@pelagicore.com>, who never upstreamed them. I've also added an option for getting full SPDX output from FOSSology, i.e. not only for all files, but for the package as well, including license references. License refs are required in order to process the output by SPDXTools. For that reason, this option defaults to true. (From OE-Core rev: 5d3a4f4f57e4d8581fd88a14324f94e93104a690) Signed-off-by: Tobias Olausson <tobias.olausson@pelagicore.com> Signed-off-by: Ross Burton <ross.burton@intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* default-versions.inc: match version of db and db-native while "AGPL-3.0" in ↵Hongxu Jia2014-10-241-0/+4
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | ${INCOMPATIBLE_LICENSE} The db 6.0.30's LICENSE is 'AGPL-3.0', and db 5.3.28 LICENSE is 'Sleepycat' While building rpm image with "AGPL-3.0" in ${INCOMPATIBLE_LICENSE}, db 6.0.30 and db-native 5.3.28 were built, the different versions caused the rpm doesn't work on target. ... root@qemux86-64:~# rpm -qa |rpmdb: BDB2531 Unacceptable log file /var/lib/rpm/./log/log.0000000001: unsupported log version 21 |rpmdb: BDB2527 Invalid log file: log.0000000001: Invalid argument |rpmdb: BDB0061 PANIC: Invalid argument |==> rpmdbe_event_notify(0x623f40, PANIC(0), 0x7fffee0fbc0c) app_private (nil) |rpmdb: BDB1546 unable to join the environment |error: db_init:tmp/work/core2-64-poky-linux/rpm/5.4.14-r0/rpm-5.4.14/ rpmdb/db3.c:1144: dbenv->open(-30973): BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery ... [YOCTO #6858] (From OE-Core rev: e5a40391dfa12c44f31bdb7550df1275edda3864) Signed-off-by: Hongxu Jia <hongxu.jia@windriver.com> Signed-off-by: Ross Burton <ross.burton@intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* libtool: Extend fix-final-rpath.patchRandy Witt2014-10-241-2/+14
| | | | | | | | | | | | | | | When building upower from meta-oe, the following QA error occurred: ERROR: QA Issue: package upower contains bad RPATH It appears to have been caused by one of the cases fix-final-rpath.patch is meant to address but missed. So this change fixes the additional case that was causing upower to have the QA error. (From OE-Core rev: d2b2bb7cedb678c9f67ef1d9170fc427d9beee1e) 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>
* liburcu: revert ARM GCC blacklist commitJonathan Liu2014-10-242-0/+48
| | | | | | | | | | | | | | This fixes the following error when building liburcu: "Your gcc version produces clobbered frame accesses" OE-Core is using a patched GCC 4.8.2 which is able to compile liburcu properly. (From OE-Core rev: 83bb2c2b1f68abfc4d882b2aec3b5468372b1436) Signed-off-by: Jonathan Liu <net147@gmail.com> Signed-off-by: Ross Burton <ross.burton@intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* nfs-utils: fix a Gcc undefined behaviorRoy Li2014-10-242-0/+39
| | | | | | | | | | | | | | Calling strncpy with NULL second argument, even when the size is 0, is undefined behavior, which leads to GCC to drop the check old variable with NULL in following code. https://bugzilla.yoctoproject.org/show_bug.cgi?id=6743 (From OE-Core rev: af56e7559d31cb9cb84b85a7dedd8e12cf1f06cd) Signed-off-by: Roy Li <rongqing.li@windriver.com> Signed-off-by: Ross Burton <ross.burton@intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* python-smartpm: Add checking for "rpm-ignoresize" optionChong Lu2014-10-243-0/+39
| | | | | | | | | | | | | | | | | The do_rootfs takes a very long time when build host has mounted many NFS devices. syscall lstat() was being called on every filesystem mounted on the build host during building. The reason for the lstat() is that rpm is verifying that enough free disk space is available to do the install. However, since the install is into the target rootfs it should not matter how much free space there is in the host mounts. Add checking for "rpm-ignoresize", by it, smart can make whether RPM skip checking for diskspace when install a rpm package. (From OE-Core rev: fc0668a019eca422540ceab3efcd2b2a27dd79e0) Signed-off-by: Chong Lu <Chong.Lu@windriver.com> Signed-off-by: Ross Burton <ross.burton@intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* systemd: Use ${ROOT_HOME} instead of /rootDan McGregor2014-10-242-1/+182
| | | | | | | | | | | | | systemd avoids using nss lookups for the root user, so naturally it assumes that root's home directory is /root. In OE that's not the case, and it can lead to long delays when shutting down due to user shutdown unit failures. (From OE-Core rev: e1efc61979b329c651c15acff1afeba2987397b5) Signed-off-by: Dan McGregor <dan.mcgregor@usask.ca> Signed-off-by: Ross Burton <ross.burton@intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
OpenPOWER on IntegriCloud