Bug#664819: libav source build needs to link with -lgcrypt

[John David Anglin]

On 29-Apr-12, at 4:40 AM, Reinhard Tartler wrote:

> On Thu, Mar 22, 2012 at 1:30 AM, John David Anglin <dave.anglin at bell.net 
> > wrote:
>> On 20-Mar-12, at 9:54 PM, Andres Mejia wrote:
>>
>>> This issue is common if you're using the libav-extra libraries. It's
>>> likely a broken symlink from your *.so files.
>>
>>
>> I don't think so.  Updating libgcrypt11 to 1.5.0-3 fixes the build.
>>  Somehow,
>> it eliminates the dependency.
>
> I'm not sure if I understand your message. Does this mean that there
> is nothing to do in libav and we can close this bug?


In the original report,  there wasn't a broken symlink but I'm puzzled
by the message:

/lib/libgcrypt.so.11: could not read symbols: Invalid operation

Yet the linker seems to have read the symbols:
/usr/bin/ld.bfd.real: note: 'gcry_control@@GCRYPT_1.2' is defined in  
DSO /lib/libgcrypt.so.11 so try adding it to the linker command line
Note the undefined reference came from libavformat/ 
libavformat.a(network.o).  I think
that libraries need to be explicitly specified on the command line  
when linking with archive libraries.
I don't know why the archive version of libavformat was used.

With libgcrypt11 1.5.0-3, I had a successful build of the libav  
package.  There isn't a reference to the
above symbol in my installed version of libavformat.a.

Given that issue that triggered the problem is gone, I would close.

Dave
--
John David Anglin	dave.anglin at bell.net