On Thu, Dec 12, 2019 at 10:33 AM Werner Koch via Gnupg-users <gnupg-users@gnupg.org> wrote: > > On Wed, 11 Dec 2019 23:24, Johan Wevers said: > > >> libassuan.so.0 is linked to libassuan.so.0.8.3. > > > > That's quite an ancient version, current version is 2.5.3. My first > > Nope. Assuming this is a standard Linux distor, this is the lates > versions. The name of the libary includes the *SO version* which is > another name for the ABI. The 2.5.3 is the software version - software > verion and SO version are different. > > The problem here is that GnuPg was build using a newer Libassuan version > but the runtime linker picks up an older version. Set LD_LIBARY_PATH > and things will be good. Or put /usr/local/lib into your ld.so.conf so > that they are picked up. > > > Shalom-Salam, > > Werner > > -- > Die Gedanken sind frei. Ausnahmen regelt ein Bundesgesetz. > Thank you for your quick and clear response; however I must still be missing something.
With $ printenv LD_LIBRARY_PATH giving /..../src/gnupg/gnupg-2.2.19/PLAY/inst/lib $ gpg-agent --version gives the same relocation error as before. What should I try now? --ajax -- _______________________________________________ > Gnupg-users mailing list > Gnupg-users@gnupg.org > http://lists.gnupg.org/mailman/listinfo/gnupg-users _______________________________________________ Gnupg-users mailing list Gnupg-users@gnupg.org http://lists.gnupg.org/mailman/listinfo/gnupg-users
