2007/11/8, Alon Bar-Lev <[EMAIL PROTECTED]>:
> This was supported once, then reverted (I don't know why).
> I agree it is better to have this on $(libdir)/pkcs11, but why
> not putting there the library itself?
>
> Also please note that you need to use $(DESTDIR)$(libdir)/pkcs11 so that
> libdir wi
Hello,
This was supported once, then reverted (I don't know why).
I agree it is better to have this on $(libdir)/pkcs11, but why
not putting there the library itself?
Also please note that you need to use $(DESTDIR)$(libdir)/pkcs11 so that
libdir will be available also to 64bit.
So you need some
2007/11/8, Ludovic Rousseau <[EMAIL PROTECTED]>:
> I propose to support the scheme described at
> http://wiki.cacert.org/wiki/Pkcs11TaskForce
My motivation to do that is that I always forget the name of the
OpenSC PKCS#11 lib.
Once again today I used /usr/lib/libopensc.so instead of
/usr/lib/open
On 11/8/07, Ludovic Rousseau <[EMAIL PROTECTED]> wrote:
> The first step is to make /usr/lib/pkcs11/opensc-pkcs11.so usable.
OK.
So do it the other way around...
Make the link in lib... :)
Alon.
___
opensc-devel mailing list
opensc-devel@lists.opensc-pr
2007/11/8, Alon Bar-Lev <[EMAIL PROTECTED]>:
> This was supported once, then reverted (I don't know why).
I could not find a reference to /usr/lib/pkcs11/ in my mails. But I
also think we already talked about that.
> I agree it is better to have this on $(libdir)/pkcs11, but why
> not putting the
Hello,
I propose to support the scheme described at
http://wiki.cacert.org/wiki/Pkcs11TaskForce
I propose the patch:
Index: src/pkcs11/Makefile.am
===
--- src/pkcs11/Makefile.am (révision 3290)
+++ src/pkcs11/Makefile.am (copie de
