The integrated cross-platform development tool for ANSI Common Lisp LispWorks logo

Lisp Knowledgebase



Title: LispWorks for Linux executable corrupted after installation

ID: 17046


Product: LispWorks for Linux
Version: All
OS: Linux

Description: After an initially successful installation of LispWorks for Linux, the LispWorks executable appears to be corrupted and is reduced in size, as shown:

$ lispworks
Lisp executable apparently corrupted. (Truncated?) Cannot restart.
$ ls -la /usr/lib/LispWorks/
total 216
dr-xr-xr-x   3 root root   4096 Oct  5 04:02 .
drwxr-xr-x  24 root root   4096 Oct  4 09:51 ..

dr-xr-xr-x   3 root root   4096 Oct  4 09:51 lib
-r-xr-xr-x   1 root root  35721 Jul 24 19:52 lispworks-5-0-0-x86-linux
-r-xr-xr-x   1 root root  35721 Oct  4 10:31 lispworks-tty
-r--r--r--   1 root root 103745 Jul 26 15:38 readme-5-0


This problem has been seen on machines running Red Hat Enterprise Linux 4 and Fedora core 3.
It is caused by the prelink cron job, which does not understand LispWorks executables.

Another error message seen attempting to run a saved LispWorks executable on Fedora 14 was

Reading LispWorks file lw-6-0-1: failed to find trailer, error -101

See Also:
Workaround: Add descriptions of your Lisp executables to the end of the file /etc/prelink.conf. For example, this will match the default names:

-b lispworks-*-linux

The truncated executables need to be reinstalled.

As of version 5.1 the LispWorks for Linux rpm installer writes a line in /etc/prelink.conf which protects the released image. However this does not protect LispWorks images or runtime exectables that you have saved, because the name will differ. If you distribute LispWorks for Linux runtimes you should consider protecting them adding a suitable line in /etc/prelink.conf at install-time
Patch:

Hardware:N/A
Summary:
Bug#:
Patch Enhancement#:
Reported:

Top | Back