You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
It would be nice if either the config script could figure it out by itself, or I could point it at the correct library at the configuration time (rather than editing the config file).
The text was updated successfully, but these errors were encountered:
There is a strong argument to be made that p11-kit-proxy is the only thing that makes sense to be invoked automatically as a default module, and that if it's installed properly then it would do the right thing (and invoke OpenSC or whatever you have configured for the application in question).
That said, I'd tolerate a configure argument which allows you to specify it rather than only picking it up from p11-kit's pkgconfig.
$ port installed p11-kit
The following ports are currently installed:
p11-kit @0.22.1_0 (active)
Nonetheless, it did not get the required proxy installed. Therefore I think that there must be a config argument that would override the faulty (at least on my Mac OS X system) automatic discovery.
Nonetheless, it did not get the required proxy installed. Therefore I think that there must be a config
argument that would override the faulty (at least on my Mac OS X system) automatic discovery.
That's more like a bug in the installation of p11-kit in macosx rather than an issue of libp11.
Currently I have to manually edit
config.h
to make this:It would be nice if either the config script could figure it out by itself, or I could point it at the correct library at the configuration time (rather than editing the config file).
The text was updated successfully, but these errors were encountered: