On Wed, Oct 1, 2008 at 9:58 AM, Hendrik Tews <[EMAIL PROTECTED]> wrote:
> Hi,
Hello,
> javax.smartcardio.TerminalFactory.{getDefault,getInstance("PC/SC")}
> both search for libpcsclite.so, which is only provided by
> libpcsclite-dev. Therefore the smartcardio package is effectively
> unusable with only libpcsclite1 installed.
>
> The fix is easy: either install libpcsclite-dev or make a link,
> for instance
> ``ln -s /usr/lib/libpcsclite.so.1 /usr/local/lib/libpcsclite.so''
> But IMHO it would be better if libpcsclite1 works out-of-the-box
> with the smartcardio package.
Loading libpcsclite.so durig execution is a bug in the JVM.
The JVM should load libpcsclite.so.1 instead.
libpcsclite.so does not provide a stable ABI. In the past it was
pointing to libpcsclite.so.0 with an API and ABI different from
libpcsclite.so.1. That is exactly why the .so file is only provided by
the -dev package. The .so file supposed to be used by the
compiler/linker at the compilation time, not at execution time.
The bug is in fact in sun-java6. Or point me to a document saying I am wrong.
Regards
--
Dr. Ludovic Rousseau
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
