Re: [MinGW] PR target/19970: Java unnecessarily disabled for MinGW in top-level configure

[David Ayers <d dot ayers at inode dot at>]

Ranjit Mathew schrieb:
> Ranjit Mathew wrote:
> 
>>>  Java and its libraries have been building for the MinGW
>>>targets since at least GCC 3.3, but they are still enumerated
>>>in noconfigdirs for MinGW targets in the top-level configure
>>>script. Because of this, libgcj is not build for MinGW
>>>even if --enable-languages lists java - an explicit
>>>--enable-libgcj is needed to overcome this. Recently,
>>>target-boehm-gc was also added to this list (and whereever
>>>else ${libgcj} was listed), exacerbating the problem.
> 
> 
> The exacerbated problem is that even --enable-libgcj doesn't
> pull in Boehm-GC and neither does --enable-java-gc=boehm.
> 
> The current situation is therefore something of a showstopper
> for Java on MinGW.

I had followed this advice which seemed reasonable:
http://gcc.gnu.org/ml/gcc-patches/2006-05/msg00886.html

But it seems --enable-libgcj is indeed used to enable java where it
isn't enabled by default where I had the impression that it was used to
--disable-libgcj it where it is.

(see also: http://gcc.gnu.org/bugzilla/show_bug.cgi?id=27963 )

I'm happy to post a patch which would remove target-boehm-gc from
noconfigdirs for the various targets for which I've added them, if that
resolves these issues.  (Note that target-boehm-gc will be re-added to
noconfigdirs dirs if it wasn't requested for Objective-C and Java is not
disabled.)

Yet I fail to understand the need for --enable/disable-libgcj if it is
merely being used to enable/disable java.  Why isn't that being done via
language variable?

Cheers,
David