Re: Fw: compile errors

2011-07-20 Thread J2C
I confirme, similar problem on gnupg-2.0.17 ___ Gnupg-users mailing list Gnupg-users@gnupg.org http://lists.gnupg.org/mailman/listinfo/gnupg-users

Re: Fw: compile errors

2010-11-02 Thread Werner Koch
On Tue, 2 Nov 2010 15:12, dcent...@ydl.net said: > Thanks for your response Heinz. However the latest version of > libassuan was compiled first and installed (as per instructions > provided in the compilation procedure of gnupg 2.0.16) before > compiling gnupg 2.0.16. See here: In any case, Gnu

Re: compile errors

2010-11-02 Thread Benjamin Donnachie
On 2 Nov 2010, at 17:16, Derick Centeno wrote: $ whereis libassuan libassuan: /usr/local/lib/libassuan.la /usr/local/lib/libassuan.so /usr/local/lib/libassuan.a $ man libassuan Which OS and distro are you using? You may need to add /usr/local/lib to your config; is libassuan listed if you run

Fw: compile errors

2010-11-02 Thread Derick Centeno
From: Derick Centeno To: Heinz Diehl Subject: Re: compile errors On Mon, 1 Nov 2010 08:52:31 +0100 Heinz Diehl wrote: > On 01.11.2010, Derick Centeno wrote: > > > ../../g10/gpg2: error while loading shared libraries: > > libassuan.so.0: cannot open shared object file: N

Fw: compile errors

2010-11-02 Thread Derick Centeno
From: Heinz Diehl To: Derick Centeno Subject: Re: compile errors On 01.11.2010, Derick Centeno wrote: > ../../g10/gpg2: error while loading shared libraries: > libassuan.so.0: cannot open shared object file: No such file > or directory You have to install libassuan first, you can ge

compile errors

2010-10-31 Thread Derick Centeno
Hi Everyone! I was compiling the latest version of gnupg 2.0.16. The configure process completed well, but the make process failed as follows: .. Making all in tests make[2]: Entering directory `/usr/src/gnupg-2.0.16/tests' Making all in openpgp make[3]: Entering directory `/usr/src/g

compile errors on Solaris 10 64bit

2010-05-03 Thread Williams, Stephen
Good evening list. I have been trying to get my compile to work and I keep getting the below error. I am only using the -disable-asm option with my configure (found that as a fix to a similar issue in this list). If anyone has any insight into this matter that would be great. Thanks, -Stephen