On Fri, 25 Jul 2003 22:32:01 +0000, Aaron Sloman wrote:
>
> john duncan <agley@optusnet.com.au> writes:
>
>> > They have the 3.0.1 version of OpenMotif and when these libraries
>> > are present it seems to make no difference whether you run
>> > run_install or INSTALL_NOMOTIF the process proceeds on its own merry
>> > way (after commenting out poplink_cmnd)and builds everything but
>> > won't run it because it can't find libXm.so.2
>
> Just after you posted this message I created a new package which is now
> much easier to install.
>
> It is all in
> http://www.cs.bham.ac.uk/research/poplog/bham-linux-poplog.tar.gz
>
> Most of the 'optional extras' have not changed so if you have a slow
> internet connection you could simply fetch the relevant new bits:
>
> http://www.cs.bham.ac.uk/research/poplog/new/linux-poplog.tar.gz
> about 12 Mbytes
> (this now installs poplog v15.53c)
>
> and some small text files in here:
> http://www.cs.bham.ac.uk/research/poplog/new-scripts.tar.gz
> 47577 bytes
>
> If you have previously unpacked the bham-linux-poplog.tar.gz file in
> /usr/local/poplog/src
>
> then put the first file in
> /usr/local/poplog/src/linux-poplog/linux-poplog.tar.gz
> (over-writing the old version)
>
> and untar new-scripts.tar in
> /usr/local/poplog/src
>
> Then delete or move:
> /usr/local/poplog/v15*
>
> Then, provided that you have
> /usr/X11R6/lib/libXm.so
> (if necessary just a link to some other file, e.g. libXm.so.3.0.1)
>
>
> Then installation should be very simple:
>
> cd /usr/local/poplog/src
> and run
> ./INSTALL_EVERYTHING_WITH_MOTIF
>
> It now does everything from that one script, and it starts building
> poplog from a minimal core file in $usepop/pop/pop/corepop
>
> Alternatively, without motif:
> ./INSTALL_EVERYTHING_WITHOUT_MOTIF
>
>
>> > I thought of running rebuilding.linux.poplog but saw that the
>> > relinking at the end is the same command as in INSTALL_NOMOTIF so
>> > gave it a miss for the time being.
>
> This is no longer needed because of the new LINK* scripts in
> $usepop/INSTALL
>
>
>
>> > I then purged Motif and installed xpdf to read Unix Text Processing
>> > which is now a free download and which uses Lesstif2. Upon running
>> > INSTALL_NOMOTIF again the installation appears to have picked up
>> > Lesstif and so far all the bells and whistles are working.
>
> This is a surprise.
> Must have been a bug in the previous installation scripts.
>
>> > It seems that Lesstif2 installs a libXm.so.2 in /usr/lib where it
>> > is found by the installation.
>
> In my experience Lesstif only partly works as a substitute for motif,
> with poplog. Most things work OK, but there a few things that go wrong:
> but it is a long time since I tried, and I can't remember details.
>
>
>> > While struggling with this I installed Mr. Isard's mini Poplog
>> > which seems very suitable for a starter like me.
>
> Fine.
>> > ;;; WARNING - xtw: X TOOLKIT WARNING (xtRemoveGrab: grabError --
>> > XtRemoveGrab asked to remove a widget not on the list)
>
> I wonder if this has anything to do with use of Lesstif. Could you
> describe exactly what you do to produce this.
This warning occurs whenever a window is closed, I'd say that the
lesstif widgets are not referenced by include XmConstants.ph or the
library search paths don't work because of lesstif being in /usr/lib
>
> How do you run poplog? Do you use the command
>
> poplog xved ....
>
> or just
> xved ...
> for instance.
I always use poplog pop11 %x
>
> I wonder whether you are using the version of poplog recently put
> on the web site with the changes suggested by Waldek Hebisch
> or is it all a version you fetched some months ago?
>
> The new package mentioned above
>
>> >
>> > 00002 errors
>> > 00000 warnings
>> > *** Interrupted
>
> I don't see how this could give you a working system?
>
>> Standard images made in popsavelib
>> total 0
>>
>> I don't know if this means trouble but so far what I use is working.
>
> That should mean that the pop11 command does not work (because that
> looks for $popsavelib/startup.psv) but basepop11 should still work
> though not Xved.
It seems to get going again after this and build all the local images.
> I know nothing about Debian, but it would be interesting to know if the
> latest package does install in Debian.
>
> Aaron
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.
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. It does seem
to find Motif O.K.
Line 87 of INSTALL_MOTIF_POPLOG seems to be missing a = sign
as well. I am not sure about the PATH statement in LINK_MOTIF_POPLOG
either. 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.
All the best,
John Duncan
|