summaryrefslogtreecommitdiffstats
path: root/meta/recipes-core/meta
Commit message (Collapse)AuthorAgeFilesLines
* testexport: Fix to work as an image classRichard Purdie2022-08-121-1/+1
| | | | | | | | | | The class is mainly an image based class but one recipe does need to look at values shared with the class and isn't an image. Move this to a conf file instead, avoiding the need to pollute all recipes globally. (From OE-Core rev: ed4238487c81b3580e83c257b50745a832a6e717) Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* wic: depend on cross-binutilsRoss Burton2022-08-021-0/+1
| | | | | | | | | | | Wic can build an unified kernel image, but this needs the cross-objcopy from binutils. (From OE-Core rev: 7c7a488116f49083ca42d3628ebc0870585110c3) Signed-off-by: Ross Burton <ross.burton@arm.com> Signed-off-by: Luca Ceresoli <luca.ceresoli@bootlin.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* meta-ide-support: adjust to provide (e)SDK experience directly in a yocto buildAlexander Kanavin2022-07-281-3/+23
| | | | | | | | | | | | | | | | | Specifically: 1. Add a few more toolchain items to DEPENDS so they're available in the recipe sysroot. 2. Use deploy mechanism to place the SDK environment setup file and testdata for testing it into the image deploy directory. 3. Add ability to run SDK tests via the testsdk class and task. This also requires providing a testdata json file. 4. Ensure sysroot population always runs, as those items are mean to be picked up by 'bitbake build-sysroots' into the unified sysroot. (From OE-Core rev: 93f419451cc18b5d31b6fe134ca52a2750fa567d) Signed-off-by: Alexander Kanavin <alex@linutronix.de> Signed-off-by: Alexandre Belloni <alexandre.belloni@bootlin.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* signing-keys: fix RDEPENDS to signing-keys-devFederico Pellegrin2022-06-211-0/+2
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | Specific provider (ie. RPM or IPK) does "provide" just itself as a package to the system. This will cause the "-dev" package, which refers to the generic signing-keys and not the provider specific, to miss the dependency. Error case (RPM) when populating sdk: Error: Problem: conflicting requests - nothing provides signing-keys = 1.0-r0 needed by signing-keys-dev-1.0-r0.noarch (try to add '--skip-broken' to skip uninstallable packages) Examining signing-keys-rpm packages in PROVIDES we have indeed: signing-keys-rpm = 1.0-r0 But in signing-keys-dev: in REQUIRES: signing-keys-1.0-r0 This MR will fix the situation by removing the RDEPENDS for the -dev package (From OE-Core rev: ecdba906c3c8bc21e33b4a2651a762c40487149b) Signed-off-by: Federico Pellegrin <fede@evolware.org> Signed-off-by: Luca Ceresoli <luca.ceresoli@bootlin.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* cve-update-db-native: make it possible to disable database updatesMarta Rybczynska2022-06-061-2/+4
| | | | | | | | | | | | | | | Make it possible to disable the database update completely by using a negative update interval CVE_DB_UPDATE_INTERVAL. Disabling the update is useful when running multiple parallel builds when we want to have a control on the database version. This allows coherent cve-check results without an database update for only some of the builds. (From OE-Core rev: b5c2269240327c2a8f93b9e55354698f52c976f3) Signed-off-by: Marta Rybczynska <marta.rybczynska@huawei.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* cve-update-db-native: let the user to drive the update intervalMarta Rybczynska2022-05-031-1/+9
| | | | | | | | | | | | | Add a new variable CVE_DB_UPDATE_INTERVAL allowing the user to set the database update interval. - a positive value sets an interval (in seconds) - a zero ("0") forces the database update (From OE-Core rev: fe7bc6f16184d5ebdb1dd914b6dcb75c9e5e0c9c) Signed-off-by: Marta Rybczynska <marta.rybczynska@huawei.com> Signed-off-by: Luca Ceresoli <luca.ceresoli@bootlin.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* cve-update-db-native: update the CVE database once a day onlyMarta Rybczynska2022-05-031-2/+2
| | | | | | | | | | | | | | | | The update of the NVD database was expected to happen once per hour. However, the database file date changes only if the content was actually updated. In practice, the check worked for the first hour after the new download. As the NVD database changes usually only once a day, we can just update it less frequently. (From OE-Core rev: 35bccdedadeaba820d58b69fe74ce5e4c1f577e3) Signed-off-by: Marta Rybczynska <marta.rybczynska@huawei.com> Signed-off-by: Luca Ceresoli <luca.ceresoli@bootlin.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* wic: Add dependencies for erofs-utilsSean Anderson2022-04-271-1/+1
| | | | | | | | | | | | In order to build erofs filesystems, wic must have the erofs-utils package installed into its sysroot. Fixes: 30375ce97 ("Add support for erofs filesystems") (From OE-Core rev: 68e364340c439a1341d37c3f7a2b0e6aad8e1e56) Signed-off-by: Sean Anderson <sean.anderson@seco.com> Signed-off-by: Luca Ceresoli <luca.ceresoli@bootlin.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* buildtools: Add standalone make tarballRichard Purdie2022-04-191-0/+15
| | | | | | | | | Some versions of make have bugs. Add a way to provide a make tarball that can be used on it's own in these cases. (From OE-Core rev: 4f1f6743fa252405075192633e19b9d2b03b7303) Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* buildtools-tarball: Only add cert envvars if certs are includedRichard Purdie2022-04-191-2/+4
| | | | | | | | | Users may or may not include the certificates in buildtools. Only set the appropriate variables if they're present. (From OE-Core rev: 0945a2a5d7c41af22e222a116aafacb4beee54d2) Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* buildtools-tarball: include nativesdk-python3-pyyamlRoss Burton2022-04-011-3/+2
| | | | | | | | | | | | | BitBake can optionally 'import yaml' if BB_LOGCONFIG specifies a yaml file. This is a 3rd party module, so that this works out of the box when buildtools is used -- either explicitly via buildtools-tarball or implicitly via eSDK -- we can add pyyaml to the buildtools. (From OE-Core rev: 6be90f884bb3fc87d9aa21cb882a835d6bc583a9) Signed-off-by: Ross Burton <ross.burton@arm.com> Signed-off-by: Alexandre Belloni <alexandre.belloni@bootlin.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* buildtools-docs-tarball: Add test for building documentation using sphinxRichard Purdie2022-03-182-2/+7
| | | | | | (From OE-Core rev: 26b224a1bbe27b5d9886be4552147e1d66e34519) Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* Add buildtools-docs-tarball recipeRichard Purdie2022-03-181-0/+16
| | | | | | (From OE-Core rev: 4f691a4ecd02dd588158b28e57f5a58a42beffea) Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* meta/scripts: Automated conversion of OE renamed variablesRichard Purdie2022-02-211-1/+1
| | | | | | (From OE-Core rev: aa52af4518604b5bf13f3c5e885113bf868d6c81) Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* meta/scripts: Change BB_ENV_EXTRA_WHITE -> BB_ENV_PASSTHROUGH_ADDITIONSRichard Purdie2022-02-212-4/+4
| | | | | | | | After the change to bitbake, update the references in OE-Core to match the updates. (From OE-Core rev: 193affb9f28b0116c3fd619834f145326fee08c5) Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* buildtools: Allow testsdk to access the networkRichard Purdie2022-02-121-0/+1
| | | | | | | | Some of the buildtools tests test network access so allow this. (From OE-Core rev: c47424b8e71b95e60f4c5f343176825082b53896) Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* buildtools-tarball/uninative-tarball/meta-ide-support: Drop useless meta classRichard Purdie2021-09-234-4/+1
| | | | | | | | | | | | The class adds an emtpy PACKAGES setting but most code now uses the nopackages class which is much clearer. It also adds recursive do_build dependencies which don't really serve any useful purpose any more. Simplify the code and drop the class use. (From OE-Core rev: 030d56e2e8ece93472adc51fe467221d846c9ac0) Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* siteinfo/autotools: Ensure task checksums reflect site filesRichard Purdie2021-09-232-0/+11
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | Currently, if you change the site files, nothing rebuilds since they are not accounted for in task checksums. They could/should be through the file-checksums task flag. We need to cache all the files looked for, whether the exist or not so that if they do exist and didn't, the checksum also changes. This gets complicated by the need to clean out hardcoded build paths from the variable and that other layers can have site files. This patch adds this functionality. A new variable, SITEINFO_PATHVARS is added which controls which substitutions to make on the file-checksum values to remove the hardcoded paths. Layers adding site files will need to set this to a variable that has the layer path in it and is excluded from task hashes (COREBASE is the one the core layer uses). This patch will cause yocto-check-layer to fail for some layers where site files are added yet the layer isn't a machine specific layer. This is arguable correct since these additional site files apply to all recipes and things from a layer like core could be changed by such changes so it is right they should rebuild. There is a determinism issue potentially there if not. meta-openembedded does have some such references but looking at them they should move to core or likely just be removed as most look obsolete anyway. [YOCTO #13729] (From OE-Core rev: 29daffc2410f06f36b779d5bf1fd1ef6e900ca8f) Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* buildtools-tarball: add testsdk taskRoss Burton2021-08-121-0/+13
| | | | | | | | | | | Add a testsdk task, which is essentially the same as testsdk.bbclass but the test case directory is changed. This lets us exercise the buildtools tarballs at build time. (From OE-Core rev: 39a0e45ced42826832f84cfbf1cf50ed7c334997) Signed-off-by: Ross Burton <ross.burton@arm.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* Convert to new override syntaxRichard Purdie2021-08-028-19/+19
| | | | | | | | | | | | This is the result of automated script conversion: scripts/contrib/convert-overrides.py <oe-core directory> converting the metadata to use ":" as the override character instead of "_". (From OE-Core rev: 42344347be29f0997cc2f7636d9603b1fe1875ae) Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* buildtools-tarball: Add lz4 and ztsd (including pzstd)Richard Purdie2021-07-201-0/+2
| | | | | | | | | Since we start to require these for builds, we need to include them in buildtools-tarball so that older systems can access them easily. (From OE-Core rev: a9ab105b881215653e08d442786e6a3aff84c8ba) Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* cve-update-db-native: skip on empty cpe23UriKonrad Weihmann2021-04-231-1/+6
| | | | | | | | | | | | | | Recently an entry in the NVD DB appeared that looks like that {'vulnerable': True, 'cpe_name': []}. As besides all the vulnerable flag no data is present we would get a KeyError exception on acccess. Use get method on dictionary and return if no meta data is present Also quit if the length of the array after splitting is less than 6 (From OE-Core rev: 00ce2796d97de2bc376b038d0ea7969088791d34) Signed-off-by: Konrad Weihmann <kweihmann@outlook.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* cve-update-db-native: Allow to overrule the URL in a bbappend.jan2021-03-311-2/+3
| | | | | | | | | | With this small patch, it's possible to overrule the public URL with a local mirror for those without Internet access. (From OE-Core rev: 2d903126e8bbece3a5171c3488c3deae1f0aa3ee) Signed-off-by: Jan Vermaete <jan.vermaete@gmail.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* cve-update-db-native: consider version suffix when update CVE dbLee Chee Yang2021-03-201-1/+6
| | | | | | | | | | | | | | | some record from NVD can merge or split suffix from version, for example: CVE-2017-15906 "cpe23Uri" : "cpe:2.3:a:openbsd:openssh:5.0:p1:*:*:*:*:*:*" "cpe23Uri" : "cpe:2.3:a:openbsd:openssh:4.7p1:*:*:*:*:*:*:*" in such case include the suffix into version when update local CVE db. (From OE-Core rev: 13cc68197f81bb7c76fa1abecc5dd720b8bdb8d5) Signed-off-by: Lee Chee Yang <chee.yang.lee@intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* uninative-tarball: Add a dependency on nativesdk-glibc-dbgPeter Kjellerstedt2021-03-141-0/+1
| | | | | | | | | | | This adds the debug symbols for the binaries included in the uninative tar ball. These are needed if one wants to run valgrind on a native binary when uninative is used. Or get complete backtraces using gdb. (From OE-Core rev: 13775feac21f0df50d4b3db19f6c79f10cf397f5) Signed-off-by: Peter Kjellerstedt <peter.kjellerstedt@axis.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* buildtools-extended-tarball: Add glibc-gconvs needed for buildRichard Purdie2021-02-161-0/+10
| | | | | | | | | | | | When building vim it tries to rebuild files using iconv. If this fails the build continues anyway but the output is not determnistic as builds using a hosttools tarball are different from builds where there isn't a hosttools tarball. Add the needed gconvs to the tarball when iconv is present to become determistic and generate vim locales consistently. (From OE-Core rev: b945652a088f430a2adec6b968cd00c5928d4272) Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* nativesdk-buildtools-perl-dummy: Add new autoconf dependenciesRichard Purdie2021-02-131-0/+3
| | | | | | | | | When used in SDKs we need to provide the perl modules used by autoconf. Add new ones needed by recent changes. (From OE-Core rev: b548c2f4d1d88f80d713551a408064d4f5ff3d7f) Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* nativesdk-buildtools-perl-dummy: Add missing entries for nativesdk-automakeRichard Purdie2021-01-291-0/+3
| | | | | | | | | This allows the hardcoded nativesdk dependency hacking in the automake recipe to be dropped and matches what autoconf is doing. (From OE-Core rev: c723866a6834b8fa89b036a627f619a0c391a662) Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* wic-tools: add grub-efi and systemd-boot on arm64Ross Burton2020-12-181-0/+1
| | | | | | | | | These both now work on arm64, so add them to the dependencies. (From OE-Core rev: 6b350db4ef9eaff10ee274ff7d28d2e6761c532a) Signed-off-by: Ross Burton <ross.burton@arm.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* wic-tools: don't build syslinux-native for targets without syslinuxRoss Burton2020-12-181-4/+4
| | | | | | | | | | If we're not building syslinux, then there's no point building syslinux-native. (From OE-Core rev: 152dbd05c099ce50701466336a9c9642c98e4fe0) Signed-off-by: Ross Burton <ross.burton@arm.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* buildtools-tarball.bb: Fix PATH for environment setup scriptRobert Yang2020-12-151-1/+1
| | | | | | | | | | | | It only added ${SDKPATHNATIVE}/usr/bin to PATH which didn't work when files were installed to other bin dirs such as /bin or /sbin, for example, nativesdk-pigz installs the files to /bin, now fix it to keep align with sdk's PATH. (From OE-Core rev: 67cac575a5696af5bad1aab888b65ea2686adff7) Signed-off-by: Robert Yang <liezhi.yang@windriver.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* buildtools-tarball: add wic dependency into extended buildtoolsChangqing Li2020-12-031-0/+3
| | | | | | | | | | | | | | | | | | | fix below error: wic ls ./core-image-minimal-intel-x86-64.wic ERROR: Can't find executable parted wic depend on some tools like parted/mtools/..., and we have those tools in native_sysroot. so above problem can be avoided by run command like wic ls imagename.wic --native-sysroot <path> but this cannot cover condition that usr don't have build the image, the image just copy from somewhere. (From OE-Core rev: c0eda6ec09395f3a04cb80107a3ca33a063b21f8) Signed-off-by: Changqing Li <changqing.li@windriver.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* cve-update-db-native: handle all-wildcard versionsRoss Burton2020-11-291-1/+6
| | | | | | | | | | | If a CPE version field is just *:*:*:* it should be handled the same as -:*:*:*, that is 'all versions'. To ease handling, transform this case to use -. (From OE-Core rev: 04a9bc4ca5294fe6834513669c7746a824d12b04) Signed-off-by: Ross Burton <ross.burton@arm.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* buildtools-tarball: Fix conflicts with oe-selftest and other toolingRichard Purdie2020-09-231-0/+3
| | | | | | | | | | | | OECORE_NATIVE_SYSROOT is used by tools like oe-run-native and hence we were seeing selftest failures when newer buildtools-tarballs that use this were run on the autobuilder. Unset the variable after use to avoid these issues. (From OE-Core rev: ea5128fde10eb9be7fefbbb87ae6181edd2bcdff) Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* buildtools-tarball: Add python3-jinja2Richard Purdie2020-09-211-0/+1
| | | | | | | | | | | | This is used by various pieces of the result handling code, particularly the performance testing and we're seeing autobuilder failures that are easiest resolved using this. Acked-by: Tim Orling <ticotimo@gmail.com> (From OE-Core rev: e86a07e7105fd1cc4fd3e5aa22ff07aca6e960d7) Signed-off-by: Tim Orling <ticotimo@gmail.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* cve-update-db-native: remove unused variableChris Laplante2020-09-151-1/+0
| | | | | | | (From OE-Core rev: 790f8a5bfbd1851226fa5fc5b09e79f6396e747d) Signed-off-by: Chris Laplante <chris.laplante@agilent.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* cve-update-db-native: move -journal checking into do_fetchChris Laplante2020-09-151-6/+8
| | | | | | | | | | | It was always questionable to do this in an anonymous function, but now with multiconfig it is a critical mistake and leads to more strange "Exception: sqlite3.OperationalError: disk I/O error" errors. (From OE-Core rev: fcbc9d0e8421a3a559db05005ba042337cd5d864) Signed-off-by: Chris Laplante <chris.laplante@agilent.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* cve-update-db-native: be less magical about checking whether the cve-check ↵Chris Laplante2020-09-151-2/+1
| | | | | | | | | class is enabled (From OE-Core rev: cbc717350b21fb417fa6f83621022ac633a26124) Signed-off-by: Chris Laplante <chris.laplante@agilent.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* cve-update-db-native: use fetch taskRoss Burton2020-09-121-4/+5
| | | | | | | | | | Instead of inventing a new task to fetch the CVE data, use the existing fetch task. (From OE-Core rev: f5f97d33a1703d75b9fd9760f2c7767081538e00) Signed-off-by: Ross Burton <ross.burton@arm.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* cve-update-db-native: add more logging when fetchingRoss Burton2020-09-121-1/+5
| | | | | | | | | Add some debug logging when fetching the CVE data. (From OE-Core rev: 9b230584664873af2ab453b8153b1ad276d3b0af) Signed-off-by: Ross Burton <ross.burton@arm.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* cve-update-db-native: remove unused importRoss Burton2020-09-121-1/+1
| | | | | | | | | This import isn't used anymore, so remove it. (From OE-Core rev: d4f0e43bdf1de972e95869f033dd45f8d420c400) Signed-off-by: Ross Burton <ross.burton@arm.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* cve-update-db-native: use context manager for cve_fChris Laplante2020-09-101-4/+1
| | | | | | (From OE-Core rev: ff422652e1b5db62205fafc75ce56bb5951d478d) Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* cve-check/cve-update-db-native: use lockfile to fix usage under multiconfigChris Laplante2020-09-101-2/+3
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | Previously CVE_CHECK_DB_FILE / CVE_CHECK_DB_DIR was the same across multiconfigs which led to a race condition wherein multiple cve-update-db-native:do_populate_cve_db tasks could attempt to write to the same sqlite database. This led to the following task failure: Error executing a python function in exec_python_func() autogenerated: The stack trace of python calls that resulted in this exception/failure was: File: 'exec_python_func() autogenerated', lineno: 2, function: <module> 0001: *** 0002:do_populate_cve_db(d) 0003: File: '/mnt/data/agent/work/74f119cccb44f133/yocto/sources/poky/meta/recipes-core/meta/cve-update-db-native.bb', lineno: 103, function: do_populate_cve_db 0099: if year == date.today().year: 0100: cve_f.write('CVE database update : %s\n\n' % date.today()) 0101: 0102: cve_f.close() *** 0103: conn.commit() 0104: conn.close() 0105:} 0106: 0107:def initialize_db(c): Exception: sqlite3.OperationalError: disk I/O error Use a lockfile to ensure multiple tasks don't step over each other. (From OE-Core rev: 24e9380643a2ae3fcae193519cb64aedaf682153) Signed-off-by: Chris Laplante <chris.laplante@agilent.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* cve-update-db-native: add progress handlerChris Laplante2020-09-101-43/+47
| | | | | | | (From OE-Core rev: 79ae2e82b8ec11578177f428060b568d6c7d44ca) Signed-off-by: Chris Laplante <chris.laplante@agilent.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* nativesdk-sdk-provides-dummy: Add /bin/shRichard Purdie2020-08-224-2/+4
| | | | | | | | | | | | | | By doing this we can revert b18c32ab6bc9c4f1953e9f79aa39bc92d1c4e30d which was a pretty ugly hack anyway and now means the different providers are all being handled consistently. Anyone with SDK recipes will need to ensure nativesdk-sdk-provides-dummy is included in those builds (or an equivalent). This is a good thing to do anyway. (From OE-Core rev: dd2c603befdd65c92c6196d5b103568249766b3e) Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* buildtools: Handle generic environment setup injectionRichard Purdie2020-08-081-8/+11
| | | | | | | | | | | | | | | Currently buildtools has its own hacked environment setup. We added capability for generic script fragements but this code was never updated to use it even if several components it contains needs it. Remove a hardcoded variable in favour of the generic scripts to avoid bugs in this area in future. The others should probably be migrated to environment files in future too but there isn't such a file for those at present. (From OE-Core rev: eb210cee4bd71614dd108027e6d5aa8f8d451b27) Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* cve-update: handle baseMetricV2 as optionalKonrad Weihmann2020-07-271-4/+9
| | | | | | | | | | | Currently in NVD DB an item popped up, which hasn't set baseMetricV2. Let the parser handle it as an optional item. In case use baseMetricV2 before baseMetricV3 (From OE-Core rev: fdcbf3f28289188c5a97664d1421d4a5c4991eda) Signed-off-by: Konrad Weihmann <kweihmann@outlook.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* deploy.bbclass: Clean DEPLOYDIR before do_deployDaniel Klauer2020-06-301-2/+0
| | | | | | | | | | | | | | | | | | | | | | do_deploy should clean up ${DEPLOYDIR} before running, just like do_install cleans up ${D} before running. This reduces the risk of DEPLOYDIR being accidentally contaminated by files from previous runs, possibly even with different config, in case of incremental builds. It is convenient to have this in deploy.bbclass, so it doesn't have to be duplicated in every recipe, considering for example meta-freescale, which has 23 affected recipes. All recipes using deploy.bbclass (grep -r 'inherit .*deploy') in poky, meta-openembedded and meta-freescale look like they either benefit from this or are at least not affected negatively by it. The only exception I've noticed was uboot-sign.bbclass, which was however fixed by the previous patch. (From OE-Core rev: 7083a7d56f4d90c81d2e6652ee291d20fd908bbe) Signed-off-by: Daniel Klauer <daniel.klauer@gin.de> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* grub: Remove native version of grub-efiJacob Kroon2020-06-231-1/+1
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | The native version of grub-efi only installs the tools /usr/bin/grub-editenv /usr/bin/grub-mkimage to sysroots-components/, but equivalent tools are already provided by grub-native, the difference on x86_64 being 4 hardwired paths in grub-mkimage (values taken from grub-native): LOCALEDIR = $TMPDIR/work/x86_64-linux/grub-native/2.04-r0/recipe-sysroot-native/usr/share/locale GRUB_DATADIR = $TMPDIR/work/x86_64-linux/grub-native/2.04-r0/recipe-sysroot-native/usr/share GRUB_LIBDIR = $TMPDIR/work/x86_64-linux/grub-native/2.04-r0/recipe-sysroot-native/usr/lib GRUB_SYSCONFDIR = $TMPDIR/work/x86_64-linux/grub-native/2.04-r0/recipe-sysroot-native/etc If grub-native and grub-efi-native are built with the following patch --- grub-2.04.orig/configure.ac +++ grub-2.04/configure.ac @@ -1980,10 +1980,10 @@ grub_libdir="$(eval echo "$libdir")" grub_localedir="$(eval echo "$localedir")" grub_datadir="$(eval echo "$datadir")" grub_sysconfdir="$(eval echo "$sysconfdir")" -AC_DEFINE_UNQUOTED(LOCALEDIR, "$grub_localedir", [Locale dir]) -AC_DEFINE_UNQUOTED(GRUB_LIBDIR, "$grub_libdir", [Library dir]) -AC_DEFINE_UNQUOTED(GRUB_DATADIR, "$grub_datadir", [Data dir]) -AC_DEFINE_UNQUOTED(GRUB_SYSCONFDIR, "$grub_sysconfdir", [Configuration dir]) +AC_DEFINE_UNQUOTED(LOCALEDIR, "/non-existent", [Locale dir]) +AC_DEFINE_UNQUOTED(GRUB_LIBDIR, "/non-existent", [Library dir]) +AC_DEFINE_UNQUOTED(GRUB_DATADIR, "/non-existent", [Data dir]) +AC_DEFINE_UNQUOTED(GRUB_SYSCONFDIR, "/non-existent", [Configuration dir]) the produced grub-editenv/grub-mkimage binaries become binary equivalent, assuming reproducible builds is active. Since the unpatched values of LOCALEDIR/GRUB_DATADIR/GRUB_LIBDIR/GRUB_SYSCONFDIR point to directories that are not expected to exist at runtime, they can be ignored. Therefore: * remove grub-efi-native and instead rely on the same tools from grub-native * replace references to grub-efi-native with grub-native * remove unused grub-efi-native security flags overrides (From OE-Core rev: 7044181df7487f047d175242f7ebbc3c35bf5402) Signed-off-by: Jacob Kroon <jacob.kroon@gmail.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* buildtools-tarball: export OPENSSL_CONF in environment setupSteve Sakoman2020-06-151-0/+1
| | | | | | | | | | | The autobuilder has been experiencing SSL: CERTIFICATE_VERIFY_FAILED errors during error report uploads when using buildtools due to looking for certs in /opt/poky (From OE-Core rev: 197f1d5d14b8e57295f5a81c03c86abba5328614) Signed-off-by: Steve Sakoman <steve@sakoman.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
generated by cgit v1.2.3-54-g00ecf (git 2.39.0) at 2024-07-01 22:02:50 +0000