[Date Prev] [Date Next] [Thread Prev] [Thread Next] Date Index Thread Index Search archive:
Date:Tue, 15 Feb 2005 01:26:35 +0000 (UTC) 
Subject:AMD64 version of poplog v15.6 
From:A . Sloman 
Volume-ID: 

I ran the patches on a version of v15.6 poplog to update the sources for
AMD64, then rebuilt the tar file and modified the install script to
recompile the poplog sources after un-tarring.


I now have a test version of poplog v15.6 for AMD64

(So this takes a little longer to install than the 32 bit version,
which has the sources precompiled).

One person on the South Birmingham Linux user group volunteered to test
it on an AMD64 running gentoo linux.

As far as I can tell from the log file he sent me, everything worked
except the attempt to run popling_cmnd before recompiling the sources,
naturally. (I'll change the install script later.)

I.e. all the saved images got built in $usepop/pop/lib/psv as expected,
but when he tried to run pop11 he got a segmentation fault (i.e. the
saved image would not start).

I had the same behaviour when I tried to install poplog on Fedora core 2,
and I concluded that it was due to some interaction with the 2.6 linux
kernel.

However others have run poplog on 2.6 kernels, including Suse 9.1

If anyone who has an AMD64 machine running a 64bit linux would like to
check out the package the instructions are below, and also available in

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

NOTE:
I have the impression from the patch used to make the AMD64 version
that the X11 libraries are in a different directory, i.e.

	/usr/X11R6/lib64

so I have changed the checking script to look there instead of in

	/usr/X11R6/lib

If it installs OK there are test demos in the $usepop/bin/demos
directory

If they don't work because of the problem of running saved images,
the following test of Eliza may work:

    $usepop/bin/poplog.sh basepop11

that should give you a colon prompt. Then do the following

    uses teaching
    lib elizaprog
    eliza();

the second line (lib command) should cause
    ;;; LOADING LIB elizaprog

at the end eliza should start.

Each sentence typed to eliza should end with RETURN.

 When bored you can type this to finish eliza

     bye

	
(I still have not fixed the INSTALL script to check whether it is run
by root.)

Aaron
===

New instructions, for AMD64 Poplog:

CONTENTS

 -- STEP 1: Fetch and run Checking file
 -- STEP 2. Fetch main poplog tar bundle
 -- STEP 3. Fetch istallation script
 -- STEP 4. Run script to see instructions and options
 -- STEP 5. Run install script with options specified
 -- STEP 6. Explore the contents of the bin/demos directory
 -- STEP 7. For regular poplog users

-- STEP 1: Fetch and run Checking file

First fetch this small file.

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

Make it executable

    chmod 755 CHECK_LINUX_FACILITIES

then run it on your computer.

    ./CHECK_LINUX_FACILITIES

It will report any problems that might interfere with use of
poplog.

If run as root it will fix some simple common problems like
the presence of

    /usr/X11R6/lib64/libXm.so.3

without a symbolic link to it of the form libXm.so

I.e. it can insert some missing symbolic links
(and will report what it has done.)

-- STEP 2. Fetch main poplog tar bundle

Fetch the main poplog tar bundle (about 18 Mbytes):

    http://www.cs.bham.ac.uk/research/poplog/amd64/bham-linux-poplog-amd64-v15.6.tar.gz


-- STEP 3. Fetch istallation script

Fetch this 69Kbyte file and install it in the same directory
as the tar bundle:

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


-- STEP 4. Run script to see instructions and options

Make it executable and run it

    chmod 755 INSTALL_BHAM_LINUX_POPLOG_AMD64

    ./INSTALL_BHAM_LINUX_POPLOG_AMD64

It will print out instructions as follows (this may change)

   Three arguments are required.
   The first should be either
       motif
   or
       nomotif
   The second should be either
       bham
   or
       original
   The third should be either an installation directory or just
       default
   (The default installation directory is /usr/local/poplog)

   Examples:

       ./INSTALL_BHAM_LINUX_POPLOG_AMD64 motif    bham     default > install.log
       ./INSTALL_BHAM_LINUX_POPLOG_AMD64 nomotif  bham     ~/mypop > install.log
       ./INSTALL_BHAM_LINUX_POPLOG_AMD64 motif    original /usr/local/newpoplog > install.log

   ====

   Use COMMAND > install.log to save output in file install.log


-- STEP 5. Run install script with options specified

If the CHECK scripte said that libXm.so was not found, then give the
nomotif option, otherwise motif. Choose any directory you prefer.

If you run it as root it will put some symbolic links in /usr/local/bin
(1 link) and /usr/local/man/man1 (a few links). If you don't run it as
root it will print warnings instead.

Choose your preferred option then run the appropriate command to install
poplog.


Novice users should do this:

       ./INSTALL_BHAM_LINUX_POPLOG_AMD64 motif bham default > install.log

That will

o create a directory (/usr/local/poplog)

o untar the main bundle into /usr/local/poplog/amd64-v15.6

o run some scripts in

    /usr/local/poplog/amd64-v15.6/INSTALL

They will

o - link the basic poplog executable in the amd64-v15.6/pop/pop
    directory,

o - create some system saved images in the amd64-v15.6/pop/pop
    directory,

o - create a number of user saved images in
        amd64-v15.6/pop/lib/psv
    using scripts in amd64-v15.6/pop/com/
    (e.g. mkstartup and other scripts).

o - link the executable script amd64-v15.6/bin/poplog.sh to

        /usr/local/bin/poplog

    (provided the installation script is run as root)

o - link files in amd64-v15.6/man/man1 to the directory

        /usr/local/man/man1

    (provided the installation script is run as root)

NOTE: if you do not run the script as root or if the /usr/local/bin and
/usr/local/man/man1 directories do not exist you will get a warning
message when the script fails to install the links. These can be
ignored. Instructions for coping can be found in the bin/demos
directory in which poplog is installed, as explained below.

-- STEP 6. Explore the contents of the bin/demos directory

Look in:

    amd64-v15.6/bin/demos/

There are four text files

    bash-users-default-dir
    bash-users-nondefault-dir
    tcsh-users-default-dir
    tcsh-users-nondefault-dir

explaining how to use poplog, depending on whether you
are a bash or a tcsh user, and depending on whether you
have installed poplog in the default directory

    /usr/local/poplog

or somewhere else.

Just read the script that is relevant to your case.

You can also read the file

    amd64-v15.6/bin/demos/AREADME-DEMOS.txt

which shows you how to run some demonstration programs
that will test the installation. (pop11 only).

-- STEP 7. For regular poplog users

Two scripts for running poplog are created in amd64-v15.6/bin

    poplog.sh
        for bash users

    poplog
        for tcsh or csh users

If the installation is done as root /usr/local/bin/poplog
will be made a link to the first one.

You can then run poplog as

    poplog pop11
    poplog xved
    poplog xved file.p
    poploc clisp

etc.

See the relevant introductory guide mentioned in Step 6, for
more details.

See the userguide and man files in

    amd64-v15.6/man/man1/userguide.html
    amd64-v15.6/man/man1/poplog.1

This provides more information on running poplog prolog,
poplog common lisp, poplog ML, ved and xved.


Aaron Sloman
14 Feb 2005
http://www.cs.bham.ac.uk/~axs/
[end]