summaryrefslogtreecommitdiffstats
Commit message (Collapse)AuthorAgeFilesLines
...
* wic: don't forcibly pass -T defaultRoss Burton2021-08-123-3/+3
| | | | | | | | | | | | | | This reverts part of oe-core eecbe62555, which was a previous attempt to solve the Y2038 problem. This is now solved centrally in e2fsprogs, so doesn't need to be dealt with in wic. We don't revert the commit entirely, to retain the warning if a filesystem has small inodes. (From OE-Core rev: 7e8017208bed98b6c90735cb641fc9d7aedf9140) Signed-off-by: Ross Burton <ross.burton@arm.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* e2fsprogs: ensure small images have 256-byte inodesRoss Burton2021-08-122-0/+23
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | e2fsprogs calls filesystems larger than 3MB but smaller than 512MB "small", which has some implications: - blocksize 1024 instead of 4096 - inode_ratio 4096 instead of 16384 - inode_size 128 instead of 256 The outcome of the inode size dropping to 128 bytes is that they cannot store 64-bit timestamps, so are not Y2038-safe. A previous attempt to solve this problem[1] changed some of the canned wic files to pass -T default to mkfs.ext4, but this only covered wic images and not traditional images. Also, actually small filesystems, for example a core-image-minimal, will happily be tens of megabytes and with the "default" options will result in an image which runs out of blocks before it runs out of space: mkfs.ext4: Could not allocate block in ext2 filesystem while populating file system Considering that many OpenEmbedded images are in fact "small", being 2038-safe is worth the marginal increase is disk usage. This patch alters the small configuration in native builds so that it also has 256-byte inodes. Target is unchanged so that standard behaviour is maintained outside of the build. This is actually the same underlying patch that Mathieu Dubois-Briand sent in April, but the wic change in [1] was accepted instead. I believe that is the wrong approach and this approach covers more cases. [ YOCTO #14478 ] [1] openembedded-core eecbe62 [2] https://lists.openembedded.org/g/openembedded-core/message/150298 (From OE-Core rev: 9ab0ae83a24ee99e69f8ac54256b253a122aef8a) Signed-off-by: Ross Burton <ross.burton@arm.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* MAINTAINERS: add overlayfs maintainerVyacheslav Yurkov2021-08-121-0/+1
| | | | | | | (From OE-Core rev: 8749556d06b07961080650ac17ee1c37666e01fd) Signed-off-by: Vyacheslav Yurkov <uvv.mail@gmail.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* oeqa/selftest: overlayfs unit testsVyacheslav Yurkov2021-08-121-0/+171
| | | | | | | | | Unit tests for overlayfs.bbclass (From OE-Core rev: b393e1982090063d9d0610fdcfd3601e78a501c0) Signed-off-by: Vyacheslav Yurkov <uvv.mail@gmail.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* overlayfs: meta-selftest recipeVyacheslav Yurkov2021-08-121-0/+17
| | | | | | | | | The recipe demonstrates example usage of overlayfs bbclass (From OE-Core rev: 1ad7a6fdd6382a30f1d9e115840ce8243b7fce2f) Signed-off-by: Vyacheslav Yurkov <uvv.mail@gmail.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* systemd-machine-units: add bbappend for meta-selftestVyacheslav Yurkov2021-08-121-0/+2
| | | | | | | (From OE-Core rev: 797ab6d3237c3248778ea3c9304e92dcc94a67da) Signed-off-by: Vyacheslav Yurkov <uvv.mail@gmail.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* rootfs-postcommands: add QA check for overlayfsVyacheslav Yurkov2021-08-121-0/+25
| | | | | | | | | | The check is conditional and only enabled when overlayfs is set in DISTRO_FEATURES (From OE-Core rev: 4734799bacf0a5d2487e1cde3ae1c00223b032b2) Signed-off-by: Vyacheslav Yurkov <uvv.mail@gmail.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* overlayfs.bbclass: generate overlayfs mount unitsVyacheslav Yurkov2021-08-121-0/+111
| | | | | | | | | | | | | | It's often desired in Embedded System design to have a read-only rootfs. But a lot of different applications might want to have a read-write access to some parts of a filesystem. It can be especially useful when your update mechanism overwrites the whole rootfs, but you want your application data to be preserved between updates. This class provides a way to achieve that by means of overlayfs and at the same time keeping the base rootfs read-only. (From OE-Core rev: 18377d6f09fc8855c71f2e5c097cbbbccf5632ce) Signed-off-by: Vyacheslav Yurkov <uvv.mail@gmail.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* lib/oe: add generic functions for overlayfsVyacheslav Yurkov2021-08-121-0/+43
| | | | | | | (From OE-Core rev: 53f0af20f94399335c8a5a6b7001994e332b69a6) Signed-off-by: Vyacheslav Yurkov <uvv.mail@gmail.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* cve-check: remove deprecated CVE_CHECK_CVE_WHITELISTMichael Opdenacker2021-08-121-3/+0
| | | | | | | | | This variable has been deprecated since Yocto Project version 3.0. (From OE-Core rev: f8ac58568b2dceef54a743369460019b3a3eeccd) Signed-off-by: Michael Opdenacker <michael.opdenacker@bootlin.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* meta: use new override syntax in commentsChen Qi2021-08-125-7/+7
| | | | | | | (From OE-Core rev: 572e7db6e8831227911ff3e52bde3a4aa6df1c91) Signed-off-by: Chen Qi <Qi.Chen@windriver.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* convert-overrides.py: also convert comments without a leading whitespaceChen Qi2021-08-121-3/+3
| | | | | | | | | | | | | | | | | Currently lines like below are converted. e.g. # IMAGE_INSTALL_append = " A" But lines without a leading whitespace are not converted. e.g. #IMAGE_INSTALL_append = " A" We should be converting both. (From OE-Core rev: 1994e3844c1aa6b595c0c18040e4f8240fa04438) Signed-off-by: Chen Qi <Qi.Chen@windriver.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* libtool: Fix lto option passing for reproducible buildsRichard Purdie2021-08-122-0/+23
| | | | | | | | | If lto is enabled, we need the prefix-map variables to be passed to the linker. Add these to the list of options libtool passes through. (From OE-Core rev: 2c26d2c00b47df856fb2d9c35486b135094d46ac) Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* ell: upgrade 0.41 -> 0.42wangmy2021-08-121-1/+1
| | | | | | | (From OE-Core rev: aedc4667474f891654f01bb4c0f542092fbe5aa3) Signed-off-by: Wang Mingyu <wangmy@fujitsu.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* curl: Fix reproducibility issue with LDFLAGSRichard Purdie2021-08-121-0/+1
| | | | | | | | | If we add DEBUG_PREFIX_MAP into LDFLAGS, curl-dev is no longer reproducible. Fix this. (From OE-Core rev: 3a30b7ad413de0e8f60504ba2be76107e4324640) Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* ruby: Fix reproducibility issue with LDFLAGSTony Battersby2021-08-122-0/+43
| | | | | | | | | | If we add DEBUG_PREFIX_MAP into LDFLAGS, ruby and ruby-dbg are no longer reproducible. Fix this. (From OE-Core rev: c34d5e409b291e69d6ff28ee71acba7055ef3f08) Signed-off-by: Tony Battersby <tonyb@cybernetics.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* gettext: Fix reproducibility issue with LDFLAGSRichard Purdie2021-08-121-0/+1
| | | | | | | | | If we add DEBUG_PREFIX_MAP into LDFLAGS, gettext-ptest is no longer reproducible. Fix this. (From OE-Core rev: c759bae9c3b360e0ca5321469e8d77512cadaf1e) Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* ruby: Fix DEBUG_PREFIX_MAP in LDFLAGS issueRichard Purdie2021-08-121-0/+4
| | | | | | (From OE-Core rev: 78da145c2f2fbd58e286e8ce983c2cc0b074e6a5) Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* bitbake.conf: add DEBUG_PREFIX_MAP to TARGET_LDFLAGSTony Battersby2021-08-121-1/+1
| | | | | | | | | | | | | | | -f*-prefix-map flags are required when linking with LTO enabled to make the output binary reproducible. See discussion here: https://gcc.gnu.org/bugzilla/show_bug.cgi?id=101473 [YOCTO #14481] (From OE-Core rev: fddaecc88979967d0e00e2fafdbaaabec030da9f) Signed-off-by: Tony Battersby <tonyb@cybernetics.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* valgrind: skip broken ptests for glibc 2.34Tony Tascioglu2021-08-122-0/+9
| | | | | | | | | | | | | Skip tests that are problematic for glibc-2.34. The list of problematic ptests was found by Richard after patching several to work with the new glibc version. https://bugzilla.yoctoproject.org/show_bug.cgi?id=14500 (From OE-Core rev: c177c7f9ef6f90ca49074f003accb8e9a1a645aa) Signed-off-by: Tony Tascioglu <tony.tascioglu@windriver.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* glibc: Add missing symlinks for libpthread and librt dev filesKhem Raj2021-08-121-0/+2
| | | | | | | (From OE-Core rev: 3a02079bbc29c64f3807f24f9b69ee02f765bec7) Signed-off-by: Khem Raj <raj.khem@gmail.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* glibc: Drop DUMMY_LOCALE_T define patchKhem Raj2021-08-123-31/+0
| | | | | | | | | It was needed for very old centos distros which are no longer supported (From OE-Core rev: 24663490adbb0434e810c13ab627a4903c018ca7) Signed-off-by: Khem Raj <raj.khem@gmail.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* glibc: Remove obsolete --enable-stackguard-randomizationKhem Raj2021-08-121-1/+0
| | | | | | | | | this has been removed in 2.34 onwards (From OE-Core rev: 1ca248f0b894b95b7fc9f0c0c76b5efe3555e386) Signed-off-by: Khem Raj <raj.khem@gmail.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* glibc: Upgrade to 2.34 releaseKhem Raj2021-08-1244-1443/+136
| | | | | | | | | | | | | | | | bump localedef to get __attr_access_none and __attr_access definitions replace /bin/bash instead of @BASH@ in ldd as @BASH@ has been substituted with /bin/bash now package libc_malloc_debug.so.0 Detailed changelog [1] [1] https://sourceware.org/pipermail/libc-alpha/2021-August/129718.html (From OE-Core rev: af4e1306a78cf8c508dd911f02c103af81bc1af5) Signed-off-by: Khem Raj <raj.khem@gmail.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* releases: update to include 3.1.10Michael Halstead2021-08-112-1/+2
| | | | | | | | | Adding 3.1.10 to documentation switcher and release list. (From yocto-docs rev: 86b44b72c366f56d6977e7462aca8821721d89bd) Signed-off-by: Michael Halstead <mhalstead@linuxfoundation.org> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* manuals: further documentation for cve-checkMichael Opdenacker2021-08-103-1/+97
| | | | | | | | | | | | | This adds details about the actual implementation of vulnerability checks, about how to fix or ignore vulnerabilities in recipes, and documents the CVE_CHECK_PN_WHITELIST and CVE_CHECK_WHITELIST variables. (From yocto-docs rev: 55886d211218b3a604c2f8a29c854685ebf284dd) Signed-off-by: Michael Opdenacker <michael.opdenacker@bootlin.com> Reviewed-by: Quentin Schulz <foss@0leil.net> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* manuals: mention license information in footerMichael Opdenacker2021-08-101-1/+1
| | | | | | | | | | Previously, the license for the manuals was only stated in the SPDX headers at the beginning of source files (From yocto-docs rev: cef60f23d5601a18d7ba7e894af2aa459fb2efb8) Signed-off-by: Michael Opdenacker <michael.opdenacker@bootlin.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* migration-3.4: Add extra notes to override syntax changesRichard Purdie2021-08-101-0/+7
| | | | | | | | (From yocto-docs rev: dba53562b684c511fb59a3272656cb6052f28fb2) Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org> Reviewed-by: Michael Opdenacker <michael.opdenacker@bootlin.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* test-manual: Add extra detail to YP Compatible sectionRichard Purdie2021-08-101-0/+5
| | | | | | | | | | | Add a note about documenting where a layer doesn't support 'core' functionality. (From yocto-docs rev: 0fc15d069aae11e6e705d80f684345150ff7bf3b) Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org> Reviewed-by: Michael Opdenacker <michael.opdenacker@bootlin.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* packagedata: Fix after override syntax changeRichard Purdie2021-08-061-1/+1
| | | | | | | | | Fix a reference that should have been part of the override syntax change causing packages to be written out incorrectly. (From OE-Core rev: 0f978b4f03e71267ad0a8a5054141e7727f2944f) Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* cve-check: improve comment about CVE patch file namesMichael Opdenacker2021-08-061-3/+6
| | | | | | | (From OE-Core rev: 8aa613480663e11ecc62278d8c57ca719eb23899) Signed-off-by: Michael Opdenacker <michael.opdenacker@bootlin.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* cve-check: update link to NVD website for CVE detailsMichael Opdenacker2021-08-061-1/+1
| | | | | | | | | | | | The old URL schema https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-ID now redirects to https://nvd.nist.gov/vuln/detail/CVE-ID (From OE-Core rev: 57adb57a9d9b08c08ab606ec7b561792e4f4ff2d) Signed-off-by: Michael Opdenacker <michael.opdenacker@bootlin.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* cve-check: fix commentsMichael Opdenacker2021-08-061-4/+4
| | | | | | | | | | | This implements various fixes in comments in cve-check.bbclass In particular, the "whitlisted" typo is important as the "whitelisted" word is going to be replaced in a near future. (From OE-Core rev: 5eecd2bf942254d08c252388594e5ec7ae330f45) Signed-off-by: Michael Opdenacker <michael.opdenacker@bootlin.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* oeqa/runtime/cases/ptest: Increase test timeout from 300s to 450sRichard Purdie2021-08-061-1/+1
| | | | | | | | | | Some tests such as lttng-tools are marginal and timing out on the autobuilder with the current 300s default. Increase to avoid this noise in the ptest failures list. (From OE-Core rev: 5fb902a52e35130af6b0735a087c709daa35655f) Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* bitbake: ui/taskexp: Fix to work with empty build directoriesRichard Purdie2021-08-061-0/+1
| | | | | | | | | | | | If run on an empty build directory, taskexp wasn't working as it didn't send the current environment to the server. This means HOSTTOOLS in oe-core couldn't be built and gave an error. Add the missing updateToServer call in. [YOCTO #14408] (Bitbake rev: 06a0bbe746f879ae539223e7fdb6f07d55d13719) Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* bitbake: ui/taskexp: Improve startup exception handlingRichard Purdie2021-08-061-0/+4
| | | | | | | | | | When an exception occurs at startup, show it to the user. [YOCTO #14408] (Bitbake rev: cc1df1af67cfd3e223b39e2b7ea5f86b8cf78aee) Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* bitbake: command: Ensure we catch/handle exceptionsRichard Purdie2021-08-061-3/+11
| | | | | | | | | | | If an exception occurs in early setup, bitbake could just hang. Return the exception rather than doing that. [YOCTO #14408] (Bitbake rev: c8a4107132ce51f84ae84bf1ceb1c3fd90f156d3) Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* bitbake: process: Improve traceback error reporting from main loopRichard Purdie2021-08-061-2/+4
| | | | | | | | | | | | | Currently the code can just show nothing as the exception if there was a double fault, which in this code path is quite likely. This leads to an error log which effectively says "it failed" with no information about how. Improve things so we get a nice verbose traceback left in the logs/output which is preferable to no logs. (Bitbake rev: e5782b71647d1eb6de53bde7bc4f6019a5589f21) Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* bitbake: fetch/tests/toaster: Override conversion fixupsRichard Purdie2021-08-064-4/+4
| | | | | | | | | Fix some references that missed during the overrides syntax migration or were incorrect. Thanks to Quentin Schulz <foss@0leil.net> for the patch. (Bitbake rev: 6184cb07dfa44f5f76f1c423533b4547d80b20ab) Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* bitbake: doc: Fix append/prepend/remove referencesRichard Purdie2021-08-061-13/+13
| | | | | | | | | Fix some references missed during the overrides syntax migration. Thanks to Quentin Schulz <foss@0leil.net> for the patch. (Bitbake rev: 2fd03ec7b136c694f2ced43b3abb69f719c99ec2) Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* gcc: Backport patch to make LTO builds more reproducibleTony Battersby2021-08-052-0/+96
| | | | | | | | | | | | Backport ustream gcc patch that enables -fdebug-prefix-map to cover additional cases with LTO enabled to make LTO builds more reproducible. [YOCTO #14481] (From OE-Core rev: 8923253b9bc91b14b474abc4923ca916fb8a12ec) Signed-off-by: Tony Battersby <tonyb@cybernetics.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* lto.inc: disable LTO for grubTony Battersby2021-08-051-0/+2
| | | | | | | | | | | | | | With gcc 11.1, compiling grub with LTO causes an internal compiler error (ICE), and with gcc 10.2, files under /usr/lib/grub/i386-pc/*.mod are not binary reproducible. [YOCTO #14490] (gcc 11.1 ICE) [YOCTO #14481] (LTO and binary reproducibility) (From OE-Core rev: d1fd3693411d83214f0f88b2f9d7aef12ecd6e02) Signed-off-by: Tony Battersby <tonyb@cybernetics.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* elfutils: Add patch from upstream for glibc 2.34 ptest fixesRichard Purdie2021-08-052-0/+139
| | | | | | | | Add a patch being discussed upstream to fix a ptest issue with glibc 2.34. (From OE-Core rev: 8921f2acfd566d2c03cea7bdb9f0b1883994148b) Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* bitbake: runqueue: Improve multiconfig deferred task issuesRichard Purdie2021-08-051-26/+32
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | The previous patches have exposed new issues with this code path, the issues being around what should happen when the hash of a task changes and the task is or is not on the deferred task list. Rather than rebuilding the deferred task list during each rehash event, build it once at the start of a build. This avoids the problem of tasks being added back after they have run and also avoids problems of always ensuring the same task is deferred. It also allows the 'outrightfail' codepath to be handled separately as the conditions are subtly differnt. One significant win for the new approch is the build is not continually printing out lists of deferred tasks, that list remains fairly static from the start of the build. Logic is added in to ensure a rehashed task with a hash matching other deferred tasks is deferred along with them as a small optimization. An interesting test case for this code was reported by Mark Hatle with four multiconfigs, each the same apart from TMPDIR and running a build of: bitbake buildtools-tarball mc:{one,two,three,four}:core-image-minimal which is interesting in that the build of buildtools partially overlaps core-image-minimal and the build has a rehash event for qemuwrapper-cross even without any external hash equivalence server or preexisting data. (Bitbake rev: bb424e0a6d274d398f434f7df63951da9ce305b3) Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* local.conf.sample: disable prelinkAlexander Kanavin2021-08-051-2/+1
| | | | | | | | | | | | | | | | | | | | | | | Recent tests have shown that prelinking works only when PIE is not enabled [0], and as PIE is both a desirable security feature, and the only configuration provided and tested by Yocto, there is simply no sense in continuing to enable prelink. There's also a concern that no one is maintaining the code, and there are open bugs (including serious ones such as [1]). Given that prelink does intricate address arithmetic and rewriting of binaries the best option is to disable the feature. [0] https://rlbl.me/prelink-1 https://rlbl.me/prelink-2 [1] https://bugzilla.yoctoproject.org/show_bug.cgi?id=14429 (From meta-yocto rev: f712b495ce6362d50db3c5c565245535429d6419) Signed-off-by: Alexander Kanavin <alex.kanavin@gmail.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* valgrind: Add patches for glibc 2.34 supportRichard Purdie2021-08-055-0/+1674
| | | | | | | | This partially resolves ptest failures with glibc 2.34. (From OE-Core rev: 9adf897176924cad6b12d4da73a904cfbf578f46) Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* strace: Upgrade 5.12 -> 5.13Richard Purdie2021-08-052-6/+6
| | | | | | | | This includes changes to work with glibc 2.34. (From OE-Core rev: 58cdb3ff8689c5e87769eb53d154a395492cdeb5) Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* diffoscope: Upgrade 178 -> 179Richard Purdie2021-08-051-1/+1
| | | | | | (From OE-Core rev: c889354ead36c332ee47bbeadea0dfd96d7dd5d3) Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* systemd-boot: use ld.bfd as efi-ld even when gold or lld is used in ${LD}Martin Jansa2021-08-051-1/+4
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | * since the upgrade to 249.1 in: https://git.openembedded.org/openembedded-core/commit/?id=323ec445dfe22860cd450c303db5ed8fcb4e791c the builds with ld-is-gold are failing with: [17/21] Generating linuxx64.elf.stub with a custom command FAILED: src/boot/efi/linuxx64.elf.stub /OE/build/oe-core/tmp-glibc/work/core2-64-oe-linux/systemd-boot/249.1-r0/recipe-sysroot-native/usr/bin/x86_64-oe-linux/x86_64-oe-linux-ld -o src/boot/efi/linuxx64.elf.stub -T /OE/build/oe-core/tmp-glibc/work/core2-64-oe-linux/systemd-boot/249.1-r0/recipe-sysroot/usr/lib/elf_x86_64_efi.lds -shared -Bsymbolic -nostdlib -znocombreloc --build-id=sha1 -L /OE/build/oe-core/tmp-glibc/work/core2-64-oe-linux/systemd-boot/249.1-r0/recipe-sysroot/usr/lib /OE/build/oe-core/tmp-glibc/work/core2-64-oe-linux/systemd-boot/249.1-r0/recipe-sysroot/usr/lib/crt0-efi-x86_64.o src/boot/efi/string-util-fundamental.c.o src/boot/efi/disk.c.o src/boot/efi/graphics.c.o src/boot/efi/measure.c.o src/boot/efi/pe.c.o src/boot/efi/secure-boot.c.o src/boot/efi/util.c.o src/boot/efi/linux.c.o src/boot/efi/splash.c.o src/boot/efi/stub.c.o -lefi -lgnuefi /OE/build/oe-core/tmp-glibc/work/core2-64-oe-linux/systemd-boot/249.1-r0/recipe-sysroot/usr/lib/../lib/x86_64-oe-linux/11.2.0/libgcc.a /OE/build/oe-core/tmp-glibc/work/core2-64-oe-linux/systemd-boot/249.1-r0/recipe-sysroot-native/usr/bin/x86_64-oe-linux/x86_64-oe-linux-ld: internal error in segment_precedes, at ../../gold/layout.cc:3721 [18/21] Generating boot.c.o with a custom command ninja: build stopped: subcommand failed. WARNING: exit code 1 from a shell command. as reported in: https://lists.openembedded.org/g/openembedded-core/message/154246 * if someone is using lld or ld.lld in ${LD} then it would fail as well: https://github.com/systemd/systemd/commit/e39288193fcdf3a36dbc49b78e6c9bf86a764e31 * work around this by always using ld.bfd instead of whatever is set in ${LD} * it needs to be prefixed with ${HOST_PREFIX} to match how LD is constructed: $ bitbake-getvar -r systemd-boot LD # # $LD [2 operations] # exported /OE/build/oe-core/openembedded-core/meta/conf/bitbake.conf:523 # [export] "1" # set /OE/build/oe-core/openembedded-core/meta/conf/bitbake.conf:523 # "${HOST_PREFIX}ld${TOOLCHAIN_OPTIONS} ${HOST_LD_ARCH}" # pre-expansion value: # "${HOST_PREFIX}ld${TOOLCHAIN_OPTIONS} ${HOST_LD_ARCH}" export LD="x86_64-oe-linux-ld --sysroot=/OE/build/oe-core/tmp-glibc/work/core2-64-oe-linux/systemd-boot/249.1-r0/recipe-sysroot " $ bitbake-getvar -r systemd-boot EFI_LD # # $EFI_LD # set /OE/build/oe-core/openembedded-core/meta/recipes-core/systemd/systemd-boot_249.1.bb:23 # "${HOST_PREFIX}ld.bfd" EFI_LD="x86_64-oe-linux-ld.bfd" otherwise first ld.bfd it will find will be from HOSTTOOLS_NONFATAL and fail when host's binutils isn't compatible as in: https://autobuilder.yoctoproject.org/typhoon/#/builders/104/builds/2673/steps/11/logs/stdio FAILED: src/boot/efi/linuxx64.elf.stub /home/pokybuild/yocto-worker/genericx86-64-alt/build/build/tmp/hosttools/ld.bfd -o src/boot/efi/linuxx64.elf.stub -T /home/pokybuild/yocto-worker/genericx86-64-alt/build/build/tmp/work/core2-64-poky-linux/systemd-boot/249.1-r0/recipe-sysroot/usr/lib/elf_x86_64_efi.lds -shared -Bsymbolic -nostdlib -znocombreloc --build-id=sha1 -L /home/pokybuild/yocto-worker/genericx86-64-alt/build/build/tmp/work/core2-64-poky-linux/systemd-boot/249.1-r0/recipe-sysroot/usr/lib /home/pokybuild/yocto-worker/genericx86-64-alt/build/build/tmp/work/core2-64-poky-linux/systemd-boot/249.1-r0/recipe-sysroot/usr/lib/crt0-efi-x86_64.o src/boot/efi/string-util-fundamental.c.o src/boot/efi/disk.c.o src/boot/efi/graphics.c.o src/boot/efi/measure.c.o src/boot/efi/pe.c.o src/boot/efi/secure-boot.c.o src/boot/efi/util.c.o src/boot/efi/linux.c.o src/boot/efi/splash.c.o src/boot/efi/stub.c.o -lefi -lgnuefi /home/pokybuild/yocto-worker/genericx86-64-alt/build/build/tmp/work/core2-64-poky-linux/systemd-boot/249.1-r0/recipe-sysroot/usr/lib/../lib/x86_64-poky-linux/11.2.0/libgcc.a /home/pokybuild/yocto-worker/genericx86-64-alt/build/build/tmp/hosttools/ld.bfd: warning: /home/pokybuild/yocto-worker/genericx86-64-alt/build/build/tmp/work/core2-64-poky-linux/systemd-boot/249.1-r0/recipe-sysroot/usr/lib/crt0-efi-x86_64.o: unsupported GNU_PROPERTY_TYPE (5) type: 0xc0010002 /home/pokybuild/yocto-worker/genericx86-64-alt/build/build/tmp/hosttools/ld.bfd: warning: /home/pokybuild/yocto-worker/genericx86-64-alt/build/build/tmp/work/core2-64-poky-linux/systemd-boot/249.1-r0/recipe-sysroot/usr/lib/crt0-efi-x86_64.o: unsupported GNU_PROPERTY_TYPE (5) type: 0xc0010001 /home/pokybuild/yocto-worker/genericx86-64-alt/build/build/tmp/hosttools/ld.bfd: /home/pokybuild/yocto-worker/genericx86-64-alt/build/build/tmp/work/core2-64-poky-linux/systemd-boot/249.1-r0/recipe-sysroot/usr/lib/crt0-efi-x86_64.o: unable to initialize decompress status for section .debug_line /home/pokybuild/yocto-worker/genericx86-64-alt/build/build/tmp/hosttools/ld.bfd: /home/pokybuild/yocto-worker/genericx86-64-alt/build/build/tmp/work/core2-64-poky-linux/systemd-boot/249.1-r0/recipe-sysroot/usr/lib/crt0-efi-x86_64.o: unable to initialize decompress status for section .debug_line /home/pokybuild/yocto-worker/genericx86-64-alt/build/build/tmp/work/core2-64-poky-linux/systemd-boot/249.1-r0/recipe-sysroot/usr/lib/crt0-efi-x86_64.o: file not recognized: File format not recognized (From OE-Core rev: 603e50f3db224a0e36a65decb9a98df41b9e22b3) Signed-off-by: Martin Jansa <Martin.Jansa@gmail.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* python3-importlib-metadata: upgrade 4.6.1 -> 4.6.3Tim Orling2021-08-051-1/+1
| | | | | | | | | | | | | | | | | | v4.6.3 Moved workaround for #327 to _compat module. v4.6.2 bpo-44784: Avoid errors in test suite when DeprecationWarnings are treated as errors. References: https://github.com/python/importlib_metadata/issues/327 https://bugs.python.org/issue44784 (From OE-Core rev: 9ac45967b0e739d7480ac432bab0b0ca0341b24b) Signed-off-by: Tim Orling <timothy.t.orling@intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
generated by cgit v1.2.3-54-g00ecf (git 2.39.0) at 2025-08-12 13:37:19 +0000