[To reply replace "Aaron.Sloman.XX" with "A.Sloman"]
Steve Isard <S.IsardDeleteThis@ed.ac.uk> pointed out my slip.
> Date: Wed, 23 May 2001 13:01:59 +0100
> ...
I previously wrote:
>
> > The problem is that popc is a link to basepop11 as is pop11, etc. in
> > $popsys
>
Steve commented:
> Nitpicking correction: On this solaris machine, I find it linked to
> corepop (as opposed to corepop11), together with poplink and poplibr.
That is correct. I had forgotten that basepop11 is (normally) the
full poplog executable which includes the editor, links to X
libraries, etc., whereas the system tools for rebuilding poplog
are based on a smaller simpler executable.
Saved images are built on top of basepop11 for all the standard
"user" poplog systems, pop11, xved, prolog, clisp, pml, etc.
However, if you are rebuilding poplog, e.g. recompiling the sources
in order to rebuild basepop11, or porting poplog to a new platform,
you may need something with fewer dependencies, and poplog is
usually distributed with a minimal executable, which is normally
$popsys/corepop
There are some saved images built on top of that created by
$popsrc/mknewpop
creates newpop.psv
$popsrc/mksyscomp
depending on argumetns supplied creates one or more of
popc.psv, poplibr.psv, poplink.psv
The source files used to create these system building saved images
are in $popsrc/syscomp and will vary from one poplog version to
another (e.g. since on different hardware platforms the poplog
virtual machine compilers have to be different).
There may possibly also be
$popsys/corepop11
which could be an older version that was used to create corepop.
Or corepop may have been created by copying corepop11 and then
running "strip corepop" to reduce size.
Originally in $popsys, the files popc, poplibr, poplink, and newpop
were hard links to corepop. When I had to rebuild the binaries for
linux poplog about a year ago (for redhat 6) I made them all
symbolic links, which simplifies changes (e.g. you can rename a new
corepop instead of having to copy it.) I don't know why hard links
were originally used.
There is a lot more on all of this in the files in
http://www.cs.bham.ac.uk/research/poplog/sysdoc/
especially
http://www.cs.bham.ac.uk/research/poplog/sysdoc/rebuilding
All the sysdoc files are also downloadable in
http://www.cs.bham.ac.uk/research/poplog/sysdoc.tar.gz
A script for rebuilding these system images originally written by
Michael Worsely and Praxis Ltd, is here:
http://www.cs.bham.ac.uk/research/poplog/tools/relinking.linux.poplog
Seeing how the executables and saved images are created may explain
more clearly what is there and why!
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
|