Re: new package proposal : CLISP

[Igor Pechtchanski <pechtcha at cs dot nyu dot edu>]

Sam,

Replies inline below.

On Tue, 9 Sep 2003, Sam Steingold wrote:

> > * In message <3F599652.7070301@lapo.it>
> > * On the subject of "Re: new package proposal :  CLISP"
> > * Sent on Sat, 06 Sep 2003 10:09:54 +0200
> > * Honorable Lapo Luchini <...> writes:
                             ^^^^^
Thanks.

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

According to <http://cygwin.com/setup.html#package_contents>, a
Cygwin-specific README is required.  Some maintainers also include port
notes and other Cygwin-specific information (e.g., package contents) in
that file (see the generic readme file on the above page for an example).
It's probably acceptable to have a one-liner referring to the
non-Cygwin-specific documentation in /usr/share/doc/clisp.

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

CYGWIN-PATCHES should contain at least the Cygwin-specific README (see
above) and setup.hint.

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

Umm, sorry, I'm not as configure-savvy as I'd like to be...  Do you use
autoconf?  If so, did you re-run it after upgrading?  It would help
knowing which versions of autotools you have installed.
	Igor
-- 
				http://cs.nyu.edu/~pechtcha/
      |\      _,,,---,,_		pechtcha@cs.nyu.edu
ZZZzz /,`.-'`'    -.  ;-;;,_		igor@watson.ibm.com
     |,4-  ) )-,_. ,\ (  `'-'		Igor Pechtchanski, Ph.D.
    '---''(_/--'  `-'\_) fL	a.k.a JaguaR-R-R-r-r-r-.-.-.  Meow!

"I have since come to realize that being between your mentor and his route
to the bathroom is a major career booster."  -- Patrick Naughton