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.con
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.gn
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
D
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
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 wi
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
