This is the mail archive of the
java@gcc.gnu.org
mailing list for the Java project.
Re: shared libraries
- To: green at cygnus dot com
- Subject: Re: shared libraries
- From: Tom Tromey <tromey at redhat dot com>
- Date: 17 Sep 2001 09:20:44 -0600
- Cc: java at gcc dot gnu dot org
- References: <200109170126.SAA01264@fencer.cygnus.com>
- Reply-To: tromey at redhat dot com
>>>>> "Anthony" == Anthony Green <green@redhat.com> writes:
Anthony> If the class loader finds the proper .so, Class.forName() may still
Anthony> throw a ClassNotFoundException if that .so hasn't been linked with
Anthony> every .so it depends on at runtime (unless those libraries have
Anthony> already been loaded, libgcj.so).
Anthony> Is there any easier way to deal with this?
I don't know of one. I think you have to link your .so so that the
system can discover what shared libraries it requires.
As I understand it, if you use libtool to build your shared library,
and install the `.la' file, then libltdl can discover these
dependencies even on systems where you can't link shared libraries
this way.
Tom