summaryrefslogtreecommitdiffstats
Commit message (Collapse)AuthorAgeFilesLines
...
* gcc: Upgrade to 6.2 RC1Khem Raj2016-08-1963-11/+12
| | | | | | | (From OE-Core rev: 41ce4b438795108025c79cd3eec067367d53623e) Signed-off-by: Khem Raj <raj.khem@gmail.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* libunwind: Fix build race conflict with gcc and muslRichard Purdie2016-08-192-0/+38
| | | | | | | | | | | | | | | | | | Building libunwind, then gcc-runtime causes build failures. This is hard to fix since gcc-runtime wants the internal gcc unwind.h header but libunwind wants to provide this. There are differences in include behaviour between gcc and glibc which are by design. This patch hacks around the issue by looking for a define used during gcc-runtime's build and skipping to the internal header in that case. The patch is only enabled on musl and is the best workaround I could come up with to unblock failing builds on our autobuilder. [YOCTO #10129] (From OE-Core rev: cd8b64b0a236b27e5383e2394de65b9bfd4b6677) Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* ref-manual: swabber: remove from documentationMaxin B. John2016-08-191-16/+0
| | | | | | | | | | Remove documentation as swabber was removed from oe-core with this commit: commit a7ddbea345c90646e6b9ddb89f768865caffdf07 (From yocto-docs rev: f3c462b2c6aa20de53c77e5d93cf397ae36cb2bb) Signed-off-by: Scott Rifenbark <srifenbark@gmail.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* ref-manual: Update SERIAL_CONSOLES_CHECK descriptionCalifornia Sullivan2016-08-191-1/+1
| | | | | | | | | | | | | | | | The previous description was not accurate. Looking at the code, SERIAL_CONSOLES_CHECK does not act like SERIAL_CONSOLES, as it will not add consoles to enable but only check and disable consoles defined by SERIAL_CONSOLES. Also, the previous patch adds aliasing functionality that needed to be documented. I (Scott Rifenbark) did a bit of word-smithing here from the original patch. (From yocto-docs rev: 55d07048e831f0dbc955b74e029fe26ed276675b) Signed-off-by: Scott Rifenbark <srifenbark@gmail.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* ref-manual: change SYSLINUX_ROOT to ROOT_VM for DISK_SIGNATURE variableJonathan Liu2016-08-191-3/+3
| | | | | | | | | The SYSLINUX_ROOT variable was renamed to ROOT_VM in krogoth. (From yocto-docs rev: c4bbe8bc4967dd631b939f6806d65e2862df3424) Signed-off-by: Scott Rifenbark <srifenbark@gmail.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* ref-manual: Applied review edits to "Viewing Dependencies"Scott Rifenbark2016-08-181-26/+40
| | | | | | | | | | | | | Fixes [YOCTO #10131] Fixed some small issues here and there. Also, provided a second itemized item in the note box turning it into a notes box. (From yocto-docs rev: a736c3bb707e81eda7760c642084a5a7c4de2539) Signed-off-by: Scott Rifenbark <srifenbark@gmail.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* ref-manual: Removed the "pid" stuff from viewing failed tasksScott Rifenbark2016-08-181-3/+3
| | | | | | | | | | | | | Fixes [YOCTO #10132] My attempt to be complete on the filenames that have a "pid" portion were not correct. I have removed them from the first paragraph. (From yocto-docs rev: 8261b93b39df9abc9f9d6ccb4c00dc11330ad516) Signed-off-by: Scott Rifenbark <srifenbark@gmail.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* ref-manual: Various small corrections to package-related stuffScott Rifenbark2016-08-183-5/+9
| | | | | | | | | | | | | | | | | | | | | Fixes [YOCTO #10135] Some small problems were fixed: * Added a cross-reference in the FILES glossary entry to the PACKAGES variable. The two are tied and there was not a reference to it. * Removed a redundant "/" character in a pathname example in the dev-manual. * Removed a redundant "/" character in an example pathname in the FILES glossary description. (From yocto-docs rev: 11a397c232696deece7ac5c6dafcadb87d7a5775) Signed-off-by: Scott Rifenbark <srifenbark@gmail.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* ref-manual: Updated the "Viewing Logs from Failed Tasks" section.Scott Rifenbark2016-08-181-10/+23
| | | | | | | | | | | | Fixes [YOCTO #10132] Provided a better description and removed a deprecated sentence near the end. (From yocto-docs rev: bbe588e19bb9ed58883ae7c770da551de659e982) Signed-off-by: Scott Rifenbark <srifenbark@gmail.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* ref-manual: Updated the section on viewing dependenciesScott Rifenbark2016-08-181-20/+87
| | | | | | | | | | | | | | Fixes [YOCTO #10131] The section was renamed "Viewing Dependencies" for consistency. The section was moved up to be the third item in the sub-section list. The section was extensively re-written to provide more clarity and options for the user to view dependencies. (From yocto-docs rev: d521c3aabe6ded105cde6f7b3563c85340f759fd) Signed-off-by: Scott Rifenbark <srifenbark@gmail.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* ref-manual: Clarify and flesh out debugging using bitbake -eScott Rifenbark2016-08-181-21/+54
| | | | | | | | | | | | | | | | Fixes [YOCTO #10099] Renamed the log file section to better describe what the user is accomplishing. Renamed and repositioned the variables section to better describe and emphasize the task. Also fleshed out the variables section with more information. (From yocto-docs rev: 0606fe481416a07bf98fc8ae79a30c1d62e75e6d) Signed-off-by: Scott Rifenbark <srifenbark@gmail.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* dev-manual: Added a new "known issue" for running qemu.Scott Rifenbark2016-08-181-0/+6
| | | | | | | | | | | | | | Fixes [YOCTO #9285] Added a new bullet item to note that Using QEMU in usermode might not work properly when running 64-bit binaries under 32-bit host machines. In particular, "qemumips64" is known to not work under i686. (From yocto-docs rev: 896beb3fddd427f8327d4ddd35be253866c90377) Signed-off-by: Scott Rifenbark <srifenbark@gmail.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* ref-manual: Updated PROVIDES and FILES variable descriptionsScott Rifenbark2016-08-181-1/+15
| | | | | | | | | | | | | | | | Fixes [YOCTO #10094] For PROVIDES, I added information about how the do_package task goes through PACKAGES and uses the FILES variable corresponding to each package to assign files to the package. For FILES, I added a blurb to the existing note how you can find default values for the FILES* variables. (From yocto-docs rev: c70f79a608076c5c0490918b87986554bc5d8353) Signed-off-by: Scott Rifenbark <srifenbark@gmail.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* ref-manual: Updated the SERIAL_CONSOLES_CHECK variable description.Scott Rifenbark2016-08-181-5/+14
| | | | | | | | | Provided a better, more accurate description of this variable. (From yocto-docs rev: 020f927bc01d662601fb44b19e4c6bc70e5e5ee7) Signed-off-by: Scott Rifenbark <srifenbark@gmail.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* ref-manual: Changed the BPN variable description.Scott Rifenbark2016-08-181-13/+10
| | | | | | | | | | | Fixes [YOCTO #10068] Removed redundant wording. (From yocto-docs rev: b6c9c979a01c8070d3d2c23340d3c0f5ef358157) Signed-off-by: Scott Rifenbark <srifenbark@gmail.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* ref-manual: Updates to PARALLEL_MAKE, PARALLEL_MAKEINST, EXTRA_OEMAKEScott Rifenbark2016-08-181-4/+29
| | | | | | | | | | | | | Fixes [YOCTO #10070] Updated these three variables with various items to make clear that PARALLEL_MAKE and PARALLEL_MAKEINST won't work unless EXTRA_OEMAKE is passed to "make". (From yocto-docs rev: 4f8b56cc67502cd672e0296cf2f143ecbcde22ac) Signed-off-by: Scott Rifenbark <srifenbark@gmail.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* ref-manual: Added note to PROVIDES variable description.Scott Rifenbark2016-08-181-0/+17
| | | | | | | | | | | | Fixes [YOCTO #10069] Added a note at the end of the variable description to explain how runtime virual dependencies work. (From yocto-docs rev: de1d16017c27b6b2502735fc41acd22660f6e7b9) Signed-off-by: Scott Rifenbark <srifenbark@gmail.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* ref-manual: New "Fakeroot and Pseudo" section.Scott Rifenbark2016-08-183-0/+86
| | | | | | | | | | | | | Fixes [YOCTO #10060] I provided a new section in the Technical Details chapter. Also some extra explanation was added to both the do_install task and to the D variable. (From yocto-docs rev: 565fb11d72bf8c585469bcf65f92b6738e344813) Signed-off-by: Scott Rifenbark <srifenbark@gmail.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* ref-manual: Added new variable description EXTRANATIVEPATH.Scott Rifenbark2016-08-181-0/+21
| | | | | | | | | | | Fixes [YOCTO #10002] Created new base description for EXTRANATIVEPATH. (From yocto-docs rev: aafc2de2657203440fe4b0bf3895cf367063bed1) Signed-off-by: Scott Rifenbark <srifenbark@gmail.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* ref-manual: Applied review changes to INITRAMF_IMAGE variable.Scott Rifenbark2016-08-181-3/+5
| | | | | | | | | | | | | Fixes [YOCTO #10012] There was a mistake referring to the wrong example recipe. I changed "core-image-sato-initramfs.bb" to "core-image-minimal-initramfs.bb" for the fix. (From yocto-docs rev: 4d63e1fc5786556dd0dd5ca1435252d43dbd745a) Signed-off-by: Scott Rifenbark <srifenbark@gmail.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* ref-manual: Updated the INITRAMFS_IMAGE_BUNDLE variable description.Scott Rifenbark2016-08-181-12/+25
| | | | | | | | | | | Fixes [YOCTO #10013] I enhanced the description with more detail all around. (From yocto-docs rev: 319dabecf5abf0884295b991f681bed0e1dbf673) Signed-off-by: Scott Rifenbark <srifenbark@gmail.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* ref-manual: Updated the do_compile task section.Scott Rifenbark2016-08-181-1/+1
| | | | | | | | | | | | Fixes [YOCTO #9964] There was a small fix to change oe_runmake task to oe_runmake function. (From yocto-docs rev: aa049c9165c67e041c84fab9fabfbe98828c79bb) Signed-off-by: Scott Rifenbark <srifenbark@gmail.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* ref-manual: Updates to INITRAMFS_IMAGE and INITRAMFS_FSTYPESScott Rifenbark2016-08-181-2/+7
| | | | | | | | | | | Fixes [YOCTO #10012] Applied review comments. (From yocto-docs rev: 1862d03c1916c34c29c1aea86fbb6ee4c7f34cca) Signed-off-by: Scott Rifenbark <srifenbark@gmail.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* ref-manual: Updated the INITRAMFS_FSTYPES variable.Scott Rifenbark2016-08-181-0/+11
| | | | | | | | | | | Fixes [YOCTO #10012] Added a new paragraph to the end explaining the default behavior. (From yocto-docs rev: 1591f96fc04f64906145f272d205ec6c44ac70c0) Signed-off-by: Scott Rifenbark <srifenbark@gmail.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* ref-manual: Updated the INITRAMFS_IMAGE variable.Scott Rifenbark2016-08-181-30/+37
| | | | | | | | | | | Fixes [YOCTO #10012] Updated the description completely. New more detailed information. (From yocto-docs rev: cb6ce91674ab092324f97ca4e56a0cbcd9140fbe) Signed-off-by: Scott Rifenbark <srifenbark@gmail.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* ref-manual: Updated the PROVIDES variable description.Scott Rifenbark2016-08-181-0/+28
| | | | | | | | | | | | Added more information about virtual targets to the end of the description. Fixes [YOCTO #10011] (From yocto-docs rev: ce7ae0c6ad4ad3a0c2422b797556563dc48a9a5b) Signed-off-by: Scott Rifenbark <srifenbark@gmail.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* systemd-compat-units: Only enable for systemd in DISTRO_FEATURESRichard Purdie2016-08-181-1/+3
| | | | | | | | | This recipe only makes sense when systemd is enabled and otherwise causes world build failures. (From OE-Core rev: 5dca6cc2fcdb2799c19b1697f0647a16ce296290) Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* systemd-compat-units: pkg_postinst() does not workJoe Slater2016-08-181-7/+10
| | | | | | | | | | | | | | The test for various files is wrong and will always be true, even if init.d does not exist. Exit if init.d does not exist, and correctly test for file existence otherwise. (From OE-Core rev: 8183309080aee45746daaff46b0506b09b5bd269) 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>
* sanity: Require bitbake 1.31.1 for multi-config changesRichard Purdie2016-08-181-1/+1
| | | | | | (From OE-Core rev: ecc8d346223030ee06aa6d83427f757982e948e4) Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* devtool/recipetool/meta: Adapt to bitbake API changes for ↵Richard Purdie2016-08-188-20/+19
| | | | | | | | | | | | | | multi-configuration builds Unfortunately to implenent multiconfig support in bitbake some APIs had to change. This updates code in OE to match the changes in bitbake. Its mostly periperhal changes around devtool/recipetool [Will need a bitbake version requirement bump which I'll make when merging] (From OE-Core rev: 041212fa37bb83acac5ce4ceb9b7b77ad172c5c3) Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* bitbake: bitbake: Update version to 1.31.1Richard Purdie2016-08-182-2/+2
| | | | | | (Bitbake rev: 3ff1c66e6f336e5de7dcbc983a97fcd19ddc6b81) Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* bitbake: bitbake: Initial multi-config supportRichard Purdie2016-08-189-388/+531
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | This patch adds the notion of supporting multiple configurations within a single build. To enable it, set a line in local.conf like: BBMULTICONFIG = "configA configB configC" This would tell bitbake that before it parses the base configuration, it should load conf/configA.conf and so on for each different configuration. These would contain lines like: MACHINE = "A" or other variables which can be set which can be built in the same build directory (or change TMPDIR not to conflict). One downside I've already discovered is that if we want to inherit this file right at the start of parsing, the only place you can put the configurations is in "cwd", since BBPATH isn't constructed until the layers are parsed and therefore using it as a preconf file isn't possible unless its located there. Execution of these targets takes the form "bitbake multiconfig:configA:core-image-minimal core-image-sato" so similar to our virtclass approach for native/nativesdk/multilib using BBCLASSEXTEND. Implementation wise, the implication is that instead of tasks being uniquely referenced with "recipename/fn:task" it now needs to be "configuration:recipename:task". We already started using "virtual" filenames for recipes when we implemented BBCLASSEXTEND and this patch adds a new prefix to these, "multiconfig:<configname>:" and hence avoid changes to a large part of the codebase thanks to this. databuilder has an internal array of data stores and uses the right one depending on the supplied virtual filename. That trick allows us to use the existing parsing code including the multithreading mostly unchanged as well as most of the cache code. For recipecache, we end up with a dict of these accessed by multiconfig (mc). taskdata and runqueue can only cope with one recipecache so for taskdata, we pass in each recipecache and have it compute the result and end up with an array of taskdatas. We can only have one runqueue so there extensive changes there. This initial implementation has some drawbacks: a) There are no inter-multi-configuration dependencies as yet b) There are no sstate optimisations. This means if the build uses the same object twice in say two different TMPDIRs, it will either load from an existing sstate cache at the start or build it twice. We can then in due course look at ways in which it would only build it once and then reuse it. This will likely need significant changes to the way sstate currently works to make that possible. (Bitbake rev: 5287991691578825c847bac2368e9b51c0ede3f0) Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* bitbake: siggen: properly close files rather than opening them inlinePaul Eggleton2016-08-181-6/+9
| | | | | | | | | | If you don't do this, with Python 3 you get a warning on exit under some circumstances. (Bitbake rev: 49502685df3e616023df352823156381b1f79cd3) Signed-off-by: Paul Eggleton <paul.eggleton@linux.intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* bitbake: ast/ConfHandler: Add a syntax to clear variableJérémy Rosen2016-08-184-0/+79
| | | | | | | | | | | | unset VAR will clear variable VAR unset VAR[flag] will clear flag "flag" from var VAR (Bitbake rev: bedbd46ece8d1285b5cd2ea07dc64b4875b479aa) Signed-off-by: Jérémy Rosen <jeremy.rosen@openwide.fr> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* bitbake: cache: Build datastores from databuilder objectRichard Purdie2016-08-183-41/+51
| | | | | | | | | | | | | | Rather than passing in a datastore to build on top of, use the data builder object in the cache and base the parsed recipe from this. This turns things into proper objects building from one another rather than messy mixes of static and class functions. This sets things up so we can support parsing and building multiple configurations. (Bitbake rev: fef18b445c0cb6b266cd939b9c78d7cbce38663f) Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* bitbake: cache: Split Cache() into a NoCache() parent objectRichard Purdie2016-08-181-52/+57
| | | | | | | | | | | There are some cases we want to parse recipes without any cache setup or involvement. Split out the standalone functions into a NoCache variant which the Cache is based upon, setting the scene for further cleanup and restructuring. (Bitbake rev: 120b64ea6a0c0ecae7af0fd15d989934fa4f1c36) Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* bitbake: cache/cooker: Pass databuilder into bb.cache.Cache()Richard Purdie2016-08-182-3/+5
| | | | | | | | | | | | | Rather that the current mix of static and class methods, refactor so that the cache has the databuilder object internally. This becomes useful for the following patches for multi config support. It effectively completes some of the object oriented work we've been working towards in the bitbake core for a while. (Bitbake rev: 7da062956bf40c1b9ac1aaee222a13f40bba9b19) Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* bitbake: cache: Make virtualfn2realfn/realfn2virtual standalone functionsRichard Purdie2016-08-183-40/+35
| | | | | | | | | Needing to access these static methods through a class doesn't make sense. Move these to become module level standalone functions. (Bitbake rev: 6d06e93c6a2204af6d2cf747a4610bd0eeb9f202) Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* bitbake: cache/ast: Move __VARIANTS handling to parse cache functionRichard Purdie2016-08-182-5/+5
| | | | | | | | Simple refactoring to allow for multiconfig support. (Bitbake rev: 266b848da40904446eb1d084bbdc5307a9b45197) Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* bitbake: runqueue: Abstract worker functionality to an object/arrayRichard Purdie2016-08-181-56/+66
| | | | | | | | | | | | | | | With the introduction of multi-config and the possibility of distributed builds we need arrays of workers rather than the existing two. This refactors the code to have a dict() of workers and a dict of fakeworkers, represented by objects. The code can iterate over these. This is separated out from the multi-config changes since its separable and clearer this way. (Bitbake rev: 8181d96e0a4df0aa47287669681116fa65bcae16) Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* bitbake: cookerdata: Simplify prefiles/postfilesRichard Purdie2016-08-181-3/+5
| | | | | | | | | The current codepaths are rather confusing. Stop passing these as parameters and use the ones from when the object is created. (Bitbake rev: 8c992c148d9619b10eeae8bbd9376ecf408037a5) Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* yocto-bsp/yocto-kernel: update to work with the latest kern-toolsBruce Ashfield2016-08-188-12/+11
| | | | | | | | | | | | | | | | With some recent changes in the kern tools, we can drop some changes in the yocto-bsp and yocto-kernel tools that ensured proper patching and BSP inheritance. In particular, we no longer need to signify the start of patching, and we must instruct the tools that we only want configuration fragments via inheritance .. no patches (since they are already applied). (From meta-yocto rev: 34ed5eebd0b5baab98b6b2d7b3f06ca40932b37d) 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>
* parselogs: Ignore amb_nb warning messages under qemux86*Richard Purdie2016-08-181-0/+1
| | | | | | (From OE-Core rev: 857f4ca134e4575e71993b4fa255ebafec612d1e) Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* parselogs.py: Add failed to setup card detect gpio error on x86California Sullivan2016-08-181-0/+1
| | | | | | | | | | | This error has occurred on the MinnowBoard Max and Turbot since its inception. It supposedly indicates a non-working SD card reader, but ours works fine. Whitelist the error. (From OE-Core rev: d577028a1d756b70da056dee73df657cf8000baf) Signed-off-by: California Sullivan <california.l.sullivan@intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* parselogs.py: Add dmi and ioremap errors to ignore list for core2California Sullivan2016-08-181-0/+2
| | | | | | | | | | These errors have been occuring since the introduction of the 4.4 kernel with no apparent functionality loss. Whitelist for now. (From OE-Core rev: 47b9058994f15507fc18ce0b08ac82a4c052966e) Signed-off-by: California Sullivan <california.l.sullivan@intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* parselogs.py: Ignore Skylake graphics firmware load errors on genericx86-64California Sullivan2016-08-181-1/+7
| | | | | | | | | | | | These errors can't be fixed without adding the firmware to the initramfs and building it into the kernel, which we don't want to do for genericx86-64. Since graphics still work acceptably without the firmware blobs, just ignore the errors for that MACHINE. (From OE-Core rev: d73a26a71b2b16be06cd9a80a6ba42ffae8412c4) Signed-off-by: California Sullivan <california.l.sullivan@intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* testimage: allow using kvm when running qemux86* machinesBill Randle2016-08-182-2/+16
| | | | | | | | | | | | Using kvm can provide significant speedups when running qemux86* machines on an x86* host. Enabled by using the new QEMU_USE_KVM variable. [YOCTO #9298] (From OE-Core rev: ebac2c8d1fcd09ebce0659a4abb445e4f1c18571) Signed-off-by: Bill Randle <william.c.randle@intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* image.bbclass: rename COMPRESS(ION) to CONVERSIONPatrick Ohly2016-08-183-38/+39
| | | | | | | | | | | | | | | | | | | With the enhanced functionality, the term "compression" is no longer accurate, because the mechanism also gets used for conversion operations that do not actually compress data. It is possible to remove this naming problem in a backward-compatible manner by including COMPRESSIONTYPES in CONVERSIONTYPES and checking for the old COMPRESS_CMD/DEPENDS as fallbacks. [YOCTO #9346] (From OE-Core rev: 9d68c024790850cab72ead1e3372a5fcec4ef7b0) Signed-off-by: Patrick Ohly <patrick.ohly@intel.com> 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>
* grub: split grub-editenv into it's own packageAlejandro del Castillo2016-08-181-1/+5
| | | | | | | | | | | | | | grub-editenv edits the env block at runtime on a booted system. Other tools can depend on it to configure a live system, for ex. to set next boot mode upon reboot. By splitting grub-editenv, tools don't have to depend on the entire grub package (grub-editenv just edits one file). (From OE-Core rev: 24b832b6e31c4e358d0c7a0062b69f66469cdcee) Signed-off-by: Alejandro del Castillo <alejandro.delcastillo@ni.com> Signed-off-by: Ioan-Adrian Ratiu <adrian.ratiu@ni.com> Signed-off-by: Ross Burton <ross.burton@intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* bash: 4.3.39 -> 4.3.46Dengke Du2016-08-181-0/+21
| | | | | | | | (From OE-Core rev: 2e12615ca5ab4acf7ec2952b7555054ca88e147d) Signed-off-by: Dengke Du <dengke.du@windriver.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-28 00:43:48 +0000