Re: Linker name conflicts due to optimization in gjavah

[Terry Laurenzo <tlaurenzo at gmail dot com>]

> I wonder what changed in 4.1. GCJ for MinGW used to build just
> fine in 3.4 and 4.0, IIRC, no?
Since building a dll isn't supported out of the box on MinGW, GCJ
still builds without error.  It just produces a static archive that
causes linkage errors if you use any of the affected classes. 
Currently the only affected class I found was
java.util.logging.Logger, which was being pulled in implicitly from my
use of commons-logging.  The problem stems from natLogger.cc which was
only added in February of this year.

There could be other infrequently used problem classes out there, so
we need to figure out what the root cause is and correct it.

I unfortunately don't have the intermediate .o files from that build
anymore.  Is there anything I could grep out of libgcj.a that would
help you identify the problem?

> Well, my home PC is even "humbler" (P3 750MHz, 512MB RAM) but
> I manage to do a native bootstrap of C, C++ and Java in around 150-
> 160 minutes on Linux. If you have Linux, you can try the crossed-native
> build approach as given in:

I did my first three builds of the entire suite on a P2 450MHz, 256MB
RAM because it had Linux already installed.  I intermixed a camping
trip to the mountains with the experience.  I've since switched to a
coLinux Debian install on my Windows laptop which is quite a bit
faster.  If I get a chance, I'll write up some instructions on
installing coLinux for this purpose.

TJ