Bug#764630: missing JNI path in jarwrapper

2014-12-03 Thread Mathieu Malaterre
On Wed, Dec 3, 2014 at 9:06 AM, Markus Koschany wrote: [...] > On a side note: jarwrapper exports LD_LIBRARY_PATH=/usr/lib/jni. Was > this ever useful because -Djava.library.path is still used? I believe you *should* try your patch on libvtk-java package. I can't remember if each and every java m

Processed: Re: Bug#764630: missing JNI path in jarwrapper

2014-12-03 Thread Debian Bug Tracking System
Processing control commands: > tags -1 patch Bug #764630 [jarwrapper] missing JNI multi-arch PATHs in jarwrapper Added tag(s) patch. -- 764630: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=764630 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems -- To UNSUBSCRIBE, emai

Bug#764630: missing JNI path in jarwrapper

2014-12-03 Thread Markus Koschany
Control: tags -1 patch Mathieu Malaterre wrote: [...] > In summary: > 1. Make jexec the default binfmts (before jarwrapper) > 2. Update jarwrapper to use the above mentionned `java -d32|64` trick > to build the library path. Hi, I think we have reached a point in the release cycle when it beco

Bug#764630: missing JNI path in jarwrapper

2014-11-25 Thread Mathieu Malaterre
On Tue, Nov 25, 2014 at 12:49 AM, Emmanuel Bourg wrote: > Le 21/11/2014 17:12, Mathieu Malaterre a écrit : > >> Maybe this is time to change the Java policy §2.4 Java libraries > >> This means that dicomscope package would install only the `jar` file, >> and the x86 or x86_64 native lib (*.so) can

Bug#764630: missing JNI path in jarwrapper

2014-11-24 Thread Emmanuel Bourg
Le 21/11/2014 17:12, Mathieu Malaterre a écrit : > Maybe this is time to change the Java policy §2.4 Java libraries > This means that dicomscope package would install only the `jar` file, > and the x86 or x86_64 native lib (*.so) can be installed whether the > user want the 32bits or the 64bits v

Bug#764630: missing JNI path in jarwrapper

2014-11-21 Thread Mathieu Malaterre
On Fri, Nov 21, 2014 at 12:23 PM, Emmanuel Bourg wrote: > On Thu, 30 Oct 2014 10:36:02 +0100 Mathieu Malaterre > wrote: > >> Currently jarwrapper is used as backend for binfmts (not sure why this >> is not jexec). Anyway the script is incomplete, now that we have >> multi-arch JNI location: > > T

Bug#764630: missing JNI path in jarwrapper

2014-11-21 Thread Emmanuel Bourg
On Thu, 30 Oct 2014 10:36:02 +0100 Mathieu Malaterre wrote: > Currently jarwrapper is used as backend for binfmts (not sure why this > is not jexec). Anyway the script is incomplete, now that we have > multi-arch JNI location: This is tricky, because if we add the multi arch path based on the ou

Bug#764630: missing JNI path in jarwrapper

2014-10-30 Thread Mathieu Malaterre
reassign 764630 jarwrapper 0.47 retitle 764630 missing JNI multi-arch PATHs in jarwrapper thanks Currently jarwrapper is used as backend for binfmts (not sure why this is not jexec). Anyway the script is incomplete, now that we have multi-arch JNI location: [...] $ tail /usr/bin/jarwrapper if [ -