On Tue, May 29, 2007 at 05:06:45PM +0200, Paolo Bonzini wrote: > > >>>>Certainly. Any compile-and-link tests won't work. > >>>I'm sorry, I missed the "and link" part of your question. Configury > >>>tests of this kind really aren't going to work. For things like tests > >>>for PIC, it's pointless: gcj supports the same options as gcc. > >>Then, does anybody know the very reason why all those tests are run > >>repeatedly for each language? > > > >I will guess. It is because the C/C++/Java/Fortran/.. compilers may > >not come from the same gcc version or based on gcc at all. > > Okay, so we have a problem. Because the patch you are proposing will > not be accepted in any way by upstream. :-(
Bulding an XXX language run-time library is a very special case. You can't build an XXX language run-time library, assuming the XXX language compiler is fully functional. If upstream libtool can support it, it is great. Otherwise, we have to do one of these 4: 1. Drop Java. 2. Drop libtool for libjava. 3. Hack libtool for libjava. 4. Hack libjava configure to work around the libtool problem. I proposed #3 with a simple and straightforward work around. We may have to keep it around forever. H.J.
