Instructions for experienced poplog users.
[Please send corrections to a.sloman@cs.bham.ac.uk
cc: to pop-forum@cs.bham.ac.uk]

--------------------------------------------------------------------------
DRAFT

INSTALLATION AND USE:

PRELIMINARY:
    Make sure you have all the required linux system libraries/packages:

NB espeak, included below, is optional: e.g. useful for the eliza chatbot
demo. Delete it from the command if you don't want it.

On FEDORA and RedHat derivatives, e.g. scientific linux, CentOs,
this should work.
    (On older versions use 'yum' instead of 'dnf': see
    https://www.linux.com/learn/what-you-need-know-about-fedoras-switch-yum-dnf )

dnf install gcc glibc-devel.x86_64 libXext-devel.x86_64 libX11-devel.x86_64 \
    libXt-devel.x86_64 motif-devel.x86_64 tcsh ncurses-devel.x86_64 xterm \
    wget espeak

Some of this may be reduntant depending on what you already have installed
on your machine. I am used to 'xterm' and like to have it available. You
may prefer something else, e.g. gnome-terminal, or xfce4-terminal, etc.

Whichever you use if you try to run poplog or its development tools you
should do so with the environment variable $TERM set to "xterm" to avoid
problems.

On UBUNTU and derivatives try thigs instead:

(Explicitly specify 64 bit options if that's not the default. Not yet
tested by me!)

apt-get install libc6 libncurses5 libstdc++6 \
        gcc build-essential tcsh  \
         libxext6 libxext-dev libx11-6 libx11-dev \
         libxt-dev libmotif-dev libncurses5-dev xterm wget \
         espeak

NB espeak is optional: e.g. useful for the eliza chatbot demo. Delete it
from the command if you don't want it.

1) Unpack contents of the tarball in the desired place,
e.g. in this directory

    /usr/local/poplog

    Make a symbolic link 'current-poplog' to the directory created, e.g.
    if the untarred file produces this directory v15.6301-amd64 then do:

    ln -s v15.6301-amd64 current-poplog

    [Not absolutely essential but it can be useful to have things in
    a standard location.]

If you run bash, then

    cd <installation directory>, e.g. cd current-poplog

    Use 'setenv' or 'export' to make that directory path the value of
    the environment variable $usepop

    e.g. using tcsh, or csh:

        setenv usepop /usr/local/poplog/current-poplog

or in bash/sh (or equivalent):

        export usepop=/usr/local/poplog/current-poplog

SETUP ENVIRONMENT VARIABLES, INCLUDING PATHS.

If you have been using another poplog with different paths, clear the
environment variables first:

If running bash or sh

clear old variables:
    source $usepop/poplogout.sh

set new ones:
    source $usepop/poplog.sh

If running tcsh or csh

clear old variables:
    source $usepop/poplogout.csh

set new ones:
    source $usepop/poplog.csh

====

Check that the core 64-bit executable runs:

    basepop11

(or, equivalently: $usepop/pop/pop/basepop11 )

exit using CTRL-D

If that works, you may or may not be able to use the pre-built saved
images, and failing that you may be able to rebuild them:

E.g. if this package has been installed on a compatible linux, then after
setting up the paths using
one of

    source $usepop/poplog.sh
    source $usepop/poplog.csh

you should be able to run familiar commands, such as pop11, or xved, or
clisp, or prolog, or pml, or teach, because in this package everything is
pre-built. But it may not work in all versions of linux.

Moreover only some parts may work, e.g.  basepop11, but not the saved
images.

E.g. you may find that the saved images supporting those options do not
work in which case this may work

    basepop11

followed by commands to load required packages, starting with 'startup':

You may also be able to rebuild the saved images in your current
environment.

E.g. if the pop11 command (or 'basepop11 +startup') fails, then you may
be able to recreate the poplog saved images, e.g. by running

    $usepop/pop/com/mkstartup

If that produces no errors, and after that the 'pop11' command works then
you may wsh to be able to invoke xved the graphical poplog editor, directly
from the shell, instead of just ved in an xterm window, or starting pop11
then running xved.

To create the xved saved image do:

    $usepop/pop/com/mkxved

If all the saved images work, you may be able to run prolog, common lisp
and Standard ML using the saved images, using these commands:

    prolog

    clisp

    pml

If they don't work, try recreating the saved images:

    $usepop/pop/com/makeimages

If that fails but you can run pop11, or basepop11, you can start pop11 and
then create the additional compilers in a few seconds. (30 years ago it
took several minutes to start each one up, hence the original need for
pre-built saved images).

If the pre-built saved images all work, you can use the gblocks saved image
to show a toy demo of a simplified version of Winograd's SHRDLU (circa
1971):

    $usepop/pop/com/mkgblocks

For more information see the files in
    $usepop/bin/demos

For this version of poplog, most of what's needed is already pre-built in
the tar file.

The following commands all work at Birmingham University on a machine
running 64 bit CentOS

    CentOS Linux release 7.3.1611 (Core)
    3.10.0-514.26.2.el7.x86_64

To create, or re-create all saved images run this command:

    $usepop/pop/com/makeimages

E.g. If this works you can use the gblocks saved image to show a toy demo
of a simplified version of Winograd's SHRDLU (circa 1971):

    $usepop/pop/com/mkgblocks

===============================
Rebuilding from a lower level:

There are alternative build options, provided by Waldek Hebisch in

http://www.cs.bham.ac.uk/research/projects/poplog/amd64

Apologies for incomplete instructions. This is a temporary package meant
for expert users.

Requests for help can be posted to pop-forum@cs.bham.ac.uk.


Aaron Sloman