Skip to contentSkip to conversation

libxcrypt: fix hard-coded ".so" extension

PATCH New [email protected] 1 participant 1 message Jul 2, 2023

lore
Share & tools
lore
#0 lore raw

PATCH 1/1 libxcrypt: fix hard-coded ".so" extension

From: Etienne Cordonnier <[email protected]>

2 issues:
- the .so extension is hard-coded, and therefore the libxcryt package compiled with meta-darwin is empty, because the dylib files are not contained in FILES_${PN}
- nothing actually produces a file libcrypt-*.so (the symlink file is libcrypt.so, without dash), thus defining FILES:${PN} manually to contain libcrypt-*.so has no effect.

(cherry picked from commit 7ed6bfa2428b4f1ba7f09d6e9e67c462ff355153)
---
 meta/recipes-core/libxcrypt/libxcrypt.inc | 6 ------
 1 file changed, 6 deletions(-)
meta/recipes-core/libxcrypt/libxcrypt.inc +0 -6
index 61b0381076..454a55d73d 100644
@@ -17,12 +17,6 @@ SRC_URI += "file://fix_cflags_handling.patch"
 
 PROVIDES = "virtual/crypt"
 
-FILES:${PN} = "${libdir}/libcrypt*.so.* \
-               ${libdir}/libcrypt-*.so \
-               ${libdir}/libowcrypt*.so.* \
-               ${libdir}/libowcrypt-*.so \
-"
-
 S = "${WORKDIR}/git"
 
 BUILD_CPPFLAGS = "-I${STAGING_INCDIR_NATIVE}"
Signature · 1 line
2.35.6