john duncan <agley@optusnet.com.au> writes:
> Date: Sun, 27 Jul 2003 15:51:08 +1000
> ....
[JD]
> >> >
> >> > 00002 errors
> >> > 00000 warnings
> >> > *** Interrupted
> >
[AS]
> > I don't see how this could give you a working system?
>
> Hi Aaron,
> I am on night shift this weekend so have limited time to play
> but can tell you that the assembler errors were my own stupid fault. This
> was a net install with minimal libraries and I had only the kernel
> assembler as86 and linked to it but have now installed binutils which has
> /usr/bin/as in it.
Glad to hear that problem is solved.
> I gave the new tarball a try but on Debian I have to
> comment out poplink_cmnd from LINK_MOTIF_POPLOG, which is a problem since
> where it is seems to be over written whenever I change it.
Apologies: the poplink_cmnd instruction is no longer needed, and I
should have removed it earlier. All that used to do is produce a
version of basepop11 linked with motif. But that is now redundant,
since the script does the following:
use corepop to make system images
popc.psv, poplibr.psv, poplink.psv, newpop.psv
then newpop is used to create basepop11 (and in the process
it overwrites the pre-existing poplink_* files so they are not
strictly needed -- I left them in case there is a problem with
corepop and re-linking has to be the first step.
I've now removed the poplink_cmnd instruction from:
http://www.cs.bham.ac.uk/research/poplog/com/LINK_MOTIF_POPLOG
This will be changed soon again for Poplog Version 16
> It does seem
> to find Motif O.K.
That's probably because the later newpop command successfully links
it?
> Line 87 of INSTALL_MOTIF_POPLOG seems to be missing a = sign
> as well.
Yes. Apologies.
In fact it does not matter because the instructions that use to use
the environment variable are now commented out. I'll fix this.
> I am not sure about the PATH statement in LINK_MOTIF_POPLOG
> either.
all this does:
PATH=$usepop/pop/pop:$PATH
is put the location of the poplog executables on $PATH (before the
other directories: it could be the other way round).
> At the moment I am at a stand until I can get time to save a copy
> of LINK_MOTIF_POPLOG out of the action and place it in
> /usr/local/poplog/local/linux-poplog and point the installation to it at
> the right time or something similar depending on the details of these
> files.
It should not need to be moved. However if you have not installed
the system in the default location,
/usr/local/poplog/
then the root path in the LINK script (and others) will have to be
edited. I guess I should change the scripts so that they can be run
with an optional argument specifying the installation directory to
be used.
From what you have told me you should have a system which will work
if you simply run the INSTALL_EVERYTHING_... script after you
insert the missing "=" in Line 87 of INSTALL_MOTIF_POPLOG.
(I have now run that script several times, and failed to notice
the error message buried among all the print out produced by
successful instructions.)
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/ (And free book on Philosophy of AI)
FREE TOOLS: http://www.cs.bham.ac.uk/research/poplog/freepoplog.html
|