summaryrefslogtreecommitdiffstats
path: root/meta/conf
Commit message (Collapse)AuthorAgeFilesLines
* tune-cortexa5.inc: Add tune options for vfpv4Khem Raj2019-01-211-2/+14
| | | | | | | (From OE-Core rev: dfcfc735b38851e95282a0b5e12d0d59b951ffe5) Signed-off-by: Khem Raj <raj.khem@gmail.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* bitbake.conf: Enable -fdebug-prefix-map for nativesdkRobert Yang2019-01-141-1/+1
| | | | | | | | | | | Files like lib/.debug/libgcc_s.so.1 from nativesdk-libgcc-dbg contains buildpath without -fdebug-prefix-map, the root cause is object files (.o) contain buildpath, and then ccache can't use them correctly. (From OE-Core rev: b0b4d1b32203bb74fc3aec9b9a0d14bf7a52a0af) Signed-off-by: Robert Yang <liezhi.yang@windriver.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* ccache.bbclass: Set CCACHE_CONFIGPATH to fix race issuesRobert Yang2019-01-141-0/+2
| | | | | | | | | | | | | | | | | | | | | | | | | | Fixed race issues when parallel build: ccache: error: /path/to/ccache/i586-poky-linux/mmc-utils/ccache.conf: No such file or directory ccache: error: /path/to/ccache/i586-poky-linux/mmc-utils/ccache.conf: No such file or directory This is because we set CCACHE_DIR for earch recipe, and ccache will create a ccache.conf for each CCACHE_DIR when CCACHE_CONFIGPATH is not set, but there might be a race issue in parallel build: ccache gcc file1.c ccache gcc file2.c If the two ccache processes use fopen(path, "w") to create ccache.conf at the same time, the error would happen. Set CCACHE_CONFIGPATH to meta/conf/ccache.conf can fix the problem, and we can add other configs to the file when needed. And also set cache_dir_levels to 1 (default is 2) since each recipe has a cache dir, thus we don't have too many files in one dir. (From OE-Core rev: 2abbc4d0cd571e82ed6188d3b2d84b4cd6be25e8) Signed-off-by: Robert Yang <liezhi.yang@windriver.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* ccache.bbclass: Refactor it to make it more reliableRobert Yang2019-01-142-6/+1
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | The previous ccache.bbclass has the following problems: - It uses host's ccache for native recipes, but this may not work on some hosts, for example, it nerver works on my Ubuntu 14.04.4, there are always build failures (m4-native failed at do_configure, and others will also be failed if I disable CCACHE for m4-native) - native/nativesdk/cross/crosssdk recipes use host's ccache, but target uses ccache-native, this may confuse user. - The target recipes may use both host's ccache and ccache-native, this may cause unexpected problems and be hard to debug. This is because ccache-native is in SIGGEN_EXCLUDE_SAFE_RECIPE_DEPS, so ccache-native may not be present when rebuild target recipes, and then it would use hosttools/ccache, but the previous ccache files were generated by ccache-native. - Target recipes can't use ccache when no ccache is installed on the host: CCACHE = "${@bb.utils.which(d.getVar('PATH'), 'ccache') and 'ccache '}" After refactored: All types recipes (native, target and others) will use ccache-native except ccache-native itself, host's cache won't be used any more. It is more reliable now, which will work everywhere when ccache-native can be built. And now we need use "CCACHE_DISABLE = '1'" to disable ccache for the recipe rather than "CCACHE = ''" since we set CCACHE in anonymous function, and d.getVar('CCACHE') works after "CCACHE ??=" which is set in bitbake.conf, so we can't check whether CCACHE is set or not in anonymous function since it is always set. Use CCACHE_DISABLE to disable it would be more clear. (From OE-Core rev: b25271b65262f70d849a4861da216c9be6c54d53) Signed-off-by: Robert Yang <liezhi.yang@windriver.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* bitbake.conf: add --enable-new-dtags to linkerAlexander Kanavin2019-01-111-0/+1
| | | | | | | | | | | | | | | | | | | Various versions of ld have different defaults for this (even between e.g. Ubuntu 16.04 and 18.04). This has the consequence of putting either RPATH or RUNPATH into the binary, depending on the linker, which have different priorities vs LD_LIBRARY_PATH env var. Also, I think, the original executable binary is looked up for the tags when resolving a dependency of a shared library when using RPATH, but not RUNPATH. Let's make this deterministic. (From OE-Core rev: 661d700ab7428b0ad982bfd2714cca134bad85a2) Signed-off-by: Alexander Kanavin <alex.kanavin@gmail.com> Signed-off-by: Ross Burton <ross.burton@intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* linux-libc-headers: update to v4.19Bruce Ashfield2019-01-081-1/+1
| | | | | | | | | | | | | Updating the linux-libc-headers to match the latest reference kernel in oe-core. We addtionally add three patches (identified by Khem) to fix muslc aarch64 build issues. (From OE-Core rev: 11f02b7c6f9854eecd3a49ea47833c8cbffb1581) Signed-off-by: Bruce Ashfield <bruce.ashfield@windriver.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* sstate: Implement hash equivalence sstateJoshua Watt2019-01-081-1/+3
| | | | | | | | | | | | | | | | | | | | | Converts sstate so that it can use a hash equivalence server to determine if a task really needs to be rebuilt, or if it can be restored from a different (equivalent) sstate object. The unique hashes are cached persistently using persist_data. This has a number of advantages: 1) Unique hashes can be cached between invocations of bitbake to prevent needing to contact the server every time (which is slow) 2) The value of each tasks unique hash can easily be synchronized between different threads, which will be useful if bitbake is updated to do on the fly task re-hashing. [YOCTO #13030] (From OE-Core rev: d889acb4f8f06f09cece80fa12661725e6e5f037) Signed-off-by: Joshua Watt <JPEWhacker@gmail.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* arch-armv4.inc, arch-armv5.inc: Do not tie generating thumb ISA to -marchKhem Raj2019-01-072-2/+2
| | | | | | | | | | | | | | | -march=armv5't'e means that CPU can execute thumb ISA, we do not need to tie this to exclusively generating thumb ISA, this change means that when we have thumb in tune features then it can use 't' in -march options irrespective of ISA being thumb or arm. This fixes derivative of armv5 tunes and paves way for gcc9 where e.g. armv5e is dropped and minimum arch supported is armv5te (From OE-Core rev: 49bc3eab2897307a92b538a045e3d4dce245b0e0) Signed-off-by: Khem Raj <raj.khem@gmail.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* maintainers.inc: Add entry for new eglinfo-wayland recipeRichard Purdie2019-01-031-0/+1
| | | | | | (From OE-Core rev: c5351163578a888270b08eec775e123c030dd7e5) Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* tcmode-default: Drop pinnings for gcc-initial based recipesKhem Raj2018-12-261-2/+0
| | | | | | | (From OE-Core rev: 5b2fd1c72407d3024512982685d8b1227c2631af) Signed-off-by: Khem Raj <raj.khem@gmail.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* recipes: Drop virtual/libc-for-gccRichard Purdie2018-12-262-3/+0
| | | | | | | | | We no longer have special "libc" for gcc so we can rely on plain virtual/libc and reduce the complexity in the dependencies. (From OE-Core rev: 122217b421f749b5fef52bea44ad6e04bc8f8d3a) Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* upstream-tracking.inc: Remove the long deprecated fileRichard Purdie2018-12-181-24/+0
| | | | | | (From OE-Core rev: 22447eba250656489a6ed636fe58cb304d74e975) Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* defaultsetup: Include maintainers.inc by defaultRichard Purdie2018-12-181-0/+1
| | | | | | | | | There is little harm in including this file rather than having a rather obscure and soon to be obsolete bbclass adding this information. (From OE-Core rev: 98536be8d1a5dcf620ee6d07135f23126a09d98f) Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* arch-powerpc64.inc: Use elfv2 ABI when building with muslSerhey Popovych2018-12-151-0/+3
| | | | | | | | | | | | | | | | | | | | | | Historically first PowerPC ABI was big-endian only (elfv1 currently). It is standard ABI for both 32-bit ppc and 64-bit ppc64 architectures. With PowerPC little-endian support new ABI was introduced (elfv2) and it is used primarily with ppc64le target only. While it has support for big-endian it is not commonly used and elfv1 still preferred. Musl does support only elfv2 ABI for both LE and BE and does not have any plans to support elfv1. Since then to build for powerpc64 with musl new ABI should be used. As expected it is not compatible with elfv1 but that isn't problem as long as there is no binary distributed software or assembly code written for elfv1 ABI. (From OE-Core rev: 68c9641855199f34aabe1050e863c21830116fe1) Signed-off-by: Serhey Popovych <serhe.popovych@gmail.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* tune-power[5-7].inc: Disable QEMU usermode usageSerhey Popovych2018-12-153-0/+9
| | | | | | | | | | The QEMU usermode fails with invalid instruction error when used with those tunes. (From OE-Core rev: c1c881ef7f4faf94f385ae742030382122ee5816) Signed-off-by: Serhey Popovych <serhe.popovych@gmail.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* tune-power[5-7].inc: Fix DEFAULTTUNE valuesSerhey Popovych2018-12-153-3/+3
| | | | | | | | | | It is ppcpX, not ppcprX, where X is 6 or 7. While there select 32bit tune for P5 machine to bring it inline with P6 and P7. (From OE-Core rev: 220eee184a4f510cdf7c55e2aed00330abee1553) Signed-off-by: Serhey Popovych <serhe.popovych@gmail.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* qemu: Bump to version 3.1Alistair Francis2018-12-151-1/+1
| | | | | | | | | Bump QEMU to the latest 3.1 and update the patches. (From OE-Core rev: eeb918fc9b67a5d252b9d5ad5f3674cc1a45aa7f) Signed-off-by: Alistair Francis <alistair.francis@wdc.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* maintainers: Add entry for libpsl (required by libsoup)Richard Purdie2018-12-151-0/+1
| | | | | | (From OE-Core rev: 70a1a10ddb2e7e99d4d854c653e89799a16aad74) Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* yocto-uninative: Correct sha256sum for aarch64Michael Halstead2018-12-151-1/+1
| | | | | | | | | Avoid uninative checksum warnings when building on aarch64 hardware. (From OE-Core rev: 3ccc2de5f08fb2023abeeed39e23c68dbc75725b) Signed-off-by: Michael Halstead <mhalstead@linuxfoundation.org> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* maintainers: Clarify/add several entriesRichard Purdie2018-12-141-14/+43
| | | | | | | | | | Images were previously missing but are added, this also corrects the names used for gcc/go/bintuils/gdb recipes and adds a few other misc missing ones to ensure we have complete coverage of the recipes in OE-Core. (From OE-Core rev: 6408b4b90833706dd1307f845266dcf9fccdbcaf) Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* libart-lgpl: removeRoss Burton2018-12-081-1/+0
| | | | | | | | | This is very dead, and nothing in oe-core or meta-oe depends on it anymore. (From OE-Core rev: 508746e28d971952b1153a4c24ee3c5a020f9ee9) Signed-off-by: Ross Burton <ross.burton@intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* bitbake.conf: Cleanup deprecated function usageRichard Purdie2018-12-081-3/+3
| | | | | | | | | This function was moved in bitbake a long time ago, use the preferred version to avoid a Deprecation warning. (From OE-Core rev: aeb189ac8bc6625ec936fd69f18974ebde758946) Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* packages: respect PACKAGE_NO_GCONVKai Kang2018-12-051-1/+1
| | | | | | | | | | | | | PACKAGE_NO_GCONV is set in libc-package.bbclass if not all of 'libc-charsets libc-locale-code libc-locales' included in DISTRO_FEATURES. And then no packages glibc-gconv-* glibc-charmap-* and glibc-localedata-* is created. Update recipes and conf file which depend on these packages to check required distro features. (From OE-Core rev: 58446992de0f16a345f1f55b66d0d34d31dc341b) Signed-off-by: Kai Kang <kai.kang@windriver.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* licence: Add license file CC-BY-SA-4.0Eric Chanudet2018-12-011-1/+1
| | | | | | | | | | Original legalcode.txt: https://creativecommons.org/licenses/by-sa/4.0/legalcode.txt (From OE-Core rev: fa06fcce7942f5960178dcdeb61a7b659f7f8207) Signed-off-by: Eric Chanudet <chanudete@ainfosec.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* maintainers.inc: update Intel ownersAnuj Mittal2018-11-271-85/+85
| | | | | | | (From OE-Core rev: 198fe6d08f000b3db9082b5fd4337536931719ee) Signed-off-by: Anuj Mittal <anuj.mittal@intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* u-boot: Add mkenvimage toolAlexey Brodkin2018-11-232-2/+2
| | | | | | | | | | | | | | | | | | | | | | | | | This utility is used for creation of images containing usable in run-time U-Boot environment. As of today this utility is added per-board like here [1] for Intel Edison board. [1] http://git.yoctoproject.org/cgit/cgit.cgi/meta-intel-edison/tree/meta-intel-edison-bsp/recipes-bsp/u-boot/u-boot-tools_2014.04.bb Given there're quite some U-Boot tools that we may want to add later this recipe name switch from "u-boot-mkimage" to generic "u-boot-tools" still for compatibility we provide "u-boot-mkimage" with help of PROVIDES as well as proposed "u-boot-mkenvimage". (From OE-Core rev: 314885b16e5d26d27d46a4bfb0d581b27a03b8fe) Signed-off-by: Alexey Brodkin <abrodkin@synopsys.com> Cc: Richard Purdie <richard.purdie@linuxfoundation.org> Cc: Otavio Salvador <otavio@ossystems.com.br> Cc: Martin Jansa <martin.jansa@gmail.com> Cc: Ross Burton <ross.burton@intel.com> Cc: Marek Vasut <marex@denx.de> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* documentation: Add newlib to TCLIBC's [doc] entryRichard Purdie2018-11-231-1/+1
| | | | | | | | | | TCBLIC can be set to 'newlib' now, document this. [YOCTO #13032] (From OE-Core rev: d06271500c485686536352f1202a74d21c51a406) Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* maintainers: Add entry for new recipe libdazzleRichard Purdie2018-11-221-0/+1
| | | | | | (From OE-Core rev: c80972be1f3592d797da9eb0845b739420c6da4a) Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* maintainers.inc: add libmodulemd entryAlexander Kanavin2018-11-211-0/+1
| | | | | | | (From OE-Core rev: bdeb0277c084ac4ecfa21bd77d318a9b0c39616d) Signed-off-by: Alexander Kanavin <alex.kanavin@gmail.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* maintainers.inc: Add entry for libjitterentropy (copied from rng-tools)Richard Purdie2018-11-141-0/+1
| | | | | | (From OE-Core rev: 9a24e79aea2fb3c60803cb265c1d03a1873cfe9d) Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* machine/qemu*: fix kernel finish crng init more and more slowlyHongxu Jia2018-11-145-5/+11
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | Just adding `-device virtio-rng-pci' to the QEMU invocation will add the device with a default host backend. As of QEMU 1.3+, the default backend is to use the host's /dev/random as a source of entropy. [1] When the entropy pool is empty, reads from /dev/random will block until additional environmental noise is gathered. [2] For Yocto, if call runqemu frequently, it will consume lots of host's /dev/random, and kernel finish crng init in guest get more and more slowly. Here are 4 times runqemu boot test: [ 3.464432] random: crng init done [ 20.874030] random: crng init done [ 23.583589] random: crng init done [ 23.858945] random: crng init done Modify entropy source to /dev/urandom device on the host which returns random bytes using a pseudorandom number generator seeded from the entropy pool. Reads from this device do not block and kernel finish crng init in guest will not delay. Of course, the side effect is obviously, we lost the quality of randomness, but the modification is only on runqemu script rather than real embedded device, and it benefits oeqa efficiency in which many cases call runqemu especially multiple oeqa builds on one host. After apply the fix: [ 3.364670] random: crng init done [ 4.619061] random: crng init done [ 3.403897] random: crng init done [ 3.450717] random: crng init done [1] https://wiki.qemu.org/Features/VirtIORNG [2] http://man7.org/linux/man-pages/man4/random.4.html (From OE-Core rev: 853644f82eb3205ef3efc1ea3959c7225dfacf61) Signed-off-by: Hongxu Jia <hongxu.jia@windriver.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* ppce500v2: remove speChunrong Guo2018-11-141-1/+1
| | | | | | | | | *The PowerPC SPE support is split off to a separate powerpcspe port (From OE-Core rev: c67bc9bdcbcf46ed54dfbafd1bb6e405ed77f86a) Signed-off-by: Chunrong Guo <chunrong.guo@nxp.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* oe-init-buildenv/base: Relax python version checks in favour of HOSTTOOLS ↵Richard Purdie2018-11-071-1/+2
| | | | | | | | | | | | | | manipulation Several distros are now shipping "python" as python v3 contra to the original python guidelines. This causes users confusion/pain in trying to use our tools. We can just force "python" to "python2" within HOSTTOOLS to avoid this issue and hide the complexity from the user. (From OE-Core rev: b06a6cde5c5503f456f260c773cf126085e18c8d) Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* yocto-uninative: Upgrade to verson 2.3 which includes glibc 2.28Richard Purdie2018-10-281-5/+5
| | | | | | | | | This allows us to handle distros which contain glibc 2.28 such as Ubuntu 18.10. (From OE-Core rev: 5c7d9abcd611d23d4340f9a0aee2564f72158a0b) Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* weston: Split out machine specific configurationMark Hatle2018-10-282-0/+2
| | | | | | | | | | | | | | | Weston needs to be configured to load the fbdev driver when run on a QEMU system. Other MACHINEs may want to also provider their own configuration as well.. Adding a new RRECOMMEND configuration package will allow this, but avoid installing empty packages/files in the majority case where it is not needed. Add maintainer entry as well. (From OE-Core rev: 0f43ea8510ae6148a49eb25accac407b6b301b43) Signed-off-by: Mark Hatle <mark.hatle@windriver.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* tcmode-default: Drop pinning go to 1.9Khem Raj2018-10-211-1/+1
| | | | | | | | | | This ensures that we default to latest go recipes 1.9 is not supported anymore (From OE-Core rev: d48c8148eae41e613448d78c26516538244cd9c9) Signed-off-by: Khem Raj <raj.khem@gmail.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* systemd: Remove items that made this machine (qemu) specificMark Hatle2018-10-212-0/+2
| | | | | | | | | | | | | | | | Create a new systemd-conf recipe to contain the specific system/machine configuration items. This new package is now machine specific. Without doing this trying to create a single system with multiple BSPs, one of which was qemu based, would result in the systemd -and- everything that dependend upon systemd to have their hash changed. The hash changing means lots of rebuilds, but worse if it's a package based system each different machine ends with a new PR value and a newly generated package. (From OE-Core rev: d3395418758ed414eee3e95e13d2d8bc5dca88cc) Signed-off-by: Mark Hatle <mark.hatle@windriver.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* Revert "os-release: avoid multilib expand"Richard Purdie2018-10-201-1/+1
| | | | | | | | This reverts commit 591a11ba58ce3c2c147bb1f8202bc6a0092b70eb. This is not needed after the recent os-release fix. Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* qemux86/gstreamer: Move kernel module recommendation to the machine ↵Richard Purdie2018-10-182-0/+4
| | | | | | | | | | | | | | | | | | | configuration If you try to build a system with multiple BSPs, one of which is qemux86 or qemux86-64, the gstreamer package will change. This will trigger anything using gstream to also be rebuilt. For a package based system, the PR values will also be incremented each time. The end result will be an ever growing set of PR values as well as being unable to tell which configured version of the multimedia components are really being deployed. These therefore belong in the machine configuration. (From OE-Core rev: 112775995158cf6c504fd6beef345ee446f4f11d) Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* maintainers: assign CMake to Pascal BachRoss Burton2018-10-181-2/+2
| | | | | | | (From OE-Core rev: 954a7715763118ba8e15ce7a96a2b82680f4a6c4) Signed-off-by: Ross Burton <ross.burton@intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* conf/machine/include: add mcf5441x cpu type tuningAngelo Dureghello2018-10-081-0/+13
| | | | | | | | | This patch adds tuning for the mcf5441x ColdFire family. (From OE-Core rev: 89e7192b607361769c03b939437c9815672ceadb) Signed-off-by: Angelo Dureghello <angelo@sysam.it> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* conf/machine/include: add m68k architecture definitionsAngelo Dureghello2018-10-081-0/+8
| | | | | | | (From OE-Core rev: 475ca28ab1b42fc0307669edae220afb97dd15c3) Signed-off-by: Angelo Dureghello <angelo@sysam.it> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* os-release: avoid multilib expandKai Kang2018-10-041-1/+1
| | | | | | | | | | Add os-release to NON_MULTILIB_RECIPES in multilib.conf that do not do multilib expand for os-release. (From OE-Core rev: 361382ca16c276e1e404eab58c0956a2b6d23d7e) Signed-off-by: Kai Kang <kai.kang@windriver.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* multilib: avoid expanding grub and grub-efi to multilibRobert Yang2018-10-011-0/+4
| | | | | | | | | | | | | | | | | | | | | | It doesn't make much sense to expand them to multilib, and there is an error on qemuarm64 since grub-efi supports arm64, but doesn't support armv7a or armv7ve: * Fixed: MACHINE = "qemuarm64" require conf/multilib.conf MULTILIBS = "multilib:lib32" DEFAULTTUNE_virtclass-multilib-lib32 = "armv7a" MACHINE_FEATURES_append = " efi" $ bitbake lib32-core-image-minimal Also introduced a variable NON_MULTILIB_RECIPES in multilib.conf, so that we can easily add other recipes, such as syslinux if needed. (From OE-Core rev: 25f7c6c329038b443d36074fff45a30ba3712f7a) Signed-off-by: Robert Yang <liezhi.yang@windriver.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* layer.conf: Drop sumo from LAYERSERIES_CORENAMESRichard Purdie2018-10-011-1/+1
| | | | | | | | | | | Prepare for release and drop sumo for the compatible list of layer names. This will mean other layers need updating to continue to indicate compatibility with master but that is intentional at this part of the release cycle, we want layers to indicate compatibility and show they're up to date. (From OE-Core rev: 9ec5a8a0f86510f7aae572dfb79e8bda73d4e0fc) Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* layer.conf: Add thud to LAYERSERIES_CORENAMESRichard Purdie2018-09-241-2/+2
| | | | | | | | | | | With the release approaching, add thud to LAYERSERIES_CORENAMES and update oe-core to use this release series. "sumo" will be removed during M4 in the next couple of weeks so people need to start updating their master layers in preperation for release. (From OE-Core rev: 986792481fa005fe136fd4b4e388042492b1ad8a) Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* yocto-uninative: Add aarch64 uninative tarball checksumRichard Purdie2018-09-201-0/+1
| | | | | | (From OE-Core rev: 957a2f95b839f2d871c658d6e8ea8c0f4d6c41e5) Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* maintainers.inc: Update package ownersMaxin B. John2018-09-201-124/+124
| | | | | | | | | | update Intel owners (From OE-Core rev: a6de4b1809e90d02a865c56ec8269bdfa3ceec0a) Signed-off-by: Maxin B. John <maxin.john@intel.com> Signed-off-by: Ross Burton <ross.burton@intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* libressl: remove recipeHongxu Jia2018-09-201-1/+0
| | | | | | | | | | Since openssh support oepnssl 1.1.x, there is no reason to keep libressl. (From OE-Core rev: 30121a78555574f49b321566fcab172417bdf3e3) Signed-off-by: Hongxu Jia <hongxu.jia@windriver.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* tune-core2: use n270 instead of core2duoAnuj Mittal2018-09-131-1/+1
| | | | | | | | | | | | | | | | | | | | | | | | | Fixes warnings in builds using core2-32 tune: warning: TCG doesn't support requested feature: CPUID.80000001H:EDX.syscall [bit 11] warning: TCG doesn't support requested feature: CPUID.80000001H:EDX.lm [bit 29] when executing postinsts using qemu-i386. i386 target doesn't enable CPUID_EXT2_SYSCALL and CPUID_EXT2_LM [1] while cpu choice of core2duo that we use for core2-32 TUNE does [2]. Use n270 cpu instead to use with qemu which supports SSSE3 and doesn't have these bits enabled [3]. [1] https://github.com/qemu/qemu/blob/master/target/i386/cpu.c#L739 [2] https://github.com/qemu/qemu/blob/master/target/i386/cpu.c#L1439 [3] https://github.com/qemu/qemu/blob/master/target/i386/cpu.c#L1603 Fixes [YOCTO #12916] (From OE-Core rev: 3db567d7835c6bb158d0f6c5b5533835a0181c45) Signed-off-by: Anuj Mittal <anuj.mittal@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-11-16 12:03:03 +0000