This is the mail archive of the
java-patches@gcc.gnu.org
mailing list for the Java project.
Re: patches to re-direct _Jv_RegisterClass
- To: "Anthony Green" <green at redhat dot com>
- Subject: Re: patches to re-direct _Jv_RegisterClass
- From: Tom Tromey <tromey at redhat dot com>
- Date: 17 Jul 2001 18:59:36 -0600
- Cc: "Per Bothner" <per at bothner dot com>, <java-patches at gcc dot gnu dot org>
- References: <m2u218owwn.fsf@kelso.bothner.com> <871yocarlq.fsf@creche.redhat.com> <m2n16y4g3v.fsf@kelso.bothner.com> <87lmmh3g6a.fsf@creche.redhat.com> <m2ofrdbqu0.fsf@kelso.bothner.com> <87r8vtsvl5.fsf@creche.redhat.com> <000001c1069a$9ff5c960$5be6b4cd@cygnus.com>
- Reply-To: tromey at redhat dot com
>>>>> "Anthony" == Anthony Green <green@redhat.com> writes:
Anthony> FYI, I filed a PR against our current scheme recently. I put
Anthony> it against "libgcj", although most people appear to just be
Anthony> using "java". Is that what I should have done?
Using libgcj is fine. `java' is ostensibly for front-end bugs.
In practice I think all the Java hackers look at both.
I've closed the PR you filed.
Anthony> Also, our current scheme uses library names foo-bar-class.so.
Anthony> This is inconvenient if you need to link against them
Anthony> (-lfoo-bar-class doesn't work). Should we change these to
Anthony> libfoo-bar-class.so? Or libgcj-foo-bar-class.so?
This will probably work automatically. We use libltdl to open .so's.
We just pass in something like `foo-bar-class'. It handles mapping
that to the system name. So I don't think we need to make any change
(though I haven't tested it).
Tom