libgcrypt-config provides an inconsistent result

Bug #838187 reported by Guillaume Emont on 2011-08-31
This bug affects 1 person
Affects Status Importance Assigned to Milestone
libgcrypt11 (Ubuntu)

Bug Description

On ubuntu 11.04, libgcrypt-config gives the following linking parameters:
$ libgcrypt-config --libs
-L/lib/x86_64-linux-gnu -lgcrypt
But there is no in /lib/x86_64-linux-gnu:

$ /sbin/ldconfig -p | grep$ (libc6,x86-64) => /usr/lib/x86_64-linux-gnu/ (libc6) => /lib32/

This means that any project using libgcrypt-config or AM_PATH_LIBGCRYPT() to compile against gcrypt will fail to compile.

Revision history for this message
Andreas Metzler (k-launchpad-downhill-at-eu-org) wrote :

This is fixed in libgcrypt11 (1.5.0-1) .

Just out of interest, does /this/ really break compilation in "any project using libgcrypt-config or AM_PATH_LIBGCRYPT()"? Both /lib/x86_64-linux-gnu and /usr/lib/x86_64-linux-gnu are in the standard gcc search path, the -L argument is superfluous. (The libtoool related breakage is a different bug - LP #751142 )

Revision history for this message
Guillaume Emont (guijemont) wrote :

I realised later that compilation breakage only happens under particular conditions.
In my case, I was compiling a project under jhbuild, with libgcrypt being the only dependency taken from the system, so that their was no -L/usr/lib/x86_64-linux-gnu in the command, which makes me wonder whether it is really in the default search path (or was jhbuild/my project passing some magical option to reset that path?)

Revision history for this message
Guillaume Emont (guijemont) wrote :

In most cases, I guess that code being compiled against ubuntu's libgcrypt is also compiled against some other library in /usr/lib/<arch triplet>/, which allowed this bug to remain unnoticed so far.

To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.

Other bug subscribers