ports/137617: security/libgcrypt - Error: shared library "gpg-error.0" does not exist

[Hirohisa Yamaguchi]

The following reply was made to PR ports/137617; it has been noted by GNATS.

From: Hirohisa Yamaguchi <umq at ueo.co.jp>
To: bug-followup at FreeBSD.ORG, stan at dosonresorthotel.net,
        lenox.joseph at gmail.com
Cc: novel at FreeBSD.ORG
Subject: Re: ports/137617: security/libgcrypt - Error: shared library "gpg-error.0" does not exist
Date: Sun, 16 Aug 2009 09:15:18 +0900

 #  Cc:ing novel@ the maintainer of security/libgpg-error.
 ##  http://www.freebsd.org/cgi/query-pr.cgi?pr=ports/137617
 
 At Thu, 13 Aug 2009 13:28:51 -0500,
 Joseph Lenox wrote:
 > I've attempted the same build with the same issue. According to
 > libgpg-error, everything compiles and installs fine. However,
 > libgpg-error's package does complain that libgpg-error.so.0 doesn't
 > exist in /usr/local/lib on a deinstall attempt. libgpg-error's
 > install script does not attempt to make libgpg-error.so.0.
 
 > I've done a full delete (clean, distclean, make) for libgpg-error.
 
 > Looking at an older version of the ports tree (libgpg-error-1.6), I
 > see that libgpg-error.so.0 is being built, but libgpg-error.so.5 is
 > not. I symlinked libgpg-error.so.5 -> libgpg-error.so.0 and
 > libgcrypt compiled. I then ran a check over it and all of the tests
 > passed.
 
 I got new 7.2-RELEASE-p3 box, and built graphics/ImageMagick without
 any error.
  # i.e. libgpg-error.so.0 is built as expected.
 
 # It possibly is a devel/libtool problem, I'm not sure though.
 
 
 > I'm going to call that a workaround. I'm not sure where the fix
 > should be applied -- should libgpg-error create the check for the
 > difference in filename and symlink a .so.0, or should libgcrypt
 > accept either file?
 
 No, I don't think it is needed.
 
 -- 
 
 	Hirohisa Yamaguchi
 	  umq at ueo.co.jp