[Date Prev] [Date Next] [Thread Prev] [Thread Next] Date Index Thread Index Search archive:
Date:Mon Feb 8 21:52:45 2001 
Subject:Re: Linux installation and starting eliza 
From:Aaron Sloman See text for reply address 
Volume-ID:1010208.03 

[To reply replace "Aaron.Sloman.XX" with "A.Sloman"]

cglur@onwe.co.za writes:

> Date: 8 Feb 2001 19:18:45 GMT
> ...

> Setpop
> : eliza();
> ;;; DECLARING VARIABLE eliza
>
> ;;; MISHAP - enp: EXECUTING NON-PROCEDURE
> ;;; INVOLVING:  <undef eliza>
> ;;; DOING    :  pop_setpop_compiler
>   ?? perhaps some links missing ??


It looks as if the file $usepop/pop/lib/auto/eliza.p was not
autoloaded.

What happens when you start Pop-11 and do this ?

popautolist ==>

It should print out something like the following, though possibly with
different line breaks:

** [$poplocalauto/ $popsunlib/ $popautolib/ $popvedlib/
    $popvedlib/term/ $usepop/pop/lib/database/]

(or possibly more than that if your init.p file adds extra directories
to the list).

However those autoloadable directories will work only if the environment
variables have been defined, i.e. $poplocalauto $popautolib etc.

($popsunlib should probably be removed .... )

The standard environment variables will be set if you first do
this (for bash users):

    usepop=<directory containing the current poplog>
    export usepop

e.g.
    usepop=/usr/local/poplog/v15.53
    export usepop

Or for those who use csh or tcsh:

    setenv usepop /usr/local/poplog/v15.53

Then you should do this to set environment variables

or, in bash

    . $usepop/pop/com/poplog

in csh or tcsh:

    source $usepop/pop/com/poplog

Those commands can be put in your .login or .profile file if you
want then run when you login (as many regular pop11/ved users do).

There have been previous lengthy discussions of the need to make
poplog no longer require environment variables. E.g. instead it
could read a file somewhere specifying the values for the variables.
A number of schemes have been proposed, though nothing has yet been
implemented for lack of resources.

Another alternative: fetch this

    http://www.cs.bham.ac.uk/research/poplog/setup.tar.gz

and install it in your $poplocal/local directory,

You will find that it includes a shell script

    $poplocal/local/setup/bin/poplog

installing that in the recommended place, and making
    /usr/local/bin/poplog

a symbolic link to it will mean that you don't need to go through
the above rigmarole to start poplog. Just do

    poplog pop11

or
    poplog xved <file>

etc.

The poplog command sets up the environment variables then runs pop11
or xved or prolog, or whatever it gets from the command line
argument.

I hope that helps. It is widely agreed that the initial hump to get
over if you are installing poplog away from friendly experts is
too large. Eventually it should be fixed. Some would like it done
in a rpm package format. But that would not work for non-linux
users.

All this should go in a FAQ ....

Aaron
====
Aaron Sloman, ( http://www.cs.bham.ac.uk/~axs/ )
School of Computer Science, The University of Birmingham, B15 2TT, UK
EMAIL A.Sloman AT cs.bham.ac.uk   (ReadATas@please !)
PAPERS: http://www.cs.bham.ac.uk/research/cogaff/
FREE TOOLS: http://www.cs.bham.ac.uk/research/poplog/freepoplog.html