lisp-implementation-version thinks clisp was built on my machine

Bug #301459 reported by sds on 2008-11-23
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
clisp (Ubuntu)
Undecided
Unassigned

Bug Description

Binary package hint: clisp

clisp 1:2.44.1-4ubuntu2

according to the docs <http://clisp.cons.org/impnotes/environment-enq.html#version> lisp-implementation-version should print the machine-instance if it was built on a different machine from mine.
instead it prints built time stamps, as if it were built on my machine.
i.e.,
GNU CLISP 2.44.1 (2008-02-23) (built 3427401796) (memory 3434581544)
instead of something like
GNU CLISP 2.43 (2007-11-18) (built on xenbuilder2.fedora.redhat.com)

sds (sds-gnu) wrote :

now I get this:
GNU CLISP 2.44.1 (2008-02-23) (built on sysu76 [67.63.55.3])
with 1:2.44.1-4ubuntu2 on Ubuntu 8.10
this is still wrong because the package was not built on my machine (sysu76).

sds (sds-gnu) wrote :

does installation of the clisp package involve dumping a new memory image?

up until 2.48 clisp using common lisp controller was indeed dumping a core as part of the installation process. This got changed for 2.49

To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.

Other bug subscribers