[CM] Installing CM under Cygwin on Windows XP

Rick Taube taube@uiuc.edu
Mon, 3 Nov 2003 16:02:40 -0600

I finally got cygwin installed at home on my old dell. To get CM to
compile in Cygwin/clisp, edit the file src/cm.lisp and change the lines

#+(and clisp unix)
(if (find ':pc386 *features*)


#+(and clisp unix)
(if (or (find ':pc386 *features*)
	(find ':cygwin *features*))

That's it Ill commit the change to CVS tomorrow morning when Im at work.
Ill make a new tarball as soon as I fix a listener.el bug in

> -----Original Message-----
> From: cmdist-admin@ccrma.Stanford.EDU 
> [mailto:cmdist-admin@ccrma.Stanford.EDU] On Behalf Of James Ravan
> Sent: Tuesday, October 28, 2003 5:19 PM
> To: cmdist@ccrma.Stanford.EDU
> Subject: Re: [CM] Installing CM under Cygwin on Windows XP
> > > *** - The value of TOK must be one of DARWIN, LINUX
> > > The value is: CYGWIN_NT-5.1
> > >
> >
> > Well this is certainly a "bug" -- ive only tried cm in 
> Guile / cygwin
> > and it did work there.
> > But I don't think this is the problem you originally 
> posted. That one
> > seems like an end of line problem, as Ralf suggested.
> AHA! I think I understand what the original problem was. 
> CLISP seems to be
> reading the terminal in what I call "raw" mode, that is, including
> keystrokes like <backspace>. Depending on where I edited the 
> load command
> with <backspace> characters, I could get CLISP to return all 
> sorts of error
> messages, including the original one I mentioned.
> So given that, what can I do about the real bug above? And if 
> anyone else
> uses CLISP, what's going on with input editing?
> regards,
> -jim
> _______________________________________________
> Cmdist mailing list
> Cmdist@ccrma.stanford.edu
> http://ccrma-mail.stanford.edu/mailman/listinfo/cmdist