libgcrypt1.9.0: Failure on linking test executables
NIIBE Yutaka
gniibe at fsij.org
Fri Jan 22 04:59:05 CET 2021
Kasumi Fukuda <kasumi at rollingapple.net> writes:
> Let me share a repro step using docker:
Thanks a lot.
I think that it's better practice to do "make check" before
installation.
And to do that, we need to specify LD_LIBRARY_PATH too (as well as
PATH), so that testing programs in the build procedure run correctly.
Like this:
--- libgcrypt-test-install-orig.sh 2021-01-22 11:06:34.329216354 +0900
+++ libgcrypt-test-install-fixed.sh 2021-01-22 12:29:42.725628836 +0900
@@ -11,12 +11,13 @@
cd /tmp/libgpg-error-1.41
./configure --prefix=/opt/libgpg-error --disable-doc
-make && make install
+make && make check && make install
export PATH=/opt/libgpg-error/bin:$PATH
+export LD_LIBRARY_PATH=/opt/libgpg-error/lib
cd /tmp/libgcrypt-1.9.0
./configure --prefix=/opt/libgcrypt --disable-doc
-make && make install
+make && make check && make install
EOF
And... this works, with no linking errors.
The problem is somehow complicated. The linker checks runtime libraries
under LD_LIBRARY_PATH.
In your case, even if you don't need 'make check', please specify
LD_LIBRARY_PATH.
--
More information about the Gcrypt-devel
mailing list