Re: Serious (semi-)infinite loop

[Tim Van Holder]

> libffi wasn't originally part of the gcc tree.  We brought it into the
> tree with the rest of the Java runtime.  This code was developed
> differently and required a hacked automake (I know, I did the
> hacking...).

Naughty you - go and spank yourself :-)

> Tim> Well, that leaves me in a bind, as it makes me unable to
> Tim> configure the gcc tree.
> 
> Are you trying to use automake 1.4h on the gcc tree?  If so, that is
> very helpful.  It is the kind of testing we could use.

I have done on a few occasions. IIRC, aside from libffi, every
automake-controlled project in the gcc tree that is relevant to DJGPP
(so no libgloss or newlib or whatever) seems to work just fine with
cvs automake (currently, a 1.4i snapshot); same goes for the binutils/gdb
tree (except for the small ylwrap thing I posted about a while back).

> However, in this particular case I'm quite certain that the gcc libffi
> does some things which are not really allowed.  The right thing to do
> is fix gcc/libffi/Makefile.am so that it is more correct.  Probably
> this change can't go in until automake 1.5 is officially released :-(.
> But at the very least you could do testing with the fix in place.

If you post a "fixed" Makefile.am, I'd be glad to try it out.