Date:	Tue, 11 Jan 2000 15:14:50 +0200 (IST)
From:	Eli Zaretskii <eliz AT is DOT elta DOT co DOT il>
X-Sender:	eliz AT is
To:	Martin Str|mberg <ams AT ludd DOT luth DOT se>
cc:	DJGPP-WORKERS <djgpp-workers AT delorie DOT com>
Subject:	Re: The test directory (djtst203.zip)
In-Reply-To:	<200001102025.VAA05824@father.ludd.luth.se>
Message-ID:	<Pine.SUN.3.91.1000111151421.19064K-100000@is>
MIME-Version:	1.0
Reply-To:	djgpp-workers AT delorie DOT com
Errors-To:	dj-admin AT delorie DOT com
X-Mailing-List:	djgpp-workers AT delorie DOT com
X-Unsubscribes-To:	listserv AT delorie DOT com

On Mon, 10 Jan 100, Martin Str|mberg wrote:

> How is it supposed to work? Should "make" result in the tests being
> run?

Yes.  But djtst was not yet revved up to be as automatic as djlsr.  In
particular, it probably doesn't work in the cross-build environment.

There's another problem with djtst: the test programs usually don't
tell you whether the results are okay or not.  You need to examine the
results and decide that by yorself.  Sometimes this decision requires
a fairly good knowledge of library internals.

If you feel like working on that, please do.

> Anyway here's two files that I'm working on to make it make in one
> go. Feedback and ideas are welcome.
> 
> ----- Start of /djgpp/tests/libc/makefile. -----
> all :
> 	-export CURDIR = `pwd`
> 	find * -type d -exec bash ${CURDIR}/cd_make.sh '{}' ';'

We usually try very hard to avoid using anything but stock djdev
binaries (and Make).  Thus, `find', Bash, and `pwd' are out.  You can
instead use the special programs (like makemake.exe, misc.exe, etc.)
written specifically for building djlsr without any other GNU tools.

- Raw text -