Re: Bug 191256 - [PATCH] security/libgcrypt: update to 1.6.1

2014-07-06 Thread Kurt Jaeger
Hi! Log see http://people.freebsd.org/~pi/misc/build-libgcrypt.txt Hmm. I'm a bit confused now. I checked the newly linked libgcrypt.so.20 (located in src/.libs) and it seems to have all of the missing symbols in its symbol table, but all are undefined. I ran nm -D on the file and: The

Re: Bug 191256 - [PATCH] security/libgcrypt: update to 1.6.1

2014-07-06 Thread Kurt Jaeger
Hi! Log see http://people.freebsd.org/~pi/misc/build-libgcrypt.txt Hmm. I'm a bit confused now. I checked the newly linked libgcrypt.so.20 (located in src/.libs) and it seems to have all of the missing symbols in its symbol table, but all are undefined. I ran nm -D on the file and:

Re: Bug 191256 - [PATCH] security/libgcrypt: update to 1.6.1

2014-07-05 Thread Kevin Oberman
On Sat, Jul 5, 2014 at 1:03 AM, Kurt Jaeger p...@opsec.eu wrote: Hi! I was just wondering if this port could please be committed. I tried to build it on 10.0-amd64 and it failed to compile. Log see http://people.freebsd.org/~pi/misc/build-libgcrypt.txt Do you have hints on what I can do

Re: Bug 191256 - [PATCH] security/libgcrypt: update to 1.6.1

2014-07-05 Thread Kevin Oberman
On Sat, Jul 5, 2014 at 3:50 PM, Kurt Jaeger li...@opsec.eu wrote: Hi! I was just wondering if this port could please be committed. I tried to build it on 10.0-amd64 and it failed to compile. Log see http://people.freebsd.org/~pi/misc/build-libgcrypt.txt You might try deleting

Bug 191256 - [PATCH] security/libgcrypt: update to 1.6.1

2014-07-04 Thread Jerry
Fri, 4 Jul 2014 13:19:27 -0400 I was just wondering if this port could please be committed. -- Jerry signature.asc Description: PGP signature