This is the mail archive of the
java-discuss@sources.redhat.com
mailing list for the Java project.
RE: static linking
- To: "'Bryce McKinlay'" <bryce at albatross dot co dot nz>, Jeff Sturm <jeff dot sturm at appnet dot com>
- Subject: RE: static linking
- From: Anthony Green <green at redhat dot com>
- Date: Tue, 5 Dec 2000 23:04:45 -0800
- Cc: "java-discuss at sources dot redhat dot com" <java-discuss at sources dot redhat dot com>
- Organization: Red Hat, Inc.
- Reply-To: "green at cygnus dot com" <green at cygnus dot com>
Bryce wrote:
> Hmm. Works for me. libtool should figure it out based on the -lsupc++ flag
> that is passed to it:
FWIW, the last time I tried this I got the same results as Jeff. I didn't
report it as it seemed like people were still shaking out bugs from libstdc++
and libsupc++, but perhaps this is a real problem.
Jeff wrote:
> 2) classes loaded dynamically (via Class.forName) don't get linked
>
> I don't see any good solution. I got around it by linking the following
dummy
> class into my executable, but YMMV:
Hmm.. won't the class loader rummage around in appropriately named shared
libraries? What happens when you make a symlink from libgcj.so to gnu-gcj.so?
AG