Work at SourceForge, help us to make it a better place! We have an immediate need for a Support Technician in our San Francisco or Denver office.

Close

#19 Compiling clisp.lisp fails on CLISP 2.35

open
nobody
Installer (1)
5
2005-10-26
2005-10-26
stranger
No

Installing from jabberwocky.1.4.2.0.40.bin.tgz on Linux
2.6.11 with CLISP 2.35 fails, giving the following:

<0> INTERN("PROGRAM-ID"): #<PACKAGE SYSTEM> is locked

At line 121 of clisp.lisp, you have_

(defun get-process-id ()
#-:WIN32 (SYSTEM::PROGRAM-ID))

In CLISP 2.35, (SYSTEM::PROGRAM-ID) is undefined.

Section 32.10 of the implementation notes for CLISP
2.35 (http://clisp.cons.org/impnotes/syscalls.html)
lists (OS:PROCESS-ID) as the function to retrieve the
process-id.

Changing (SYSTEM::PROGRAM-ID) to (OS:PROCESS-ID)
corrects the problem. Assuming that
(SYSTEM::PROGRAM-ID) functioned correctly on previous
versions of CLISP, I leave it to you to determine
exactly how to check the version and call the
appropriate function for each case. I imagine it would
involve checking with (LISP-IMPLEMENTATION-VERSION).

Installation then fails, reporting in a dialog box:

"[Installation] failed to create [the] startup script
for Jabberwocky. Do you have enough rights in the
directory [HOME]/bin/Jabberwocky?"

The Install log shows _

<0> ;; Loading file clisp/debugcode.fas ...
<1> ;; Loaded file clisp/debugcode.fas
<1> Bye.
<1>

Afterward, the installation directory is empty, and the
script directory hasn't changed. I do own both the
installation directory and the working directory, and
the installation directory has the permissions
rwxr-xr-x. I haven't identified the problem, but I
haven't looked at it very closely.

Discussion