This is the mail archive of the
java-patches@gcc.gnu.org
mailing list for the Java project.
Re: 3.3.1 GCJ Cross compiler configuration issues
- From: Tom Tromey <tromey at redhat dot com>
- To: David Daney <ddaney at avtrex dot com>
- Cc: Peter Blemel <pblemel at hotmail dot com>, java-patches at gcc dot gnu dot org
- Date: 07 Apr 2004 23:32:32 -0600
- Subject: Re: 3.3.1 GCJ Cross compiler configuration issues
- References: <BAY2-F131QfwAbd5mpv00035f85@hotmail.com><40745A98.3030905@avtrex.com>
- Reply-to: tromey at redhat dot com
>>>>> "David" == David Daney <ddaney@avtrex.com> writes:
David> I delete about half of the classes from the Makefile.am and
David> then regenerate the Makefile to solve this problem.
David> You will know if you remove too many when you get errors
David> linking libgcj.so
Yuck -- we've got to find a better way than this. Eventually I'd like
to get the library splitting stuff from the gui branch into the main
line. This will be simpler once we have the binary compatibility ABI
stuff in, because at that point I think we won't have to worry about
the linking problem.
The problem being, today you don't need any special options if you
write a program using any set of core APIs, but if we just split the
library immediately, either you would have to or we'd have to link
them all in by default.
I suppose we could do the latter and have a bunch of -l options in
libgcj.spec, and then for embedded systems have `--disable-java-awt'
just drop a `-l'. If someone wanted to do an experiment like this,
that would be interesting...
Tom