ia64 libjava java-signal.h build failure

Alexandre Oliva aoliva@redhat.com
Fri Apr 20 01:14:00 GMT 2001


On Apr 20, 2001, Mark Mitchell <mark@codesourcery.com> wrote:

> Now you are being unfair.  

Sorry.  I was already kind of annoyed that I had to explicitly enable
Java for my own tests for a while, and got desperate upon the
possibility of having to do it too when installing the final release
of GCC 3.0 on 15+ platforms :-)

> I'm afraid that even if this "just works" for you on multiple boxes
> that it won't for other people, especially on less popular systems.

It's already disabled on less popular systems, and on systems in which
it hasn't been tested.  Look for ${libgcj} in assignments to
noconfigdirs in the top-level configure.in and you'll get a feeling of
what I'm talking about.  Even if we enable GCJ by default, only a few
platforms will get all of the libjava stuff built along with it.
Regardless of --enable-languages.  It's quite likely that libjava is
only enabled on platforms in which it's known to work.  By enabling
the Java language by default, we'll be making sure that to be the
case.  By not enabling it, it's quite likely that some people (myself
included) will try to build with
--enable-languages=lots,of,languages,plus,java (because there's no
other way to enable some language in addition to the default ones)
and, after the full bootstrap and libstdc++ build, will end up
learning that libjava fails to build on their platform, instead of
being told at configure time that libjava is known to be unsupported,
and thus disabled.

> So, how about we make a deal?  If you can get two independent reports
> (different people, different boxes, different administrative domains)
> for each primary platform, and one report for three other platforms,
> preferably not just different versions but actually different
> operating systems, go ahead and throw the switch.

How about doing it the other way round, taking into account that
libgcj is already disabled for almost all platforms: enable GCJ by
default, and, whenever we get a report that it fails to build on some
platform, we disable it?

-- 
Alexandre Oliva   Enjoy Guarana', see http://www.ic.unicamp.br/~oliva/
Red Hat GCC Developer                  aoliva@{cygnus.com, redhat.com}
CS PhD student at IC-Unicamp        oliva@{lsd.ic.unicamp.br, gnu.org}
Free Software Evangelist    *Please* write to mailing lists, not to me



More information about the Gcc-bugs mailing list