Re: PATCH: PR libjava/32098: New libtool doesn't support libjava

[H. J. Lu]

On Tue, May 29, 2007 at 04:21:22PM +0200, Paolo Bonzini wrote:
> 
> >>It doesn't work since gcj isn't functional at that time. configure
> >>complains
> >>
> >>configure:16060: /export/build/gnu/gcc-isa/build-x86_64-linux/gcc/gcj 
> >>-B/export/build/gnu/gcc-isa/build-x86_64-linux/x86_64-unknown-linux-gnu/libjava/
> >> -B/export/build/gnu/gcc-isa/build-x86_64-linux/gcc/ -c -O2 -g -O2 -fPIC 
> >>@conftest.list >&5
> >>gcjtest_compile.java:0: error: cannot find file for class java.lang.Object
> >>gcjtest_compile.java:0: error: cannot find file for class java.lang.Object
> >>gcjtest_compile.java: In class 'gcjtest_compile':
> >>gcjtest_compile.java: In constructor '()':
> >>gcjtest_compile.java:0: error: cannot find file for class
> >>java.lang.Object
> >>gcjtest_compile.java:0: error: class 'java.lang.Object' has no method 
> >>named '<init>' matching signature '()V'
> >>gcjtest_compile.java:0: confused by earlier errors, bailing out
> >
> >Since C and C++ are the only compilers available when building
> >libjava, we can't use anything else to test gcj features. Classpath
> >is a little different since libtool.m4 in classpath isn't really used
> >by libjava, it doesn't need my hack.
> 
> You need to pass -fclasspath= -fbootclasspath=$srcdir/classpath/lib 
> -fbootstrap-classes, or something like that.  Which I didn't know before 
> writing this message; I just grepped libjava/Makefile.am for GCJFLAGS.
> 
> Your complaining is based on a false hypothesis.  gcj *is* functional as 
> a bytecode-to-native compiler when building libjava; and it is also 
> functional as a source-to-native compiler only if you have ecj installed.

See

http://gcc.gnu.org/ml/gcc-patches/2007-05/msg01986.html

Gcj isn't available for compile-and-link test when building libjava.


H.J.