Hi Tudor,
<br/><br/>some progress in Pharo 5:
<br/><br/>&gt; Am 28.07.2015 um 16:10 schrieb Tudor Girba-2 [via Smalltalk] &lt;<a href="/user/SendEmail.jtp?type=node&node=4841798&i=0" target="_top" rel="nofollow" link="external">[hidden email]</a>&gt;:
<br/>&gt; 
<br/>&gt; I also tried with Pharo4 and Pharo5, but it does not work because I get a MNU for GhostClassBuilder&gt;&gt;#client:.
<br/>&gt; 
<br/>&gt; I fixed it in a Pharo5 image by using #installer: instead, but the computation of &quot;JVM newWithSettings: jvmSettings&quot; does not seem to finish and it blocks the VM.
<br/><br/>Changing the call of #client: to #installer: in GhostClassInstaller&gt;&gt;#initialize: was correct.
<br/><br/>&gt; Any idea of what goes wrong?
<br/><br/>Someone declared String&gt;&gt;subStrings: &nbsp;as deprecated in Pharo 4 or 5. When I ran ���JVM newWithSettings: jvmSettings���, a notifier opened which warned about the deprecated method. I changed the method which used it in the debugger, then proceeded. The image blocked until I hit &lt;cmd-.&gt;. A debugger opened, it was in the middle of writing to the Pharo error log file. I proceeded, the image blocked again, I hit &lt;cmd-.&gt; again. A debugger opened which contained a very large stack of contexts with the method handleSignal: calling itself endlessly. There seems to be something wrong with handling/logging deprecation warnings in Pharo 5. Why do they have to be written to the error log in the first place? I don���t think that they belong there.
<br/><br/>There are four methods sending subStrings: in the package JNIPort-Java-Base. I changed them to use substrings: instead. 
<br/><br/>There are two methods in JNIPort-StringEncoding which send &quot;Smalltalk isLittleEndian���, String&gt;&gt;#asJavaLangStringEncodedByteArray and String&gt;&gt;#fromJavaLangStringEncodedByteArray:. This does not work anymore. I replaced this with &quot;EndianDetector isLittleEndian���.
<br/><br/>After these changes, starting a JVM and executing the example script which you posted just worked fine.
<br/><br/>Unfortunately, loading the test package JNIPort-Tests-Java-Base fails with an exception:
<br/><br/>UTF8InvalidText(Object)&gt;&gt;subclassResponsibility
<br/>UTF8InvalidText(Exception)&gt;&gt;defaultAction
<br/>UndefinedObject&gt;&gt;handleSignal:
<br/>Context&gt;&gt;handleSignal:
<br/><br/>AFAIK, there was no problem when loading the package in Pharo 3. There seem to be two problems: The UTF8TextConverter seems to think that there is an invalid character in the source code file, and UTF8InvalidText has no #defaultAction method. Looks like a bug in Pharo 5 to me.
<br/><br/>HTH
<br/>Joachim
<br/><br/>

	
	
	
<br/><hr align="left" width="300" />
View this message in context: <a href="http://forum.world.st/troubles-with-JNIPort-on-Pharo-5-Java-8-tp4836922p4841798.html">Re: troubles with JNIPort on Pharo 5 / Java 8</a><br/>
Sent from the <a href="http://forum.world.st/Pharo-Smalltalk-Users-f1310670.html">Pharo Smalltalk Users mailing list archive</a> at Nabble.com.<br/>