linux/poky.git/meta/recipes-core/libxcrypt, branch master

The poky repository master branch is no longer being updated.

2025-11-07T13:31:53+00:00

You can either: a) switch to individual clones of bitbake, openembedded-core, meta-yocto and yocto-docs b) use the new bitbake-setup You can find information about either approach in our documentation: https://docs.yoctoproject.org/ Note that "poky" the distro setting is still available in meta-yocto as before and we continue to use and maintain that. Long live Poky! Some further information on the background of this change can be found in: https://lists.openembedded.org/g/openembedded-architecture/message/2179 Signed-off-by: Richard Purdie

libxcrypt: Allow undefined symbols in version scripts with lld linker

2025-08-14T09:31:10+00:00

Unlike GNU ld, LLD defaults to erroring about undefined version symbols add commandline parameter to sush lld here Fixes | x86_64-yoesdk-linux-ld.lld: error: version script assignment of 'XCRYPT_2.0' to symbol 'crypt_gensalt_r' failed: symbol not defined | x86_64-yoesdk-linux-ld.lld: error: version script assignment of 'XCRYPT_2.0' to symbol 'xcrypt' failed: symbol not defined | x86_64-yoesdk-linux-ld.lld: error: version script assignment of 'XCRYPT_2.0' to symbol 'xcrypt_gensalt' failed: symbol not defined | x86_64-yoesdk-linux-ld.lld: error: version script assignment of 'XCRYPT_2.0' to symbol 'xcrypt_gensalt_r' failed: symbol not defined | x86_64-yoesdk-linux-ld.lld: error: version script assignment of 'XCRYPT_2.0' to symbol 'xcrypt_r' failed: symbol not defined | x86_64-yoesdk-linux-clang: error: linker command failed with exit code 1 (use -v to see invocation) LLD has stricter defaults and strict symbol versioning enforcement. LLD requires that all symbols referenced in version scripts actually exist in the object files being linked Same errors/behavior can be seen with GNU linker as well if we add -Wl,--undefined-version to LDFLAGS GNU linker chooses to be a bit lenient with defaults. Having LLD to lower its barrier does not change the output it produces, it's the same as GNU ld This is known issue seen with other distros e.g. NixOS upstream [1] [1] https://github.com/besser82/libxcrypt/issues/181 (From OE-Core rev: 26a293d639ab88db84137e9df1d608dfa15aba5f) Signed-off-by: Khem Raj Signed-off-by: Mathieu Dubois-Briand Signed-off-by: Richard Purdie

meta: remove consecutive blank lines

2025-06-20T11:07:27+00:00

Some of them were introduced by mass-removal of S = WORKDIR/git assignments; rather than try to fix up (or redo) just these, I've run this sed command over the whole tree: sed -i -z -E 's/([ \t\f\v\r]*\n){3,}/\n\n/g' `find . -name *.bb -o -name *.inc` The rationale is that more than one empty line is wasting vertical screen space, and does nothing for readability. (From OE-Core rev: cedc4ff7c9bcfb22a20e43e47f9759f4007a4f1a) Signed-off-by: Alexander Kanavin Signed-off-by: Mathieu Dubois-Briand Signed-off-by: Richard Purdie

meta: remove S in recipes that fetch from git via setting BB_GIT_DEFAULT_DESTSUFFIX

2025-06-20T11:07:26+00:00

Removing all the S = ${WORKDIR}/git assignments works because BB_GIT_DEFAULT_DESTSUFFIX is set to match S from bitbake.conf (which itself is set to match typical tarball releases). A few recipes are setting S to a sub-directory of the git tree and need to be adjusted accordingly. bzip2 recipe is fetching a tarball and separately cloning tests; adjust the recipe to put the latter into 'bzip2-tests', instead of 'git'. devupstream.bbclass no longer needs to rewrite S, and is adjusted accordingly. Adjust scripts/lib/recipetool/append.py to not hardcode 'git' as unpack destination. Adjust kernel-yocto.bbclass to use the git unpack variable instead of hardcoding 'git' (there's also removal of repetition of string constants and a correction of workdir/unpackdir mismatch in one of the if-else branches). Ensure build-appliance-image recipe does not use 'git' as checkout directory for poky repo, but rather explicitly name it 'poky'. Ensure reproducible.py code that looks for git repositories does not hardcode 'git' but uses the destination set by BB_GIT_DEFAULT_DESTSUFFIX. Ensure recipetool does not write out unneeded S settings into newly created recipes that fetch from git. Adjust selftest to not hardcode 'git' as unpack directory. (From OE-Core rev: f80c07019ddadaf9c5fb890faabfda7920ecd15e) Signed-off-by: Alexander Kanavin Signed-off-by: Mathieu Dubois-Briand Signed-off-by: Richard Purdie

libxcrypt-compat,libxcrypt: upgrade 4.4.37 -> 4.4.38

2025-02-18T11:56:04+00:00

Drop patch which is already applied upstream [1] since 4.4.20 [1] https://github.com/besser82/libxcrypt/commit/fed81d1a98fab52839b60a55447d368899034847 (From OE-Core rev: 7b802e4e55b37e985cc7151a8a8561b206563509) Signed-off-by: Khem Raj Signed-off-by: Mathieu Dubois-Briand Signed-off-by: Richard Purdie

libxcrypt: update 4.4.36 -> 4.4.37

2025-01-10T11:10:00+00:00

Drop patch merged upstream. (From OE-Core rev: b66d046a3fe4230ba3b74c6741419f51bbfca9bd) Signed-off-by: Alexander Kanavin Signed-off-by: Richard Purdie

libxcrypt: correct the check for a working libucontext.h

2024-06-24T11:43:41+00:00

The test fails with GCC 14.1 due to an incompatible pointer assignment, take a patch submitted upstream to fix this. (From OE-Core rev: 054304ecb3a8a8ed523bd149f70ed468cf613178) Signed-off-by: Ross Burton Signed-off-by: Alexandre Belloni Signed-off-by: Richard Purdie

libxcrypt-compat: Rename libcrypto.so.1 -> libcrypt.so.1

2024-05-09T08:56:36+00:00

The comment in libxcrypt-cmpat incorrectly mentions libcrypto instead of libcrypt which could be misleading to the unsuspecting grep user. (From OE-Core rev: 3400945ac94c37f335b1e500bdd91e6187ed20b1) Signed-off-by: Jordan Crouse Signed-off-by: Richard Purdie

libxcrypt-compat: Remove libcrypt.so to fix conflict with libcrypt

2023-09-12T06:45:52+00:00

Fixed: IMAGE_INSTALL:append = " libxcrypt-compat" $ bitbake -cpopulate_sdk file /usr/lib/libcrypt.so from install of libxcrypt-compat-dev-4.4.33-r0.0.aarch64 conflicts with file from package libcrypt-dev-4.4.33-r0.2.aarch64 Remove libcrypt.so like other files to fix the error. (From OE-Core rev: dc0c7a8c3d1d4f02869b7f0d42f704fd24bf0dde) Signed-off-by: Robert Yang Signed-off-by: Richard Purdie

libxcrypt: upgrade 4.4.35 -> 4.4.36

2023-07-14T16:31:06+00:00

Changelog: * Fix left over bits failing with Perl v5.38.0 (issue #173). (From OE-Core rev: f77b5039b9c31fc20594b02ff165131d0c7fcb39) Signed-off-by: Wang Mingyu Signed-off-by: Alexandre Belloni Signed-off-by: Richard Purdie