pkcs11 module search paths

Stef Walter stefw at
Mon Oct 24 03:01:18 PDT 2011

On 2011-10-24 11:41, Ludovic Rousseau wrote:
> You can't set the search path at build as a configuration option.

Why not? You would just use an appropriate --with-module-path

> Because the search path depends on the CPU target you are building
> for. The search path has to be automatically detected at build time,
> not using a (fixed) command line option.

Each various architecture of p11-kit would be built using a different
command line option. Obviously p11-kit can/should only load modules from
one given architecture.

> You may have on the same filesystem p11-kit compiled for 32-bits Intel
> and another p11-kit compiled for 64-bits Intel.
> The first one will look in /usr/lib/i386-linux-gnu/pkcs11/ and the
> second will look in /usr/lib/x86-64-linux-gnu/pkcs11/


> Or maybe you want to use something like:
> --with-module-path=/usr/lib/$(dpkg-architecture -qDEB_HOST_GNU_TYPE)/pkcs11

Right, the debian packaging build of p11-kit on each architecture need
to specify a different configure argument, similar to how you would
specify --libdir.



More information about the p11-glue mailing list