This is the mail archive of the java@gcc.gnu.org mailing list for the Java project.


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]

Re: ia64 libjava java-signal.h build failure


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

> There's supposed to be logic that turns off gcj where it's thought not
> to work.  It's OK if we simply test that logic.

But if we don't enable GCJ by default, it's that logic that won't get
tested, unless people configure --enable-languages=foo,bar,java.  I've
already done it on a number of platforms for the past 2-3 weeks, and
reported that I've encountered problems only on FreeBSD 2 (because of
a local change that caused the generic FreeBSD code to disable libjava
not to work) and AIX 4.1 (actually, on GNU/Linux/sparc too, but that
problem is already fixed).  On all other platforms, namely
GNU/Linux/x86, GNU/Linux/alpha, DU4.0D, Solaris 7/x86 and /sparc,
Solaris 2.6 and 2.5/sparc, FreeBSD 3.0, 3.4 and 4.0/x86, IRIX 6.3 and
5.2 and HP-UX 10.20, a Java-enabled build just worked out of the box.
On some platforms, libjava wasn't built, as expected per the top-level
configure rules, and configure told me it wasn't enabling those
libraries.

What else do you want me to do to get GCJ enabled by default?

-- 
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


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]