Re: using ssl and pkg-config in a package

["Julio M. Merino Vidal" <jmmv84%gmail.com@localhost>]

On 9/3/06, Steven M. Bellovin <smb%cs.columbia.edu@localhost> wrote:
> I'm trying to put together a package -- more accurately, I'm trying to
> update a package -- that uses openssl.  The configure script uses
> pkg-config to test for openssl; that test fails, presumably because
> it's in the base system rather than a package.  What's the usual fix?  (Is
> there one, short of a weird patch to the configure script?)  There is a
> buildlink reference to openssl in the Makefile.

OpenSSL installs an openssl.pc file in multiple systems but it does
not in NetBSD.  Most programs out there take this into account and, if
the .pc file is not installed, they later try to locate the library
using AC_CHECK_LIB.  It is possible that the package you are dealing
with has removed this last part...  if so:

The best way to fix this in pkgsrc could be to make openssl's
buildlink3.mk file generate a fake openssl.pc file in the buildlink
directory (when the file was not available).  This way packages would
always find the .pc file even if the base system did not provide it.
See the xextproto-fake-pc target in xextproto's builtin.mk file for an
example.

(And the best way to fix this upstream could be to tell the author
that openssl.pc is not always available even if OpenSSL is installed.)

Cheers,

--
Julio M. Merino Vidal <jmmv84%gmail.com@localhost>
The Julipedia - http://julipedia.blogspot.com/