> * In message <[EMAIL PROTECTED]> > * On the subject of "Re: new package proposal : CLISP" > * Sent on Sat, 06 Sep 2003 10:09:54 +0200 > * Honorable Lapo Luchini <...> writes: > > Binary package seems good, though it doesn't install cygwin-specific > documentation.
/usr/share/doc/clisp/* is all the doc there is. or do you want .../clisp-2.31/? (everyone is different - cygwin/RH, debian ...) > Source package: it doesn't seems to have any specific instruction nor > a CYGWIN-PATCHES subdir. nothing cygwin-specific is needed. unix/INSTALL is all you need. CLISP builds OOTB. > Last but not least, targetting cygwin-1.5.x is now a requirement, I think? Oh boy.... I upgraded to 1.5.3 last Friday and I cannot _configure_! the configure scripts fail with: ./configure --with-module=syscalls --with-module=regexp --build --fsstnd=redhat --with-module=dirkey --with-module=bindings/win32 --with-module=clx/new-clx --with-libsigsegv-prefix=/usr/local/libsigsegv-cygwin build-O ...... executing /cygdrive/d/gnu/clisp/current/build-O/avcall/configure --srcdir=../../ffcall/avcall --with-module=syscalls --with-module=regexp --with-module=dirkey --with-module=bindings/win32 --with-module=clx/new-clx --with-libsigsegv-prefix=/usr/local/libsigsegv-cygwin --cache-file=../config.cache configure: error: invalid package name: module the cause is an `expr' call which unexpectedly fails. if I add any other `expr' call right before the failing one, it works... advice?! -- Sam Steingold (http://www.podval.org/~sds) running w2k <http://www.camera.org> <http://www.iris.org.il> <http://www.memri.org/> <http://www.mideasttruth.com/> <http://www.honestreporting.com> He who laughs last did not get the joke.
