summaryrefslogtreecommitdiffstats
path: root/meta/conf
Commit message (Collapse)AuthorAgeFilesLines
...
* bitbake.conf: propagate 'opengl' DISTRO_FEATURE to native/nativesdk from targetAlexander Kanavin2020-05-271-2/+2
| | | | | | | | | | | | | | | | This will allow better control over native virgl/qemu configurations. Adjust gtk+3/cairo native configurations to actually ignore opengl when building for -native: we do not need it, and it would cause build failures as only a limited subset of mesa-native is currently built. Drop native/nativesdk overrides from virglrenderer/libepoxy recipes as opengl feature is now correctly set for those variants. (From OE-Core rev: 0e1f8fa0535dab63742f575b52ec9fa891368ca2) Signed-off-by: Alexander Kanavin <alex.kanavin@gmail.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* layer.conf: Move to gatesgarth namingRichard Purdie2020-05-181-2/+2
| | | | | | | | | We're still compatible with dunfell from the core perspective so that is left for compatibility (probably for the next week or two). (From OE-Core rev: 1e79324f8290b820fee034b0d4a8c353027879da) Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* pyelftools: Import from meta-pythonJoshua Watt2020-05-181-0/+1
| | | | | | | | | | | | | Imports the pyelftools recipes from meta-python, as of 7c02c7d41 ("gnome-themes-extra: correct the recipe name"). This recipe is commonly used by other layers, so moving it into OE-core helps to cut down on layer dependencies. (From OE-Core rev: 910ffaf5beed42936588c95b0c7c1b1ad67f99d3) Signed-off-by: Joshua Watt <JPEWhacker@gmail.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* pycryptodome: Import from meta-pythonJoshua Watt2020-05-181-1/+3
| | | | | | | | | | | | | Imports the pycryptodome recipes from meta-python, as of 7c02c7d41 ("gnome-themes-extra: correct the recipe name"). These recipes are commonly used by other layers, so moving them into OE-core helps to cut down on layer dependencies. (From OE-Core rev: a96f815c53364b119b5743b8b7100eb5588d5cf5) Signed-off-by: Joshua Watt <JPEWhacker@gmail.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* qemuarm64.conf: Use cortext-a57 as default tuneKhem Raj2020-05-151-1/+1
| | | | | | | | | This is more appropriate for the machine we are emulating (From OE-Core rev: b9499c39697593cc392bba47b35f721f5885310c) Signed-off-by: Khem Raj <raj.khem@gmail.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* armv8/tunes: Define TUNE_PKGARCHKhem Raj2020-05-157-0/+13
| | | | | | | | | | Now that they uses -mcpu, its better to have tune specific build directories, since aarch64 wont be appropriate any longer (From OE-Core rev: 030cd9021ef50d71482f6acf0e05fe425038c822) Signed-off-by: Khem Raj <raj.khem@gmail.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* aarch64: Adjust big.LITTLE tune files to use -mcpuKhem Raj2020-05-153-20/+11
| | | | | | | | | | | | mcpu is more appropriate on aarch64 and generates more optimized code forr a given SOC, unlike -march/-mtune combination as decribed here [1] [1] https://community.arm.com/developer/tools-software/tools/b/tools-software-ides-blog/posts/compiler-flags-across-architectures-march-mtune-and-mcpu (From OE-Core rev: e114c670d1e670397c1c04292688b7550f54027c) Signed-off-by: Khem Raj <raj.khem@gmail.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* tune-cortexa57.inc: Add new tune fileKhem Raj2020-05-151-0/+17
| | | | | | | (From OE-Core rev: 03b04fcfa5549a54fe6f335df14433934a7d5128) Signed-off-by: Khem Raj <raj.khem@gmail.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* tune-cortexa55.inc: crc and crypto extentions are default on cortex-a55Khem Raj2020-05-151-7/+3
| | | | | | | (From OE-Core rev: 886333c5d1c336da99300d24fb3c15ab0b37d1cb) Signed-off-by: Khem Raj <raj.khem@gmail.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* gcc10: Update to GCC 10.1 ReleaseKhem Raj2020-05-142-2/+2
| | | | | | | | | | | | | | | | | * Package new gomp header acc_prof.h * Package lto-dump which is a new tool in gcc10 * All Changes are here [1] * Porting apps to gcc 10 help is here [2] * Backport a patch to fix CET errors on cross builds * Add patch to fix mingw libstdc++ [1] https://gcc.gnu.org/gcc-10/changes.html [2] https://gcc.gnu.org/gcc-10/porting_to.html (From OE-Core rev: 44c3881b18f74eb64379818fc150f94398fb8a49) Signed-off-by: Khem Raj <raj.khem@gmail.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* tunes: Add new tune files for cortexa55 and cortexa73-cortexa53Khem Raj2020-05-122-0/+40
| | | | | | | (From OE-Core rev: fd4a454b5a357c7a26792bf486212957c698839c) Signed-off-by: Khem Raj <raj.khem@gmail.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* bitbake.conf: Prevent git from detecting parent repo in recipeJoshua Watt2020-05-091-1/+5
| | | | | | | | | | | | | Prevents git commands run in a recipe from moving up past ${WORKDIR} when searching for a .git directory, and thus prevents them from detecting the parent OE-core .git directory. Fixes several reproducibility issues where recipes would use the OE-core version as the recipe version due to git walking up the tree. (From OE-Core rev: e496605ea197414b58025293e73dec099a8976c6) Signed-off-by: Joshua Watt <JPEWhacker@gmail.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* libva-initial: New bootstrap recipeZoltan Boszormenyi2020-05-091-0/+1
| | | | | | | | | | | | | | | | | | | | | | | | | | | Mesa needs libva.pc and libva headers to enable the VAAPI state tracker and drivers. This recipe is a variant of the full libva package build as in: * it only depends on libdrm to build so it doesn't introduce the circular dependency between mesa and libva, and * it doesn't include the libraries in the final package. However, there is another issue with build dependency handling in Yocto. libva depends on mesa and mesa depends on this package. Any package that depends on libva therefore would pull in libva and this package resulting in an error in the prepare-sysroot phase because they would install identical files into the per-recipe sysroot. Using the package name "*-initial" avoids this because of the interaction between sstate.bbclass and staging.bbclass: any package with the pattern "*-initial" in the name is excluded from the dependency list unless explicitly added to DEPENDS. (From OE-Core rev: b697f0446f9b016c6c229edda1bf20ca3a7c88ce) Signed-off-by: Böszörményi Zoltán <zboszor@pr.hu> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* documentation.conf: Add variables supported by features_check.bbclassRobert P. J. Day2020-05-091-2/+9
| | | | | | | | | | Add to documentation.conf all the new variables supported by features_check.bbclass. (From OE-Core rev: 77df7e9b822c1d895d2e0212300f836eeff10b3d) Signed-off-by: Robert P. J. Day <rpjday@crashcourse.ca> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* libhandy: add a recipe from meta-oeAlexander Kanavin2020-05-071-0/+1
| | | | | | | | | This is needed by new versions of epiphany browser. (From OE-Core rev: 348467b3e6d607c662a48e3a7e31d15b5fde9f97) Signed-off-by: Alexander Kanavin <alex.kanavin@gmail.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* avahi: merge avahi-ui into the main recipeAlexander Kanavin2020-05-071-1/+0
| | | | | | | | | | | | | The split was building the same code twice, awkward to maintain, and causing issues with upgrades. Disabling the gtk bits can be easily done through the standard PACKAGECONFIG mechanism when needed. (From OE-Core rev: 33cfebfed51166e409cbb05ab7bbc3fff7c7f36d) Signed-off-by: Alexander Kanavin <alex.kanavin@gmail.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* libinput: add ptestAlexander Kanavin2020-05-071-0/+1
| | | | | | | | | The test takes about 17 minutes, and fully passes. (From OE-Core rev: adc4dbb748c01b731035a759de7cd798d7860d0c) Signed-off-by: Alexander Kanavin <alex.kanavin@gmail.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* python3-dbusmock: add recipe from meta-oeAlexander Kanavin2020-05-031-0/+1
| | | | | | | | | This is needed for glib ptests. (From OE-Core rev: 6dbe449ac2ed7c93f71f00d53237c6aba4ebbf81) Signed-off-by: Alexander Kanavin <alex.kanavin@gmail.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* libmodulemd: move from 1.x to 2.x versionAlexander Kanavin2020-05-021-1/+1
| | | | | | | | | | New libdnf requires 2.x and is the only consumer in oe-core (or elsewhere). (From OE-Core rev: 2c518de672d8876ff96e49b498feb898a497e6a5) Signed-off-by: Alexander Kanavin <alex.kanavin@gmail.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* abi_version/staging: Bump versions to force rebuild after sstate corruptionRichard Purdie2020-05-021-1/+1
| | | | | | | | | | | | | | | | | | A "broken" buildtools-extended-tarball has been released into the wild where it is optimising binaries for the host processsor. This is fine in local usage but in a non-homogeneous cluster like our autobuilder, this results in SIGILL on other machines when the sstate is shared amongst them and is painful to debug. The buildtools tarball has been fixed but we need to invalidate the hash equivalence and sstate data. This change does that. Adding to OE-Core rather than autobuilder local changes as its good to illustrate how to do this and the issue is potentially wider than just Yocto Project infrastructure. (From OE-Core rev: 23cdfa9eb23146a69edb77a83ef03719a62ddaae) Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* image/packagegroup: Remove PACKAGE_GROUP_*, long since deprecatedRichard Purdie2020-04-291-1/+0
| | | | | | | | This was deprecated in 2014 so we can safely remove the old code now. (From OE-Core rev: fe1b79188cbe8159a0950f0c02d7f476a6694a04) Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* maintainers.inc: add entries for cython and pyparsingAlexander Kanavin2020-04-291-0/+2
| | | | | | | (From OE-Core rev: 74f1170657aa92c809b7b903d00415fbd8e6adf3) Signed-off-by: Alexander Kanavin <alex.kanavin@gmail.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* layer.conf: Drop zeus compatibility for dunfell releaseRichard Purdie2020-03-291-2/+2
| | | | | | (From OE-Core rev: 8930cd153084f58c2c1c8950dc0ddce786db548b) Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* qemuarmv5.conf: drop stray comment including tune-arm1136jf-s.incAndre McCurdy2020-03-291-1/+0
| | | | | | | | | | | | An old comment which appears to have been checked in by accident as part of an unrelated change: https://git.openembedded.org/openembedded-core/commit/?id=e9ebcc4c19a624f76051c0a25d9ecf6ac4afb257 (From OE-Core rev: 29a9a2edca220bd9562e7ab5ae7df1d0b58f4d07) Signed-off-by: Andre McCurdy <armccurdy@gmail.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* tune-arm1176jz-s.inc: fix typo in PACKAGE_EXTRA_ARCHS_tune-arm1176jzsAndre McCurdy2020-03-291-1/+1
| | | | | | | (From OE-Core rev: 0481ef62fb9d3fae2e475aad7cbf3d3a29439a79) Signed-off-by: Andre McCurdy <armccurdy@gmail.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* tune-arm1136jf-s.inc: restore vfp to TUNE_FEATURES_tune-arm1136jfsAndre McCurdy2020-03-291-1/+1
| | | | | | | | | | | | | | The change to TUNE_FEATURES_tune-arm1136jfs as part of: https://git.openembedded.org/openembedded-core/commit/?id=ac83d22eb5031f7fdd09d34a1a46d92fd3e39a3c effectively removed both armv6 and vfp, when it should have removed armv6 only. Add vfp back to TUNE_FEATURES_tune-arm1136jfs. (From OE-Core rev: e0916a4e03d2ec101c4623b305f32607c0f566e2) Signed-off-by: Andre McCurdy <armccurdy@gmail.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* documentation.conf: Drop obsolete variable docsRichard Purdie2020-03-291-3/+0
| | | | | | | | | These fetcher *DIR variables were dropped a while back, drop the docs that reference them (thanks Robert Day). (From OE-Core rev: 609fcfe1f1490e9d9c35e40a0606a3b6b86bd78c) Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* security_flags.inc: fix flags missing from SDK toolchainTom Hochstein2020-03-251-0/+2
| | | | | | | | | | | | | The security flags were missing from the SDK toolchain because they were added specifically to class-target. Add them to class-cross-canadian as well (since the SDK environment file is created from cross-canadian target flags). (From OE-Core rev: cd46e8f890069a40d1e9048cfa0f378dec1dc5e9) Signed-off-by: Tom Hochstein <tom.hochstein@nxp.com> Signed-off-by: Antoine Manache <a.manache@gmail.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* layer.conf: Allow compatibility with zeus for nowRichard Purdie2020-03-151-1/+1
| | | | | | (From OE-Core rev: 1970c5f7838ff10cd6243e1624553bdc46e89fad) Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* layer.conf: Update to LAYERSERIES_CORENAME to dunfellRichard Purdie2020-03-151-2/+2
| | | | | | | | Update the layer core name to the new release name. (From OE-Core rev: 090bb3b44ba0cc01c29942c00d43e910d1ff735e) Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* gcc: Upgrade to 9.3 bugfix releaseKhem Raj2020-03-131-1/+1
| | | | | | | | | | | | This brings ~157 bugfixes [1] to gcc-9 with no features Drop backports which are already part of the release now [1] https://gcc.gnu.org/bugzilla/buglist.cgi?bug_status=RESOLVED&list_id=260610&resolution=FIXED&target_milestone=9.3 (From OE-Core rev: caf80e4e245132bdc3bbe219b567013f2c5d2f46) Signed-off-by: Khem Raj <raj.khem@gmail.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* nspr: Move to meta-oeAdrian Bunk2020-03-111-1/+0
| | | | | | | | | It was used only by nss. (From OE-Core rev: baecda5b32b66d09dadccbcbe706c5ec0a270568) Signed-off-by: Adrian Bunk <bunk@stusta.de> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* nss: Move to meta-oeAdrian Bunk2020-03-111-1/+0
| | | | | | | | | rpm was the last user in OE-core. (From OE-Core rev: 15aa3bdf798b0e45a20f877e203f3750b623754f) Signed-off-by: Adrian Bunk <bunk@stusta.de> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* ptest-packagelists.inc: add coreutils to SLOWTrevor Gamblin2020-03-111-0/+1
| | | | | | | (From OE-Core rev: 0c2c798164da283b79d396b1e50aedee9b6e70d6) Signed-off-by: Trevor Gamblin <trevor.gamblin@windriver.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* qemuarm64: Add -machine gic-version=3 with kvmKhem Raj2020-03-081-1/+1
| | | | | | | | | | | | | | | | qemuarm64 on aarch64 host errors out when using kvm qemu-system-aarch64: PMU: KVM_SET_DEVICE_ATTR: Invalid argument qemu-system-aarch64: failed to set irq for PMU Aborted machines with GICv3 that don’t support GICv2 guests you must have ‘-machine gic-version=3’ on the QEMU command line. (From OE-Core rev: 17e93c6464184d137b9590f17bfa879ae79d0cfc) Signed-off-by: Khem Raj <raj.khem@gmail.com> Cc: Jon Mason <jdmason@kudzu.us> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* babeltrace2: added first version, 2.0.1Anders Wallin2020-03-063-0/+3
| | | | | | | | | | | | | | | | | Babeltrace 1 vs. Babeltrace 2 The Babeltrace project exists since 2010. In 2020, Babeltrace 2 was released. Babeltrace 2 is a complete rewrite of the library, Python bindings, and CLI. It is plugin based and offers much more features and potential than Babeltrace 1. Because Babeltrace 2 is still a young released project, some distributions still provide packages for the Babeltrace 1 project. Both projects can coexist on the same system as there are no common installed files. (From OE-Core rev: be52889ba5e5a2cf02f50b3f3acee8ca72ec494d) Signed-off-by: Anders Wallin <wallinux@gmail.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* bitbake.conf: omit XZ threads and RAM from sstate signaturesAndré Draszik2020-03-061-1/+4
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | The number of threads used, and the amount of memory allowed to be used, should not affect sstate signatures, as they don't affect the outcome of the compression if xz operates in multi-threaded mode [1]. Otherwise, it becomes impossible to re-use sstate from automated builders on developer's machines (as the former might execute bitbake with certain constraints different compared to developer's machines). This is in particular a problem with the opkg package writing backend, as the OPKGBUILDCMD depends on XZ_DEFAULTS. Without the vardepexclude, there is no re-use possible of the package_write_ipk sstate. Whitelist the maximum number of threads and the memory limit given assumptions outlined in [2] below. (From OE-Core rev: 7927d5f6eaab48578b23db9a4c38e2f87f011353) Signed-off-by: André Draszik <git@andred.net> [1] When starting out in multi-threaded mode, the output is always deterministic, as even if xz scales down to single-threaded later, the archives are still split into blocks and size information is still added, thus keeping them compatible with multi-threaded mode. Also, when starting out in multi-threaded mode, xz never scales down the compression level to accomodate memory usage restrictions, it just scales down the number of threads and errors out if it can not accomodate the memory limit. [2] Assumptions * We only support multi-threaded mode (threads >= 2), builds should not try to use xz in single-threaded mode * The thread limit should be set via XZ_THREADS, not via modifying XZ_DEFAULTS or XZ_OPTS, or any other way * The thread limit should not be set to xz's magic value zero (0), as that will lead to single-threaded mode on single-core systems. Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* bitbake.conf: more deterministic xz compression (threads)André Draszik2020-03-061-1/+1
| | | | | | | | | | | | | | | | | | | | | | | | | | xz archives can be non-deterministic / non-reproducible: a) archives are created differently in single- vs multi-threaded modes b) xz will scale down the compression level so as to be try to work within any memory limit given to it when operating in single-threaded mode This means that due to bitbake's default of using as many threads as there are cores in the system, files compressed with xz will be different if built on a multi-core system compared to single-core systems. They will also potentially be different if built on single-core systems with different amounts of physical memory, due to bitbake's default of limiting xz's memory consumption. Force multi-threaded operation by default, even on single-core systems, so as to ensure archives are created in the same way in all cases. (From OE-Core rev: d96aa8594c8d7531da34645cadbac4f7549d8ae6) Signed-off-by: André Draszik <git@andred.net> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* tcmode-default: Add wildcard to GLIBCVERSIONKhem Raj2020-03-011-1/+1
| | | | | | | | | glibc version has moved on to 2.31.x (From OE-Core rev: ef681222a918030d726a79cf04111fb5d0b66355) Signed-off-by: Khem Raj <raj.khem@gmail.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* yocto-uninative.inc: version 2.8 updates glibc to 2.31Michael Halstead2020-02-291-5/+5
| | | | | | | | Allow sstate use in Tumbleweed and other distros as they update glibc. (From OE-Core rev: ccb374c279b260b1fd3460f6bfd1567240816055) Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* maintainers.inc: add self for atk, at-spi2-core, at-spi2-atkTim Orling2020-02-281-3/+3
| | | | | | | | | | For GUI automation purposes, strong motivation for accessibility (a11y) via python3-dogtail and python3-pyatspi2, so taking over from Anuj. (From OE-Core rev: fb0a7ab133434febc78ce4f4d00f1192935ad95e) Signed-off-by: Tim Orling <timothy.t.orling@linux.intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* go: Update to 1.14 release seriesKhem Raj2020-02-281-1/+1
| | | | | | | (From OE-Core rev: 3daa9684e458b9c926e1a07acd9b1c0fe8bd2e86) Signed-off-by: Khem Raj <raj.khem@gmail.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* tune-cortexa72-cortexa53.inc: Adding missing TUNE_FEATURESJaewon Lee2020-02-281-2/+2
| | | | | | | | | | | | | | | | Without the proper default tune in TUNE_FEATURES, certain variables won't expand correctly. MACHINEOVERRIDES won't add cortexa72-cortexa53: TUNE_CCARGS won't add -mtune=cortexa72.cortexa-53, generating the toolchain incorrectly. Adding missing 'cortexa72-cortexa53' to both TUNE_FEATURES_tune-cortexa72-cortexa53 and TUNE_FEATURES_tune-cortexa72-cortexa53-crypto (From OE-Core rev: eee65bed5ee39051541a0a3f2a311396d6e7326c) Signed-off-by: Jaewon Lee <jaewon.lee@xilinx.com> Signed-off-by: Alejandro Enedino Hernandez Samaniego <alejandr@xilinx.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* layer.conf: Consider shared-mime-info and desktop-file-utils siggen safeKhem Raj2020-02-281-0/+2
| | | | | | | | | | | | | | These are added as dependencies by mime class, which could be inherited along with allarch and dependencies silently go into target specific recipes and which then can result in sstate hash signature mismatches when the allarch recipes are reused for another arch [YOCTO #13805] (From OE-Core rev: 510015ac81df969f690d6c8661b00bebe73b7fca) Signed-off-by: Khem Raj <raj.khem@gmail.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* hosttools: add utilities for all supported checksumsBartosz Golaszewski2020-02-281-1/+2
| | | | | | | | | | | Only md5sum and sha256sum are currently provided by HOSTTOOLS. Trying to use any other checksum conversion will result in a build failure. Fix it by adding other supported checksum utilities to HOSTTOOLS. (From OE-Core rev: 78155e5fcff9362049b576d20e31c3519c48485b) Signed-off-by: Bartosz Golaszewski <bgolaszewski@baylibre.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* abi_version/sstatesig: Introduce HASHEQUIV_HASH_VERSIONRichard Purdie2020-02-281-0/+8
| | | | | | | | | | We've found we need a way to cause a change in signatures and move to a new hash 'namespace' with hashequiv. This introduces a variable which allows us to do this. (From OE-Core rev: 1c2d5aeae2fa2dfc16bc60b6cf0b310f826337fd) Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* wayland: add ptestAlexander Kanavin2020-02-251-0/+1
| | | | | | | | | | | | | | | | | | | | Sadly, meson makes it very difficult to install tests: the test configuration is written into host-specific binary files, which can't be transferred to the target. (unlike autotools where at least everything happens via Makefiles which can be patched and tweaked via sed and env vars) So the configuration has to be entirely recreated in shell. I managed this for wayland, but weston proved too difficult. I had filed bugs asking upstream to make the tests installable: https://gitlab.freedesktop.org/wayland/wayland/issues/146 https://gitlab.freedesktop.org/wayland/weston/issues/368 (From OE-Core rev: 296ee10bb8491278f050fb9d55f42b0bcf663382) Signed-off-by: Alexander Kanavin <alex.kanavin@gmail.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* libidn: Move to meta-oeAdrian Bunk2020-02-251-1/+0
| | | | | | | | | There are no users left in OE-core. (From OE-Core rev: 2c5d140a8a2b794b36ed9535afc278cec2ef306f) Signed-off-by: Adrian Bunk <bunk@stusta.de> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* mdadm: drop from PTESTS_SLOWAlexander Kanavin2020-02-231-1/+1
| | | | | | | | | | | | | | | | | | | | | | | There are two primary reasons for this: 1. mdadm test suite tends to work like this do_action sleep arbitrary_amount check_result This is unreliable, and arbitrary_amount may or may not be enough. I have confirmed this by increasing the amount, and seeing more tests pass than before. 2. The test suite aborts half way through because one of the mdadm binaries segfaults. This indicates that upstream isn't actually running the suite anymore, and in this situation we shouldn't be relying on it either. (From OE-Core rev: e21021dc00ec76c76cc361e15bc83a89083c9e72) Signed-off-by: Alexander Kanavin <alex.kanavin@gmail.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* binutils: Upgrade to 2.34 releaseKhem Raj2020-02-221-1/+1
| | | | | | | | | | | | | | | | | | | | | | | | | | Details of changelog [1] Removing bfd/ld patch to enable PE targets, instead use specific emulations via --enable-targets for x86_64 Re-arrange/forward-port patches and upgrade libctf configure to libtool 2.4 patch rpaths are no longer emitted into elfedit/readelf therefore no need of chrpath anymore Instead of pre-generating configure scripts and house them in libtool patch, generate them during configure. This also ensures that we do not patch configure directly but rather the sources which generate it Package newly added libctf library [1] https://lists.gnu.org/archive/html/info-gnu/2020-02/msg00000.html (From OE-Core rev: 82f7d5cfc2ab02f39b69c0f8697d660936422d4a) Signed-off-by: Khem Raj <raj.khem@gmail.com> Cc: Christopher Clark <christopher.clark6@baesystems.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-10 18:04:38 +0000