On Tue, May 29, 2007 at 06:47:07AM -0700, H. J. Lu wrote: > On Tue, May 29, 2007 at 09:07:49AM +0200, Paolo Bonzini wrote: > > > > >This patch allows me to run aclocal and autoconf. However, it still > > >doesn't work. But we can't use conftest* as Java class file name since > > >it will be removed after a test is done. That means the second gcj > > >test will fail since those class files have been removed. If we > > >rename them to something else, we should remove them after all gcj > > >tests are done. > > > > Sounds like a nice plan. Can you finish it? > > 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. H.J.
