-
-
Notifications
You must be signed in to change notification settings - Fork 48
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
libpcsclite.so.1 not found on NixOS #71
Comments
The whole funk in apdu4j with the library paths is to provide "works out of the box" adjustments, to not require tweaking JVM-s with library paths. So everything related to it is a bug/missing feature. Of course, things have improved a lot from JDK1.7 times... |
I have since fixed this by setting see also: NixOS/nixpkgs#46840 (comment) |
Does this have a full path or is the variable present in environment? It should work without additional java options, so please don't close the issue |
Due to the way Nix works, the variable is available during compile time; it evaluates to e.g. The |
Due to the hard-coded paths to
libpcsclite.so.1
at https://github.com/martinpaljak/apdu4j/blob/master/pcsc/src/main/java/apdu4j/pcsc/TerminalManager.java#L54 , the PC/SC library cannot be found on the NixOS Linux distribution, which does not use the Filesystem Hierarchy Standard (/lib
etc.), and instead relies on a hash-based content store.strace
reports multiple failed attempts to access the pcsc library:The correct path would be
/nix/store/0cdj8mkp03sh1yw9bnkg1sircj99scvp-pcsclite-1.9.5/lib/libpcsclite.so
, generated from the Nix statement"${lib.getLib pkgs.pcsclite}/lib/libpcsclite.so"
.I understand that supporting such edge-cases is probably not your priority, however a simple patch would maybe allow for an easy workaround: Add
libpcsclite.so.1
without any directory path to the locations to be checked, such that I can add the correct path to the library to my PATH and have the program find it. Does the library loader respect the PATH environment variable anyway?Thanks for any help or ideas.
The text was updated successfully, but these errors were encountered: