Mail Archives: djgpp-workers/2000/01/11/09:27:11
Eli said:
> 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.
Yeah, but the plan was to generate a log file of the output of make,
then do my FAT32 changes and running it again and diff the log files.
If the making starts to work perhaps a log file from DJ should be
added (to djtst), as "this_worked_at_DJs_compilation.log"?
> 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.
Yeah, but the test suite (djtst) isn't djlsr!
As my hack is working for me, I'll probably not work on it any more
(at least not now). This is partly because I don't understand the
structure and the roles of these programs. If there was some
description of this, the likelyhood of me trying to make it work would
increase.
Right,
MartinS
- Raw text -