summaryrefslogtreecommitdiffstats
Commit message (Collapse)AuthorAgeFilesLines
* binutils: Use tip of 2.26 branchKhem Raj2016-02-1615-176/+173
| | | | | | | | | | | | | | | | | | | | | | Until 2.26.1 is released there are few fixes which are needed especially when using -fpie, here are changes that are part of this version bump H.J. Lu (7): Add a testcase for PR ld/18591 Store estimated distances in compressed_size Remove duplicated marker for 2.26 in gas/NEWS Add -mrelax-relocations= to x86 assembler Mask off the least significant bit in GOT offset Enable -Bsymbolic and -Bsymbolic-functions to PIE Fix a typo in objcopy manual John David Anglin (1): Fix /usr/bin/ld: final link failed: File truncated error on hppa (From OE-Core rev: 3685a1246110d84bffffa6d03a3c2ec0417cb4a3) Signed-off-by: Khem Raj <raj.khem@gmail.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* buildhistory.bbclass: remove out-dated information on requestPatrick Ohly2016-02-151-9/+51
| | | | | | | | | | | | | | | | | | | | | | | | | | | | buildhistory.bbclass by design is incremental: each build adds or updates information. Information is never removed. Sometimes it can be useful to reduce the information only to those recipes that were build during a specific bitbake invocation, for example when the invocation does a full world build. This is now possible by setting BUILDHISTORY_RESET as explained in the modified class. The comment on the variable also mentions the caveats associated with using this mode. In this mode, buildhistory.bbclass first moves all existing information into a temporary directory called "old" inside the build history directory. There the information is used for the "version going backwards" QA check. Then when the build is complete and before (potentially) committing to git, the temporary directory gets deleted. Because information that has not changed during the build will be reconstructed during full world rebuilds, a git log will then only show real updates, additions and removals. (From OE-Core rev: 51f4eb5bfcd25f7160e50314f433cad126aa3e9a) Signed-off-by: Patrick Ohly <patrick.ohly@intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* Remove obsolete references to exmapRandy MacLeod2016-02-151-1/+1
| | | | | | | | | | | | Exmap was a useful tool but it appears to be unsupported. Remove it from the sample local.conf and remove the commented lines from the profile tools packagegroup. (From meta-yocto rev: 4c71076dc70fc9fd2c3c6183fe6e5c1724cf6682) Signed-off-by: Randy MacLeod <Randy.MacLeod@windriver.com> Signed-off-by: Ross Burton <ross.burton@intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* bitbake: knotty: Set exit failure code on runQueueTaskFailed eventsRichard Purdie2016-02-151-0/+1
| | | | | | | | | | | If the worker segfaults, we may never see a TaskFailed event from it, only a runQueueTaskFailed event. In this case, return_value isn't getting set leading to an incorrect exit code from bitbake. Fix by setting return_value in both places. (Bitbake rev: e5dd50e0d95d532fe31dde61f8c6b1a7a72321e9) Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* bitbake: taskdata: Fix traceback issue with missing providerRichard Purdie2016-02-151-1/+3
| | | | | | | | | If there is a missing provider and we're using "-k" mode alongside "-w", we could get a traceback since there was no provider. Add tests to avoid this. (Bitbake rev: 90a4805e4e770a433b4394ea99792731e9a4b546) Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* bitbake: cooker: Improve cache handlingRichard Purdie2016-02-151-4/+10
| | | | | | | | | | | | | | | | | | | | | | We're seeing issues where the self test, which uses tinfoil doesn't notice the changed contents of include files. The issue is cached_statements in the parser being reused when the files have changed. Whilst looking at this, I realised there were some other issues: * We need to also invalidate the mtime cache when cooker restarts * We should pass full filenames to the file invalidation code * We should process cached_statements as part of inotify invalidation With these fixes, the caching is more reliable for memory resident bitbake too. It does raise some questions about cache validation and lifecycles and indicates bitbake does need more work in the area, preferably with the removal of the globals. This at least highlights and works around some of the current issues. (Bitbake rev: 3f507ff8bc467fba936cf3f31bb8ea8e02f168e8) Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* poky: Disable static libs by defaultRichard Purdie2016-02-151-0/+1
| | | | | | | | | | | | | | | | | Static libraries are old technology. We've left them around since in previous tests, they only added around 5% to the overall build time. With new and interesting uses of OE, they're becoming more problematic. For example, sstate becomes much larger with static libs enabled which increases the size of eSDK and increases the time taken for sstate operations. Since the static libs contain all the debugging symbols, they're also pretty huge. Therefore use the common include which enables this from OE-Core. (From meta-yocto rev: a67da388fd9afd8c4b6084b972349da05b9a433e) Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* bitbake.conf: Remove unhelpful default value for EXTRA_OEMAKEMike Crowe2016-02-151-1/+1
| | | | | | | | | | | | | | | Setting EXTRA_OEMAKE to "-e MAKEFLAGS=" by default is a historical accident and many classes (e.g. autotools.bbclass, module.bbclass) and recipes have to override this default in order to work with sensible build systems. Now that openssl and pciutils have been fixed to set EXTRA_OEMAKE explicitly it is possible to set EXTRA_OEMAKE = "". (From OE-Core rev: aeb653861a0ec39ea7a014c0622980edcbf653fa) Signed-off-by: Mike Crowe <mac@mcrowe.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* apmd: fix build with static libraries disabledRoss Burton2016-02-152-0/+54
| | | | | | | | | | | | apmd was using foo.o in Makefile dependencies but if libtool is being used then those are the statically linked intermediate files. When static libraries are globally disabled they won't be generated by libtool-cross so the build fails. Instead, use the libtool intermediate wrapper .lo files so the build succeeds. (From OE-Core rev: a3dbd98970683c410edee5e15e5fe72643953adf) Signed-off-by: Ross Burton <ross.burton@intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* oeqa: Update to handle domain specific references in build logsRichard Purdie2016-02-153-8/+23
| | | | | | | | | With the addition of the task name to recipe output, the sanity tests need updates where they are looking for specific messages. (From OE-Core rev: 0f2ef4304e6a6f18b4ed13f59000b4a1daa35f6b) Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* libpng12: Handle no static libsRichard Purdie2016-02-151-1/+1
| | | | | | (From OE-Core rev: d8e2dc4c26b6ad19421be9b365c24f71262992a9) Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* ed_0.5: Handle --disable-static optionRichard Purdie2016-02-151-4/+3
| | | | | | | | Also clean up use of immediate expansion as there are cleaner mechanisms now. (From OE-Core rev: 8d85e73b7279591190272536add909827144c623) Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* conf/distro/include: Add no-static-libs.incRichard Purdie2016-02-151-0/+30
| | | | | | | | | | | | | | | | | | | | | | | | | | | | Static libraries are old technology. We've left them around since in previous tests, they only added around 5% to the overall build time. With new and interesting uses of OE, they're becoming more problematic. For example, sstate becomes much larger with static libs enabled which increases the size of eSDK and increases the time taken for sstate operations. Since the static libs contain all the debugging symbols, they're also pretty huge. This patch adds a common include file which allows the user or distro to disable the static libraries in the majority of cases. There are some libs where we do need the static lib, a good example being pseudo-native which uses sqlite3-native static libs. These are left enabled by the include file, as are recipes where --disable-static doesn't work, or isn't supported. This list can likely be reduced over time as individual corner cases are addressed. Maintaining this list in a common location is more desireable than everyone doing it themselves. Poky will switch to using this, OE-Core will need to discuss that as its default. (From OE-Core rev: 773c9e18071d71454473dd81aff911104a2e9bc6) Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* classes/buildhistory: fix for python function parsing changePaul Eggleton2016-02-151-3/+3
| | | | | | | | | | | Variable expressions are no longer expanded in python functions as of BitBake commit 8bf33a8e92c0e188fa392030025756196c96fcbb, so we've now got to do this explicitly here. (From OE-Core rev: 60fd4ff61a4ad240a89d48553002901c10e93178) Signed-off-by: Paul Eggleton <paul.eggleton@linux.intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* valgrind: Fix build with muslKhem Raj2016-02-152-2/+73
| | | | | | | (From OE-Core rev: 0ec5ac9453e037f3999f4fa57750f87270bb78d9) Signed-off-by: Khem Raj <raj.khem@gmail.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* rpm: Fix build with muslKhem Raj2016-02-152-1/+166
| | | | | | | (From OE-Core rev: d0fc6e8593b951163d48665f41d6ef1eb74b8926) Signed-off-by: Khem Raj <raj.khem@gmail.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* gstreamer1.0-meta-base: Mark as machine specific due to COMBINED_FEATURESRichard Purdie2016-02-151-0/+3
| | | | | | | | | | | | | | http://git.openembedded.org/openembedded-core/commit/?id=948165dce7475b815a344fd3c3d58165e6865d48 makes gstreamer1.0-plugins-base-alsa depend on COMBINED_FEATURES. This is an allarch recipe so this only works if all your machines have the same MACHINE_FEATURES. The recipe therefore needs to become machine specific. (From OE-Core rev: 442095c3b6014f795833c36f08249eacef6fbcf3) Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* gdb-cross-canadian: Add missing virtual/* DEPENDSRichard Purdie2016-02-151-1/+3
| | | | | | | | | cross-canadian does INHIBIT_DEFAULT_DEPS so we need to add the various virtual/* toolchain pieces we rely on manually. (From OE-Core rev: 737ce94aeb7e26a41cf286097904c1234c42b477) Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* e2fsprogs: Update to upstream version of a patchRichard Purdie2016-02-151-47/+200
| | | | | | | | Switch to the upstream version of the xattr patch. (From OE-Core rev: 631217cc3cb15a7ec4f3cdf6e8d1ff67de2a72b3) Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* gdb: Rationalise PACKAGECONFIGRichard Purdie2016-02-152-4/+2
| | | | | | | | | Having two separate PACKAGECONFIG defaults and settings in two separate files is confusing. Move all to the common inc file. (From OE-Core rev: 9e6743e01467ffb08d62b7415fa7af79c09939e0) Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* insane: Add --disable-static to UNKNOWN_CONFIGURE_WHITELISTRichard Purdie2016-02-151-1/+1
| | | | | | | | | | | With the addition of a common class passing in this option, add it to the list of standard "unknown" configure options which are known about. Its not interesting/productive to go and update every recipe to handle this flag. (From OE-Core rev: f879f452dc69989aa227b8dc60b7cb0354203575) Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* linux-yocto: Work around PAT issue on qemux86Richard Purdie2016-02-153-1/+103
| | | | | | | | | | | | We have an issue with PAT handling on older processes with limited PAT bits, see the patch description for the full problem. This replaces the runqemu workaround with a kernel patch until we can get the kernel trees sorted out and discuss a proper fix with upstream. It should be safe everywhere so is applied unconditionally. (From OE-Core rev: e00f0794a535c8e68ae1c87c8b01dd65645d570b) Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* libgcrypt: update 1.6.4 -> 1.6.5Andre McCurdy2016-02-153-6/+4
| | | | | | | | | | | | | | | | Noteworthy changes in version 1.6.5 (2016-02-09) [C20/A0/R5] ------------------------------------------------ * Mitigate side-channel attack on ECDH with Weierstrass curves [CVE-2015-7511]. See http://www.cs.tau.ac.IL/~tromer/ecdh/ for details. * Fix build problem on Solaris. (From OE-Core rev: 1146a4bb3af167c75bdea3e75e6f1e80b45cc721) Signed-off-by: Andre McCurdy <armccurdy@gmail.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* musl: Upgrade to tip of treeAndre McCurdy2016-02-151-1/+1
| | | | | | | | | | | | | | | | | | | Includes misc minor bugs fixes: 0ed932f do not define static_assert macro for pre-C11 compilers 692b16d add declarations for utmpname/utmpxname to appropriate headers 500c688 fix return value for fread/fwrite when size argument is 0 416d1c7 fix line-buffered flush omission for odd usage of putc-family functions 5a6e8d0 fix failed write reporting by fwrite in line-buffered mode 869a9df remove workaround for broken mips assemblers The addition of utmpname/utmpxname prototypes fixes a change introduced in the previous git snapshot version which broke lxc. (From OE-Core rev: 837c092ba1a2ff95733707a01550152feea5b1aa) Signed-off-by: Andre McCurdy <armccurdy@gmail.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* oe-selftest: don't use specific tasksEd Bartosh2016-02-151-1/+1
| | | | | | | | | | | | | | | | | Image should be build usual way, i.e. using bitbake <image>. Specifying do_mage_complete and do_rootfs_wicenv tasks should not be needed anymore as those tasks should be run by bitbake for every image. Removed specifying do_mage_complete and do_rootfs_wicenv tasks from bitbake calls. (From OE-Core rev: d8d7bd1b41eb846f18378a2581ff172cb2cc52b8) (From OE-Core rev: 00cd291605ff5f001979b350d95670e33012fdc9) Signed-off-by: Ed Bartosh <ed.bartosh@linux.intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* oe-selftest: pylinted wic testsEd Bartosh2016-02-151-9/+9
| | | | | | | | | | | | | | | | | | Fixed the following pylint warnings: C: 45, 0: Line too long (91/80) (line-too-long) C:105, 0: Wrong continued indentation. ignore_status=True).status) ^ | (bad-continuation) W: 83, 8: Redefining built-in 'vars' (redefined-builtin) W:175, 8: Redefining built-in 'vars' (redefined-builtin) W: 27, 0: Unused import sys (unused-import) (From OE-Core rev: ecb5320e766d0fa031c269d6d9b2a24c81c7aa7e) (From OE-Core rev: c47af4a772883c86559673ba9b9f774f0ff0d54c) Signed-off-by: Ed Bartosh <ed.bartosh@linux.intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* wic-image-minimal: use uuid for root partitionEd Bartosh2016-02-152-3/+3
| | | | | | | | | | | | | | | | | Used --uuid option to generate PARTUUID for root partion and gpt partition type. As this image is used in runtime testing under qemu it makes sense to ensure that this way of specifying root partition works. Added dependency to gptfdisk-native to wic-image-minimal recipe to be able to create gpt partition table. (From OE-Core rev: ba82867bfda54e86e1de5dc4a6ad7246254cf5c3) (From OE-Core rev: 767d814b2e125e20839f204e17512ebe2aec8b95) Signed-off-by: Ed Bartosh <ed.bartosh@linux.intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* wic: fix processing of --use-uuidEd Bartosh2016-02-151-0/+3
| | | | | | | | | | | | | | | Processing of this option was lost during recent change of wks parsting. It was discovered during the work on booting wic images under qemu. Now, when -use-uuid is fixed it's possible to specify root partition by partition uuid. This will be done in the following commit. (From OE-Core rev: b4882e0b84d7fd4c85ee95386e94722485eafc2b) (From OE-Core rev: 73e9e3f150bf2de9b27c2ccc73e3dee334ee73fe) Signed-off-by: Ed Bartosh <ed.bartosh@linux.intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* oe-selftest: add new wic testcaseEd Bartosh2016-02-151-1/+11
| | | | | | | | | | | | | | Added test_qemu testcase to boot wic-image-minimal and test that 2 partitions mentioned in .wks are mounted. [YOCTO #8499] (From OE-Core rev: 6fb015d0847fe7d259d654d4a99bf4c328f810ab) (From OE-Core rev: be360c24649391235fd9547a8f2c1251b12e9c81) Signed-off-by: Ed Bartosh <ed.bartosh@linux.intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* wic-image-minimal: update .wks to boot by qemuEd Bartosh2016-02-151-5/+5
| | | | | | | | | | | | | | | With below list of changes wic-image-minimal can be boot by qemu: - Changed device name sda -> vda. - Added root=/dev/vda2 to the kernel command line. - Changed mount point for core partition to /mnt to have it mounted on boot time. (From OE-Core rev: f085274711f561f97a2c89f40bb0e89094973054) (From OE-Core rev: 4c8d44a1be344c603bcdcb1911f609ac67e6be66) Signed-off-by: Ed Bartosh <ed.bartosh@linux.intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* wic-image-minimal: change IMAGE_FSTYPESEd Bartosh2016-02-152-2/+2
| | | | | | | | | | | | | | | | Replaced wic.bz2 -> wic in the recipe. Replaced wic.bz2 -> wic in oe-selftest test case. wic-image-minimal is going to be booted in qemu and tested. As runqemu doesn't support compressed images this recipe needs to produce raw wic image. (From OE-Core rev: 3ce91db94f4b921566dce0dc6f91a422009be06b) (From OE-Core rev: 69d8dfe4fc1fec440e33b1bb6cef62e20f1f5c28) Signed-off-by: Ed Bartosh <ed.bartosh@linux.intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* oeqa/targetcontrol: support wic image typeEd Bartosh2016-02-151-1/+1
| | | | | | | | | | | | | | | | Added 'wic' to the list image types supported by targetcontrol. This is a preparation for booting and testing wic images with oe-selftest. [YOCTO #8498] (From OE-Core rev: 7dda053fbd1ea1354b7720cfa691470ba88ef5b9) (From OE-Core rev: 4b84328d3cd0d87ad146f034b58f68a5158313d7) Signed-off-by: Ed Bartosh <ed.bartosh@linux.intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* oeqa/targetcontrol: make ssh control optionalEd Bartosh2016-02-152-10/+12
| | | | | | | | | | | | | | Added new parameter 'ssh' to targetcontrol 'start' method to be able to test images without running ssh server. [YOCTO #8498] (From OE-Core rev: 1c3c66aadd43092bc19242b0651ee810cc31fe7c) (From OE-Core rev: 67ccf7413b2ac9f516dbdaa6a39d4cec38a6c94d) Signed-off-by: Ed Bartosh <ed.bartosh@linux.intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* qemurunner: add parameter to method 'start'Ed Bartosh2016-02-151-22/+23
| | | | | | | | | | | | | | | | | | | | | | | QemuRunner requires pair of ip addresses provided through kernel commandline for method 'start' to work. These ip addresses are used to connect to the image using ssh and run tests there. However, this functionality should not be mandatory as testing doesn't always require ssh connection. Some tests can be run using serial console. Added new parameter 'get_ip' to QemuRunner.start to make it possible to skip getting pair of ip addresses from kernel command line. This should allow oe-selftest to test images without modifying kernel command line. [YOCTO #8498] (From OE-Core rev: 3f8b734ebb81d035849288091bb0b97b9c4fba34) (From OE-Core rev: 4c90daaeb946f1adf58b2f71f1af8eb7f5906474) Signed-off-by: Ed Bartosh <ed.bartosh@linux.intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* oe-selftest: remove unused parameterEd Bartosh2016-02-153-5/+5
| | | | | | | | | | | Removed unused parameter 'test' from runqemu function. (From OE-Core rev: c688b3bcbb57099fa72a9728bc708b109802f7fc) (From OE-Core rev: a7af1eb28fab515180c0fa01a003ac7b2ce0cff4) Signed-off-by: Ed Bartosh <ed.bartosh@linux.intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* runqemu: support path/to/<image>-<machine>.wicEd Bartosh2016-02-151-4/+6
| | | | | | | | | | | | | | Supported providing wic image path to runqemu: runquemu path/to/<image>-<machine>.wic [YOCTO #8691] (From OE-Core rev: 58a3bfb1e4b493200820cdf0bf3fc79e31e792de) (From OE-Core rev: e6150971ea4eea49b802a12aea5ab733e894c92d) Signed-off-by: Ed Bartosh <ed.bartosh@linux.intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* runqemu: don't set KERNEL for wic imagesEd Bartosh2016-02-152-2/+2
| | | | | | | | | | | | | | | | Wic images should be boot as is, without pointing qemu to the kernel binary. Current code doesn't use kernel, but sets KERNEL variable and shows kernel path in the console output. This can confuse users. Changed runqemu and runqemu-internal code to avoid setting KERNEL variable and show kernel path. (From OE-Core rev: 474caa7ed5ff05caa5d49d270b283882fa616ed1) (From OE-Core rev: 35e776e00cce25f2c9c45500612fb66022ec4739) Signed-off-by: Ed Bartosh <ed.bartosh@linux.intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* runqemu: add support for wic imagesEd Bartosh2016-02-152-9/+10
| | | | | | | | | | | | | | Quemu should be able to run wic images this way: runqemu <machine> <image recipe> wic Tested with 'runqemu qemux86-64 wic-image-minimal wic' (From OE-Core rev: 8716be799949cb8bde7fa49cbea61312a3a93bb7) (From OE-Core rev: dd42931bf99b8bbd4ad452b3941d957f41b81796) Signed-off-by: Ed Bartosh <ed.bartosh@linux.intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* scripts/sstate-cache-management.sh: Change wordingJan Sarenik2016-02-151-2/+2
| | | | | | | | | Use "out of" rather than "from" in the output. (From OE-Core rev: c712529030c71b45bb8ae647c17319c2647aedff) Signed-off-by: Jan Sarenik <jajomojo@gmail.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* qemu.inc: Add rng-tools to qemu imagesSaul Wold2016-02-151-0/+2
| | | | | | | | | | | | | | This patch adds rng-tools to MACHINE_EXTRA_RRECOMMENDS so that can be used to provide the additional entropy to prevent hangs in getrandom() for qemu images [YOCTO #8681] [YOCTO #8816] (From OE-Core rev: cb512c0c189f5a1196da233042113a708243daa0) Signed-off-by: Saul Wold <sgw@linux.intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* rng-tools: Import recipe from meta-openembeddedSaul Wold2016-02-153-0/+90
| | | | | | | | | | | | | | | | | Adding this recipe to oe-core will allow it to be used by qemu to provide a way to generate additional entropy needed to fix hangs with getrandom(). Additional kernel config options have already been added to the default qemu kernel configs. [YOCTO #8681] [YOCOT #8816] (From OE-Core rev: 030bc0b2f9636f5cacef29c939b323569cd5673f) Signed-off-by: Saul Wold <sgw@linux.intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* lib/oe/terminal: set workdir for konsole terminalPascal Bach2016-02-141-1/+1
| | | | | | | | | | | | It seems that if the --workdir option is not set konsole does open in the users home directory. By setting --workdir . konsole opens in the recipes work directory. This is the same behavior as observed for other consoles. (Tested with Konsole 2.14.2 on Debian Jessie). (From OE-Core rev: bd06944249c3de3f629c013e14f446464441c4da) Signed-off-by: Pascal Bach <pascal.bach@siemens.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* mmc-utils: upgrade to latest git versionMaxin B. John2016-02-142-34/+5
| | | | | | | | | | | | Removed 0001-mmc.h-don-t-include-asm-generic-int-ll64.h.patch Instead of that patch, define __SANE_USERSPACE_TYPES__ to avoid compile errors due to conflicting types for '__u64' in MIPS64/PPC64 (From OE-Core rev: 819541253d63b14bb6a5fd4cafdd2b6fa16f4ca3) Signed-off-by: Maxin B. John <maxin.john@intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* ltp: Upgrade to 20160126 and fix build on muslKhem Raj2016-02-1437-410/+2705
| | | | | | | | | | | | | | pass -D__SANE_USERSPACE_TYPES__ to CFLAGS MIPS64/PPC64 uses long long for u64 in the kernel, but powerpc's asm/types.h prevents 64-bit userland from seeing this definition, instead defaulting to u64 == long in userspace. Define __SANE_USERSPACE_TYPES__ to get int-ll64.h included. (From OE-Core rev: d17984eda9635f98d4472019d4af83f661b4dfe7) Signed-off-by: Khem Raj <raj.khem@gmail.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* initscripts: start urandom after populate-volatilesJens Rehsack2016-02-141-1/+1
| | | | | | | | | | In case of read-only rootfs, populoate-volatiles might be used to create some links (or bind-mounts) required for having a writable /var/lib. (From OE-Core rev: 1f07dcfcecbd42f947b83c6f75d1a66186bcad68) Signed-off-by: Jens Rehsack <sno@netbsd.org> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* initscripts: populate-volatiles.sh: add mount-bind featureJens Rehsack2016-02-141-0/+10
| | | | | | | | | | | | | | | | Add ability to run "mount --bind" to populate-volatiles. Since several programs use realpath to determine several full qualified file names, there is no symlink to be resolved. So when speccing /run/lock - that's the location - not /var/run/lock because of the program is smarter than the operator/distributor. See https://github.com/rehsack/meta-jens/blob/jethro/recipes-core/initscripts/initscripts/volatiles for an example how to use the "b" feature. (From OE-Core rev: ab42fcaf1427a29c31ac2e93965e20849b1b1234) Signed-off-by: Jens Rehsack <sno@netbsd.org> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* libdrm: don't detect components that have been disabledRoss Burton2016-02-142-0/+60
| | | | | | | | | | | We pass --disable-cairo-tests but if cairo is in the sysroot it is detected and used, which causes problems in mass builds as cairo could be removed whilst libdrm is being built. (From OE-Core rev: 71882b061bad55f4ad62c7d235a4a629dd74dda8) Signed-off-by: Ross Burton <ross.burton@intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* buildhistory: Fix regex to handle versions without spacesRichard Purdie2016-02-141-1/+1
| | | | | | | | | | Its valid to have dependencies like XXX (=2.1) without spaces, as injected by debian.bbclass. The code was breaking these into separate components and destroying them so improve the regex to handle them. (From OE-Core rev: 613e96b06202f31870be411ca45b44237ae55b1c) Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* debian: Fix superfluous setting for RPROVIDESRichard Purdie2016-02-141-1/+1
| | | | | | | | | | | PKG_ can be set to something like ${MLPREFIX}<name> and the lack of expansion here means the case where MLPREFIX is empty leads to a bogus RPROVIDES. Use expansion of the variable to avoid this. (From OE-Core rev: 056339c32a9ff0735d39cae216663147cdbb275c) Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* autotools: Fix interaction with bitbake -bRichard Purdie2016-02-141-0/+11
| | | | | | | | | | | | | | | | If you run bitbake -b on something using autotools with dependencies on m4 files, it currently fails as the TASKDEPDATA is incomplete for bitbake -b and this means the relevant macros aren't found. Work around this by adding *all* m4 files for the -b case (and show a warning). [YOCTO #8890] (From OE-Core rev: 60207e0cf3a5bce9123d3631a10a9540c72a9034) Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
generated by cgit v1.2.3-54-g00ecf (git 2.39.0) at 2024-09-22 16:33:51 +0000