Re: [libtool 2.2.10] testsuite: 24 102 failed

[Ralf Wildenhues]

* Donald Parsons wrote on Thu, Jun 17, 2010 at 11:23:51PM CEST:
> On Thu, 2010-06-17 at 15:30 -0500, Peter O'Gorman wrote:
> > On 06/17/2010 03:11 PM, Donald Parsons wrote:
> > > ./flags.at:24: $LIBTOOL --tag=GCJ --mode=compile $compile -c $source
> > > stderr:
> > > gcj: error trying to exec 'ecj1': execvp: No such file or directory
> > > stdout:
> > > libtool: compile:  gcj -g -O2 -c a.java
> > > ./flags.at:24: exit code was 1, expected 0
> > > 24. flags.at:24: 24. passing GCJ flags through libtool (flags.at:24): 
> > > FAILED (flags.at:24)

Just to clarify: there are two separate problems here: first, your gcj
installation is broken.  It was compiled to use the external ecj1
compiler executable, but you only have the old gcj1 one installed.
You can probably install it afterwards.

Second, the libtool test should not fail because of this: we can't fix
your gcj, so our testsuite should just skip this test if gcj doesn't
work.

> I guess the comment "Ralf has already fixed the
> detection of broken java compilers" is referring to what I have
> now noticed with your help.

This second issue has been fixed meanwhile.  For the first issue, please
consult whoever provided you with the gcj installation.

Cheers,
Ralf