Running Eclipse with 3.4's gij

Andrew Haley aph@redhat.com
Fri Mar 26 13:03:00 GMT 2004


Anthony Green writes:
 > 
 > 	To run Eclipse with 3.4's gij, you will probably want to set the
 > gnu.gcj.runtime.VMClassLoader.library_control property...
 > 
 > GCJ_PROPERTIES="gnu.gcj.runtime.VMClassLoader.library_control=never" ~/eclipse/eclipse/eclipse -vm gij
 > 
 > 	Selecting the Help menu fires up tomcat and, on my system, libgcj
 > starts loading the RHEL3 versions of lib-org-apache-*, etc.
 > which are incompatible.
 > 
 > 	I was able to run Eclipse with no obvious problems after setting this
 > property.
 > 
 > 	I realize that some day we may have a new ABI that should
 > solve problems like this, but I'm thinking that it might also make
 > sense for libgcj to only load libraries from a compiler specific
 > directory. What do you think?
No, it's a bad idea to change this now. The new ABI is closer than
you think. I don't think we want to change this behaviour twice
between gcc 3.4 and 3.5.
IMO, it's quite legitimate to keep .so files in the same directory as
.jar files. One alternative I'm considering is perhaps to put them in
a subdir.
Andrew.


More information about the Java mailing list

AltStyle によって変換されたページ (->オリジナル) /