hi list, anyone ever notice that the clisp package is almost empty? it's a mere 251kB, while the x86 version of slackware 12 is 11.2MB. i've tried running the Slackbuild script for clisp, and it builds the package just fine, but i again ended up with a broken package. doing some digging, i found the following. if i go into /tmp/clisp-2.41/with-gcc-wall/, the directory where the actual compilation takes place, and then issue 'make install DESTDIR=/tmp/package-clisp, i get the following error: ===================== for f in clisp-link linkkit/* base/* full/*; do \ case $f in \ */lisp.run) /usr/bin/ginstall -c $f /tmp/package-clisp/usr/lib/clisp/$f;; \ *) /usr/bin/ginstall -c -m 644 $f /tmp/package-clisp/usr/lib/clisp/$f;; \ esac; \ done /usr/bin/ginstall: cannot stat `base/*': No such file or directory /usr/bin/ginstall: cannot stat `full/*': No such file or directory make: *** [install-bin] Error 1 ===================== indeed, there are no directories base/ and full/ in with-gcc-wall/. in fact, they do not exist anywhere in the source tree clisp-2.41/. i don't have time to look into this further ATM, but something strange is definitely going on. i mean, Pat aparently used the same Slackbuild script to build his package, so why is that one ok? -- Joost Kremers Life has its moments