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

> lewy# make
> ===> Building for clisp-2.27
> cd /mnt/raid/pkgsrc_153/lang/clisp/work/clisp-2.27/src/avcall && make
> cd /mnt/raid/pkgsrc_153/lang/clisp/work/clisp-2.27/src/callback && make
> cd vacall_r; make all
> cd trampoline_r; make all
> test -d bindings || mkdir bindings
> builddir="`pwd`"; cd avcall && make && make check && make install-lib
> libdir="$builddir" includedir="$builddir"
> ./minitests > minitests.out
> uniq -u < minitests.out > minitests.output.sparc--netbsdelf
> test '!' -s minitests.output.sparc--netbsdelf

> So it's the same problem to do with some sort of test on
> minitests.output.sparc blah blah.

> I wonder if this file has been created correctly by libtool?
> I don't know.

The file is being created (> unconditionally creates the file),
but it is empty.  libtool has nothing to do with the problem
(well not this minitests.out symptom anyway), the shell creates
the file and uniq writes to it.

What does the minitests.out file contain?  Is it also empty?
What do you see when you change to that trampoline_r directory
adn run ./minitests ?

I know exactly nothing about clisp, but i thought i might help
anyway.  Are you sure clisp actually works on sparc?

--  
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