Mailing List Archive

On 2021.11.08 10:54, Christoph Klassen via Gnupg-users wrote:
>
> I was trying to build GnuPG 2.3.3. For that reason I downloaded and
> built npth 1.6, libgpg-error 1.43, libgcrypt 1.9.4, libksba 1.6.0 and
> libassuan 2.5.5 (in this order). Then I started the build process for
> GnuPG with ./configure and make && make check. One test failed,
> saying: "t-recsel: Fatal: libgcrypt is too old (need 1.9.1, have
> 1.8.8)".

Did that happen during ./configure or during make check? In either
case, I would check for any left-over remnants of an older install of
libgcrypt, such as a stray pkcgonfig file.

_______________________________________________
Gnupg-users mailing list
Gnupg-users@gnupg.org
http://lists.gnupg.org/mailman/listinfo/gnupg-users

On 08.11.21 17:28, Jack via Gnupg-users wrote:
> In either case, I would check for any left-over remnants of an older
> install of libgcrypt, such as a stray pkcgonfig file.
I didn't think of old installations, but that was the right clue. On my
system the package libgcrypt20 was installed (from the debian repos).
The solution was to run first dpkg --purge --force-all libgcrypt20
(couldn't remove it the normal way because of some dependencies). Then I
could build GnuPG without errors. But at least one application didn't
work, so I reinstalled libgcrypt20. Now both, GnuPG and the other
application work and everything is fine!


_______________________________________________
Gnupg-users mailing list
Gnupg-users@gnupg.org
http://lists.gnupg.org/mailman/listinfo/gnupg-users

On Mon, 8 Nov 2021 20:30, Christoph Klassen said:

> repos). The solution was to run first dpkg --purge --force-all
> libgcrypt20 (couldn't remove it the normal way because of some

Not a good idea. That may break things. It is better to install
libgcrypt and the other libs to /user/local/lib and then set
LD_LIBRARY_PATH accordingly (or fix search order in ld.so.conf).

> one application didn't work, so I reinstalled libgcrypt20. Now both,

Libgcrypt 1.9 is compatible to 1.8 but not vice versa.


Shalom-Salam,

Werner

--
Die Gedanken sind frei. Ausnahmen regelt ein Bundesgesetz.

On Wed, Nov 10, 2021 at 08:13:18AM +0100, Werner Koch via Gnupg-users wrote:
>
> Not a good idea. That may break things. It is better to install
> libgcrypt and the other libs to /user/local/lib and then set
> LD_LIBRARY_PATH accordingly (or fix search order in ld.so.conf).

make install usually says,

> Libraries have been installed in:
...
> If you ever happen to want to link against installed libraries
> in a given directory, LIBDIR, you must either use libtool, and
> specify the full pathname of the library, or use the `-LLIBDIR'
> flag during linking and do at least one of the following:
> - add LIBDIR to the `LD_LIBRARY_PATH' environment variable
> during execution
> - add LIBDIR to the `LD_RUN_PATH' environment variable
> during linking
> - use the `-Wl,-rpath -Wl,LIBDIR' linker flag
> - have your system administrator add LIBDIR to `/etc/ld.so.conf'
>
> See any operating system documentation about shared libraries for
> more information, such as the ld(1) and ld.so(8) manual pages.