Re: autoconf problem building

[Tim Van Holder]

On Wed, 2002-02-13 at 20:46, Eurico de Sousa wrote:
> I rebuilt autoconf-2.52 and autoconf-2.52g, this time with --without-lispdir 
> on the configure but
> both are still giving failures on make check.

Seems that it's a single Perl error that causes every one of the
failures.

> I've attached the testsuite.log and config.log files for the 2.52g build.
> 
> I've downloaded the latest GNU Emacs but I see it has quite a few 
> dependencies so haven't built it.
> Is it better to build autoconf with the latest Emacs installed - does it 
> matter?

Not particularly; autoconf comes with a set of lisp packages that
make it a bit easier to edit autoconf files (color coding and such).
The lispdir test is to find out where they should be installed.
autoconf does not _need_ Emacs for anything (of course, [some](1) people
consider Emacs to be the One True Editor, so your life would be more
fulfilled if you have it installed :-)).

> 3. tools.at:122: testing autoconf --trace: user macros...
> tools.at:167: autoconf -t TRACE1 -t TRACE2
> 0a1
> > Unsuccessful stat on filename containing newline at 
> > /apps/asd/unix/gnu/autoconf/2.52g/autoconf-2.52g/lib/Autom4te/General.pm 
> > line 316.

Looks like either we always stat on a 'bad' filename, and this version
of SunOS is the only one to complain so far, or your setup adds
unexpected newlines to the mix.
The snapshot I have installed (some form of 2.52g) never seems to get a
filename with a newline, so it might be a bug in your Perl.

(1) Normally, I'd say "all sane people", but I wish to avoid a
    vi-vs-emacs flame war ;-)