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.
-- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/838187 Title: libgcrypt-config provides an inconsistent result To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libgcrypt11/+bug/838187/+subscriptions -- ubuntu-bugs mailing list [email protected] https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
