All Manuals > LispWorks Release Notes and Installation Guide > 4 Installation on Linux

NextPrevUpTopContentsIndex

4.4 Installing LispWorks for Linux

4.4.1 Main installation and patches

The LispWorks 7.1 installer contains each of the Editions. Additionally, there may be a patch installer which upgrades LispWorks to version 7.1.x. You need to complete the main installation before adding patches.

4.4.2 Information for Beta testers

Users of LispWorks 7.1 Beta should completely uninstall it (including any patches added to the beta installation) before installing LispWorks 7.1.

See Uninstalling LispWorks for Linux for instructions.

4.4.3 Installation from the binary RPM file (x86 and x86_64 only)

For installation on ARM and ARM64, see Installation from the tar files.

We recommend that you use RPM 4.3 or later (however see below for problems with --prefix argument with some versions of RPM). The distribution files are also provided in tar format in case you do not have a suitable version of RPM or are using another distribution of Linux.

If you already have LispWorks 7.1 Beta installed, please uninstall it before installing this product. See Uninstalling LispWorks for Linux.

Some versions of RPM may cause problems (eg. RPM 3.0). If you get the following message when using the --prefix argument:

rpm: only one of --prefix or --relocate may be used

try upgrading to RPM 3.0.2 or greater.

Installation of LispWorks for Linux from the RPM file must be done while you are logged on as root.

4.4.3.1 Installation directories

By default 32-bit LispWorks is installed in /usr/lib/LispWorks and a symbolic link to the executable is placed in /usr/bin/lispworks-7-1-0-x86-linux. Similarly, 64-bit LispWorks is installed in /usr/lib64/LispWorks and a symbolic link to the executable is placed in /usr/bin/lispworks-7-1-0-amd64-linux. However, the RPM is relocatable, and the --prefix option can be used to allow the installation of LispWorks in a non-default directory. The default prefix is /usr.

Note: RPM version 4.2 has a bug which can hinder secondary installations (CLIM, Common SQL, LispWorks ORB or KnowledgeWorks) in a user-specified directory. See RPM_INSTALL_PREFIX not set for a workaround.

Note: the Personal Edition installs by default in /usr/lib/LispWorksPersonal. Do not attempt to to install different editions in the same location, since some filenames coincide and uninstallation may break.

4.4.3.2 Selecting the correct RPM files

The main RPM file in the LispWorks distribution is named using the following pattern

lispworks-7.1-n.arch.rpm

The integer n denotes a build number and will be same in all files in your distribution. The string arch will be either i386 for 32-bit LispWorks or x86_64 for 64-bit LispWorks. The text below assumes 32-bit LispWorks.

Note: For the Personal Edition, use lispworks-personal-7.1-*.i386.rpm wherever lispworks-7.1-*.i386.rpm is mentioned in this document. See Personal Edition for more information specific to the Personal Edition.

4.4.3.3 Installing or upgrading LispWorks for Linux

To install or upgrade LispWorks from the RPM file, perform the following steps as root:

  1. Follow the instructions under License agreement.
  2. Locate the RPM installation file lispworks-7.1-n.i386.rpm.
  3. Install or upgrade LispWorks in the standard RPM way, for example:
  4. rpm --install lispworks-7.1-n.i386.rpm

    This command installs LispWorks in /usr/lib/LispWorks. A command line of the form

    rpm --install --prefix <directory> lispworks-7.1-n.i386.rpm

    installs LispWorks in <directory>.

The directory name must be an absolute pathname. Relative pathnames and pathnames including shell-expanded characters such as . and ~ do not work.

Note: LispWorks needs to be able find its library at run time and therefore the LispWorks installation should not be moved around piecemeal. If you simply want to run LispWorks from somewhere more convenient, then consider adding a symbolic link.

See Running LispWorks for instructions on entering your license details.

4.4.3.4 Installing CLIM 2.0

The following module is packaged as a separate RPM file for installation after the main lispworks package. It is available in LispWorks Professional and Enterprise Editions only.

File distributions for layered products in Professional and Enterprise Editions

File Distribution

Layered Product

lispworks-clim-7.1-n.i386.rpm

CLIM 2.0

Install this module if required by substituting the above filename into the same commands you used to install the main lispworks package.

If you used a --prefix argument when installing LispWorks, then use the same prefix for this module.

4.4.3.5 Installing loadable Enterprise Edition modules

The following modules are packaged as separate RPM files for installation after the main lispworks package.

File distributions for layered products in the Enterprise Edition

File Distribution

Layered Product

lispworks-clim-7.1-n.i386.rpm

CLIM 2.0

lispworks-kw-7.1-n.i386.rpm

KnowledgeWorks

lispworks-corba-7.1-n.i386.rpm

LispWorks ORB

lispworks-sql-7.1-n.i386.rpm

Common SQL

Install these modules as described in Installing CLIM 2.0.

4.4.3.6 Documentation and saving space

Documentation in HTML and PDF format is provided with all editions. PostScript format is available to download. To obtain copies of the printable manuals, see Printable LispWorks documentation.

Documentation is installed by default in the lib/7-1-0-0/manual sub-directory of the LispWorks installation directory.

Using RPM, you can save space by choosing not to install the documentation. For example, use the following command (all on one line):

rpm --install --excludedocs --prefix <directory> lispworks-7.1-n.i386.rpm

To install the documentation at a later stage, you need to use the --replacepkgs option:

rpm --install --prefix <directory>
 --replacepkgs lispworks-7.1-n
.i386.rpm
4.4.3.7 Installing Patches

After completing the main RPM installation of LispWorks and any modules, ensure you install the latest patches from the RPM file available for download at www.lispworks.com/downloads/patch-selection.html . Patch installation instructions are in the README file accompanying the patch download.

4.4.4 Installation from the tar files

The LispWorks distribution is also provided as tar files compressed using gzip for use if you do not have an appropriate version of RPM to unpack the RPM binary file. The gzipped files for LispWorks are as follows:

Files for LispWorks

lw71-x86-linux.tar.gz

32-bit LispWorks x86 image, modules and examples

lw71-arm-linux.tar.gz

32-bit LispWorks ARM image, modules and examples

lw71-amd64-linux.tar.gz

64-bit LispWorks x86_64 image, modules and examples

lw71-arm64-linux.tar.gz

64-bit LispWorks ARM64 image, modules and examples

lwdoc71-x86-linux.tar.gz

Documentation in HTML and PDF formats for all architectures

Note: The gzipped files for the LispWorks Personal Edition have similar names.

To install from these files:

  1. Follow the instructions under License agreement.
  2. Use cd to change directory to the location of the downloaded files before running the installation script.
  3. Run the installation script lwl-install.sh (or lwlper-install.sh for the Personal Edition). as root if the directory specified by the installation directory requires it (the default does).
  4. This script takes --prefix and --excludedocs arguments like rpm to control the installation directory and amount of documentation installed.

    For example, to install 32-bit LispWorks in /usr/lispworks, without documentation you would use:

sh lwl-install.sh --excludedocs --prefix /usr/lispworks

Note: the default location under /usr/local is appropriate for this unmanaged (non-RPM) installation.

See Running LispWorks for how to enter your license details.

4.4.4.1 Installing Patches

After completing the main tar installation of LispWorks, ensure you install the latest patches from the tar archive available for download at www.lispworks.com/downloads/patch-selection.html . Patch installation instructions are in the README file accompanying the patch download.


LispWorks Release Notes and Installation Guide - 19 Oct 2017

NextPrevUpTopContentsIndex