Re: [STUMP] [OT] How do you compile clisp correctly ?

[malnourite]

On Mon, Oct 22, 2007, Daniel Clemente wrote:
>    The method in the „FAQ" at the wiki [1] isn't good because:
> - it's not always possible to „install you distro's cl-ppcre": maybe
> you must compile cl-ppcre from source, and that's a problem, since a
> fresh CLISP comes apparently without ASDF or MK (see [2])
> - common-lisp-controller doesn't always exist
> - hey, it looks like a hack...
> 
>    The instructions about compiling CLISP are to be written in [2].
> There's also a description of the problem installing cl-ppcre, which
> I'm still getting compiling stumpwm with clisp-2.42.

It is a hack. Of course CLC doesn't exist everywhere--Nor do
I [1]. It's a Wiki. Include what works for you. If everyone does
this, a more universal solution might appear. I think a hack
is perfectly appropriate here until distributors provide
ready-made packages of these modules suitable for use with
StumpWM. If your distro provides clisp-2.42 and cl-ppcre
packages, you should be all set without having to compile
anything (although at that point make-image.lisp will
require some modifications). The cl-ppcre dependency was
introduced to replace some minor functionality which was
previously dependant upon sed, and also open up the
possibility of more extensive pattern matching in StumpWM.
It is a rather unfortunate property of CL that such things
are difficult. There are simply too many implementations.
Writing portable system-level CL is about the same as
writing portable assembly--You have to address the varying
capabilities of each target separately.

[1] A peculiar individual who has encountered few things
more vexing than footnotes to emails.

-- 
Oct 22 2007,
John Moore Liles