linux/poky.git/meta/recipes-support/libgcrypt, 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

libgcrypt: 1.11.1 -> 1.11.2

2025-08-28T09:47:09+00:00

Refresh patches: - 0004-tests-Makefile.am-fix-undefined-reference-to-pthread.patch - 0001-tests-Fix-link-errors-for-t-thread-local.patch (From OE-Core rev: 3fd1cfadefa876b403c7d8dfe6169f4c429fe78e) Signed-off-by: Hongxu Jia Signed-off-by: Mathieu Dubois-Briand Signed-off-by: Richard Purdie

libgcrypt: drop -unknown suffix from version number

2025-07-03T09:40:16+00:00

Include drop-unknown-suffix.inc to remove unknown suffix in runtime version. Befor the fix: $ mpicalc --version mpicalc 2.0 libgcrypt 1.11.0-unknown After the fix: $ mpicalc --version mpicalc 2.0 libgcrypt 1.11.0 (From OE-Core rev: 62e82a9410c66fa3f7607243bfc44faa159edbe2) Signed-off-by: Yi Zhao Signed-off-by: Richard Purdie

libgcrypt: fix compile error for t-thread-local

2025-06-05T10:02:21+00:00

Currently the libgcrypt-native build is failing with the following error: | ld: t_thread_local-t-thread-local.o: in function `main': | t-thread-local.c:(.text.startup+0x187): undefined reference to `pthread_create' | ld: t-thread-local.c:(.text.startup+0x1d0): undefined reference to `pthread_join' Backport the fix from upstream and add "-lpthread" to "t_thread_local_CFLAGS" to make the compilation successfull, similar to what 0004-tests-Makefile.am-fix-undefined-reference-to-pthread.patch does. (From OE-Core rev: d2daf78a083688b82625800919cdc6c6555fcc52) Signed-off-by: Hiago De Franco Signed-off-by: Richard Purdie

libgcrypt: upgrade 1.11.0 -> 1.11.1

2025-05-22T13:36:49+00:00

(From OE-Core rev: 73bcdedc80a83e241d2162b10a2244a8dbd0e403) Signed-off-by: Hongxu Jia Signed-off-by: Mathieu Dubois-Briand Signed-off-by: Richard Purdie

libgcrypt: upgrade 1.10.3 -> 1.11.0

2024-07-26T11:28:42+00:00

Changelog: ========== https://lists.gnu.org/archive/html/info-gnu/2024-06/msg00004.html License-Update: -Add 3-clause BSD license for poly1305-amd64-avx512.S. -cipher/Makefile.am: Add 'poly1305-amd64-avx512.S'. -cipher/poly1305-amd64-avx512.S: New. -cipher/poly1305-internal.h (POLY1305_USE_AVX512): New. -Add 'cipher/keccak-amd64-avx512.S'. -Update license docs for FSF new address and update gcrypt.texi. Apart from upgrade also refreshed the patches like 0001-libgcrypt-fix-m4-file-for-oe-core.patch 0002-libgcrypt-fix-building-error-with-O2-in-sysroot-path.patch no-bench-slope.patch In 0002-libgcrypt-fix-building-error-with-O2-in-sysroot-path.patch reverted back the change in cipher/Makefile.am related to o_flag_munging (From OE-Core rev: aa50e6bc8dcb3f5870e1fa285ec5ab997a7a59cf) Signed-off-by: simit.ghane Signed-off-by: Richard Purdie

libgcrypt: Fix building error with '-O2' in sysroot path

2024-07-02T21:29:13+00:00

Characters like '-O2' or '-Ofast' will be replaced by '-O1' and '-O0' respectively when compiling cipher and random in the filesystem paths as well if they happen to contain '-O2' or '-Ofast If we are cross compiling libgcrypt and sysroot contains such characters, we would get compile errors because the sysroot path has been modified. Fix this by adding blank spaces and tabs before the original matching pattern in the sed command. It is difficult to control -O1 for cipher and -O0 for random at the same time in OE environment along with patch file. So, keeping same change as it is. (From OE-Core rev: ecd26bbba36ad715c2a0f20475ebc977ea94746c) Signed-off-by: simit.ghane Signed-off-by: Richard Purdie

meta: Remove some not needed CVE_STATUS

2024-02-24T16:10:23+00:00

CVE_STATUS was set for those components, but meanwhile databases are updated with corrected information, so setting the CVE_STATUS is not needed anymore. (From OE-Core rev: 5ec6057cfa66ceeb33bec013e320f8e3fa7d7ecf) Signed-off-by: Simone Weiß Signed-off-by: Richard Purdie

libgcrypt: upgrade 1.10.2 -> 1.10.3

2023-11-30T08:43:03+00:00

Changelog: ========== - Fix public key computation for other EdDSA curves. - Remove out of core handler diagnostic in FIPS mode. - Check that the digest size is not zero in gcry_pk_sign_md and gcry_pk_verify_md. - Make store an s-exp with \0 is considered to be binary. - Various constant-time improvements. - Use getrandom call only when supported by the platform. - Change the default for --with-libtool-modification to never. (From OE-Core rev: e21583896116cf37bf6b95aea466854e4fd5e54b) Signed-off-by: Wang Mingyu Signed-off-by: Alexandre Belloni Signed-off-by: Richard Purdie

cve_check: convert CVE_CHECK_IGNORE to CVE_STATUS

2023-07-21T10:52:26+00:00

- Try to add convert and apply statuses for old CVEs - Drop some obsolete ignores, while they are not relevant for current version (From OE-Core rev: 1634ed4048cf56788cd5c2c1bdc979b70afcdcd7) Signed-off-by: Andrej Valek Reviewed-by: Peter Marko Signed-off-by: Alexandre Belloni Signed-off-by: Richard Purdie