Hi Anri, your only "way out" that I see is to link **everything** statically, including a rebuild of openssl with the engine-pkcs11 library in place. Especially this last part will be particularly tricky. I've built engine-pkcs11.so with a statically linked opensc-pkcs11.so without any problems - IIRC it was just a matter of - building opensc-pkcs11 - removing the opensc-pkcs11.so file (so that only the .a remains) - linking engine-pkcs11.so against opensc-pkcs11
HTH, JJK Anri Lau wrote: > Hello Jan > > Thanks for your reply. You are right. Plugining the engine to the > openssl will be a great problem, but engine-pkcs11 load the > opensc-pkcs11.so using libtool, too. If i disable the opensc's dynamic > linking capablity, does it still work well. How should handle this > problem, could you give me some suggestion? > > On 21/02/2008, *Jan Just Keijser* <[EMAIL PROTECTED] > <mailto:[EMAIL PROTECTED]>> wrote: > > Hi Anri, > > opensc and libtool rely on the autoconf 'configure' scripts; as > long as > the 'configure' script detects that dynamic linking is not > supported on > uclinux you should be fine. > however, what do you intend to do with engine-pkcs11 without > dynamic lib > support? engine-pkcs11 is primarily intended to be loaded as a shared > library inside an openssl session... > > HTH, > > > JJK > > > Anri Lau wrote: > > Hello All > > > > I need to install the opensc on UClinux. But UClinux does not > support > > dynamic linking. I know, the opensc depend on the Libtool. > > My question is libtool will work well on uclinux? > > If not is there solution for it? > > > > how about the engine-pkcs11 and libp11 installation on uclinux? > > > > _______________________________________________ opensc-devel mailing list opensc-devel@lists.opensc-project.org http://www.opensc-project.org/mailman/listinfo/opensc-devel
