LFS 6.2.26 automake-1.9.6 fails gcj4.tests

[Jesse Chisholm]

In following the LFS 6.2 process, at step 6.26: automake-1.9.6, when I get to the "make check" step, it fails one test.

Several letters back and forth with the Ralf @ automake, revealed two things: 1: gcj is never installed by the LFS process. 2: automake's gcj4.test didn't check for this.

Ralf Wildenhues <Ralf.Wildenhues@…> has started a new patch into their process, dated 2007-08-20.

Thought you'd want to know so you can be sure to get it included in the next version.

In the meantime, the one failure reported by the automake check is innocuous.

-Jesse Chisholm

[dnicholson@…]

This is confusing. I see the commit they made upstream.

​http://sources.redhat.com/cgi-bin/cvsweb.cgi/automake/tests/defs.in.diff?r1=1.39.2.1&r2=1.39.2.2&cvsroot=automake

However, what was there already should have worked (it just did for me). tests/gcj4.test sets required=gcj. It then sources ./defs, which just checks if the tools in the $required variable exist by running $tool --version. This should fail since we don't have gcj, and it will cause the rest of the test to be skipped.

I found your email with the automake maintainer.

​http://lists.gnu.org/archive/html/bug-automake/2007-08/msg00019.html

In the log, it seems that you do have gcj, but it's broken. So, I don't think we need to do anything here since in LFS we only install the C and C++ languages for GCC. Did you build gcj following the instructions in BLFS, or did you just add java to the list of languages?

Anyway, it seems that the upstream commit will fix their testsuite, but I'm afraid this isn't really an LFS issue since we don't cover the possibility of having gcj. Thanks for the report, though. If you're still trying to build gcj and having problems, try the blfs-support list.