Paul NCC/CS <pts@bom.gov.au> writes:

> It's not empty, it has stuff like:

Yes, i missed that it was running 'test ! -s'; i thought it was
'test -s'.

> minitests.output.sparc--netbsdelf  contains only a small
> fraction of it after uniq:
> 
> Int f(Int,Int,Int):({1},{2},{3})->{6}
> Int f(Int,Int,Int):({1},{2},{3})->{83448}
> J f(J,int,J):({47,11},2,{73,55})->{120,68}
> J f(J,int,J):({47,11},2,{73,55})->{83448,131072}

I build this on i386 and see what's going on now.  It writes
pairs of lines to minitests.out; one line for the expected
results and one for the actual results.  Then it runs uniq -u on
that file.  If all tests passed, all the line pairs will be
identical and uniq -u will end up writing nothing; hence 'test !
-s foo' indicates whether the tests pass.

Now, looking at the lines quoted above, it looks like clisp
definitely has some problems on sparc; once it expected a 6 and
another time it expected a 120 but in both cases got 83448; looks
like overflow.

Good luck.

--  
Eric Gillespie <*> epg@pretzelnet.org

Build a fire for a man, and he'll be warm for a day.  Set a man on
fire, and he'll be warm for the rest of his life. -Terry Pratchett