gpg2 --version gpg: Fatal: libgcrypt is too old (need 1.7.0, have 1.6.3)

[murphy]

Hi David - I have run into this exact issue on various 32 bit machines
or OS that run as 32 bit, like raspberry pi.  I am certainly no expert
but this seems to consistently solve the problem.

sudo nano /etc/ld.so.conf

Then place the following as the first line:

include /etc/ld.so.conf.d/libc.conf

save and then:

sudo ldconfig

Best of luck!

Murphy




signature.asc
Description: OpenPGP digital signature
___
Gnupg-users mailing list
Gnupg-users@gnupg.org
http://lists.gnupg.org/mailman/listinfo/gnupg-users

Re: gpg2 --version gpg: Fatal: libgcrypt is too old (need 1.7.0, have 1.6.3)

[David Adamson]

Running ldconfig as root resolved the issue I was having! Now when I
type gpg2 --version in a new shell it reports the following:

gpg (GnuPG) 2.1.15
libgcrypt 1.7.3

Thanks for the help.

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

Re: gpg2 --version gpg: Fatal: libgcrypt is too old (need 1.7.0, have 1.6.3)

[Peter Lebbing]

On 19/11/16 15:13, David Adamson wrote:
> Are you proposing I do this every time I wish to use gpg2?
> Is this behavior expected in a successful installation or what did I
> do wrong and can I fix it?

Did you issue a

# ldconfig

as root after you installed the libraries? Because you say you run
Debian jessie, and that has the file:

::
/etc/ld.so.conf.d/libc.conf
::
# libc default configuration
/usr/local/lib

So unless you manually changed the settings for ld.so, this directory
should already be in the system search path. However, invoking ldconfig
as root is a necessary step to scan these directories for new additions,
AFAIK. Possibly this is only necessary if you put the first library in
one of the dirs, I don't have the details ready. But in a normal Debian
jessie system, libraries in this directory should "Just Work"(TM).

Or is this a problem with the 1.6.3 receiving priority over 1.7.3? I
don't know off the top of my head how to fix that, so let's try ldconfig
first...

HTH,

Peter.

-- 
I use the GNU Privacy Guard (GnuPG) in combination with Enigmail.
You can send me encrypted mail if you want some privacy.
My key is available at 

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

Re: gpg2 --version gpg: Fatal: libgcrypt is too old (need 1.7.0, have 1.6.3)

[David Adamson]

That worked thank you but only for that session and I read that it's
generally not good practice to make that path permanent.

Are you proposing I do this every time I wish to use gpg2?
Is this behavior expected in a successful installation or what did I
do wrong and can I fix it?

Thanks again.

P.S. I am prepared to do fresh install of OS if that would be smart.

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

Re: gpg2 --version gpg: Fatal: libgcrypt is too old (need 1.7.0, have 1.6.3)

[Werner Koch]

On Sat, 19 Nov 2016 00:24, davidadamson...@gmail.com said:

> gpg: Fatal: libgcrypt is too old (need 1.7.0, have 1.6.3).

You built gpg2 against Libgcrypt 1.7 but the system can't find that
library at runtime and uses the system provided version (1.6.3).  Quick
workaround (assuming gpg was built with defaults):

  $ LD_LIBRARY_PATH=/usr/local/lib
  $ export LD_LIBRARY_PATH


Shalom-Salam,

   Werner

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


pgpj_xBMxlzdZ.pgp
Description: PGP signature
___
Gnupg-users mailing list
Gnupg-users@gnupg.org
http://lists.gnupg.org/mailman/listinfo/gnupg-users

gpg2 --version gpg: Fatal: libgcrypt is too old (need 1.7.0, have 1.6.3)

[David Adamson]

Hello,

I'm running a debian Jessie v8 kernel release 3.16.0-4-amd64 on my
personal laptop. It came pre-installed with GnuPG 1.4.18.

Rightly or not I thought having the latest version was a good idea for
no other reason than wanting to have the latest and greatest. So from
gnupg.org download page I downloaded and installed Gnupg Modern 2.1.15
along with the required libraries: nPth v1.2, Libgpg-error v1.25,
Libgcrypt v1.7.3, Libksba v1.3.5 and Libassuan v2.4.3. Integrity
checked them all.

After installation completed I ran gpg --version from the command line
and was presented with:
gpg (GnuPG) 1.4.18
but then saw reference online somewhere to gpg2 and figured that I
should be checking the version to that and so I ran gpg2 --version and
was presented with:
gpg: Fatal: libgcrypt is too old (need 1.7.0, have 1.6.3).

I would like to have either version at this point that works. I don't
like the idea of having misconfigured or improperly installed software
trashing up my system. If you can help me clean up my system and have
either version operational, I'd appreciate it.

I intend to use Gnupg just to encrypt and sign text and files.

Thanks in advance!

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