Why p11-kit-1 instead of p11-kit?

[Jim Lloyd]

I configure and install p11-kit using the usual incantation:

./configure && make && sudo make install

This seems to run without errors. However, 'make check' does report one
test failure. I logged that failure:
https://bugs.freedesktop.org/show_bug.cgi?id=47374

Anyway, I would expect that the usual incantation should be enough to
locate p11-kit when I configure GnuTLS. But it isn't able to find it. I've
never needed to use pkg-config before so its still a bit mysterious to me,
but I would expect that after installing p11-kit that one of these two
commands would output something useful:

$ pkg-config --libs p11-kit
$ pkg-config --libs p11-kit-1

Both produce an error like this one (for the 2nd command above):
Package p11-kit-1 was not found in the pkg-config search path.
Perhaps you should add the directory containing `p11-kit-1.pc'
to the PKG_CONFIG_PATH environment variable
No package 'p11-kit-1' found

Is there some reason why I have to do something beyond the usual
incantation when installing p11-kit?

Thanks,
Jim

On Fri, Mar 16, 2012 at 12:01 AM, Nikos Mavrogiannopoulos
<nmav at gnutls.org>wrote:

> On 03/15/2012 10:41 PM, Jim Lloyd wrote:
>
> > Sorry to bug the list with this question, but this seems to be a case
> where
> > Google does not know all.
> >
> > I'm attempting to build gnutls 2.12.17 on CentOS 6.0 x86-64. I'm doing
> this
> > specifically for PKCS11 support, which we are adding to an existing
> product.
> >
> > I have built and installed p11-kit 0.12. But when I configure gnutls I
> get
> > this error:
> >
> > checking for P11_KIT... configure: error: Package requirements (p11-kit-1
> >> = 0.11) were not met:
> > No package 'p11-kit-1' found
> >
> > Why p11-kit-1 instead of p11-kit? Does this indicate that I need a forked
> > variant of p11-kit?
>
>
> Not really. p11-kit advertises itself as p11-kit-1. You might want to
> check config.log for the reason of non-detection.
>
> regards,
> Nikos
>
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: </pipermail/attachments/20120316/e45e9cb2/attachment.htm>