Re: java library installation issues
- To: Per Bothner <per@bothner.com>
- Cc: java@gcc.gnu.org, debian-java@lists.debian.org
- Subject: Re: java library installation issues
- From: Tom Tromey <tromey@redhat.com>
- Date: 04 Apr 2001 17:52:07 -0600
- Message-id: <[🔎] 87puesrzo8.fsf@creche.redhat.com>
- Reply-to: tromey@redhat.com
- In-reply-to: Per Bothner's message of "04 Apr 2001 16:38:11 -0700"
- References: <[🔎] m23dbq6cdw.fsf@kelso.bothner.com> <[🔎] 87d7asfoaf.fsf@creche.redhat.com> <[🔎] m2y9tg9qxo.fsf@kelso.bothner.com>
>> The `L.so' in this case should probably follow the naming scheme we
>> adopted for the `.so' files that Class.forName will automatically try
>> to load. That will make it so that the linker and Class.forName will
>> agree -- it won't matter to the end program whether a class is loaded
>> at runtime or at link time.
Per> Do you have a write-up of this?
Nothing formal :-(.
Here is the comment in natClassLoader.cc:
// Turn `gnu.pkg.quux' into `gnu-pkg-quux'. Then search for a
// module named (eg, on Linux) `gnu-pkg-quux.so', followed by
// `gnu-pkg.so' and `gnu.so'. If loading one of these causes
// the class to appear in the cache, then use it.
Tom
Reply to:
- References:
- java library installation issues
- From: Per Bothner <per@bothner.com>
- Re: java library installation issues
- From: Tom Tromey <tromey@redhat.com>
- Re: java library installation issues
- From: Per Bothner <per@bothner.com>
- java library installation issues
- Prev by Date: Re: java library installation issues
- Next by Date: Re: java library installation issues
- Previous by thread: Re: java library installation issues
- Next by thread: Orphaning everything written in Java
- Index(es):