Date:	Wed, 15 Dec 1999 09:04:27 +0200 (IST)
From:	Eli Zaretskii <eliz AT is DOT elta DOT co DOT il>
X-Sender:	eliz AT is
To:	Ansgar Duelmer <gec3 AT c2 DOT hrz DOT uni-giessen DOT de>
cc:	djgpp AT delorie DOT com
Subject:	Re: Q: autoconf-2.14a
In-Reply-To:	<835dqi$je6@c4.hrz.uni-giessen.de>
Message-ID:	<Pine.SUN.3.91.991215085856.18491E-100000@is>
MIME-Version:	1.0
Reply-To:	djgpp AT delorie DOT com
X-Mailing-List:	djgpp AT delorie DOT com
X-Unsubscribes-To:	listserv AT delorie DOT com

On 14 Dec 1999, Ansgar Duelmer wrote:

> i need autoconf-2.14a to configure a programm. has anybody the "binary"
> for this script? i have the sources, but can't compile them, course 
> "make check" fails, and if i install it, autoconf fails, too.

How about posting the error messages here, together with the relevant 
fragments of the scripts/programs that fail?

In general, you shouldn't need "make check" to succeed in order to 
install and use a GNU package.  "make check" runs the test suite supplied 
with the package, but passing the tests is not a prerogative for a 
successful build and installation.  

Also, many test suites that fail in the DJGPP environment simply stumble
on the DOS- vs Unix-style of end-of-line format (because the use `cmp' to
compare the expected output with the actual one).  So if you really want 
the test suite to succeed, you might consider looking into the specific 
causes of the failures.  I'd be surprised if the test suite were 
responsible for the installation problems, though.

- Raw text -