I was looking for something else on google groups and found that
Chris Dollin had posted a message saying
> I am upgraded to Fedora Core 5. I have a pop11 failure or few.
The message had a large attachment, which is probably why it never
reached the Birmingham news server and therefore did not get to
the pop-forum gateway (which might not have let it through anyway).
Anyhow I copied the installation log file from the google group site
and found:
> X WINDOW LIBRARIES MISSING
> Could not find libX11.so libXext.so libXt.so
> nor files with version numbers to link them to.
> Cannot run poplog with graphical (X window) facilities
> Investigate installation of X Window system with libraries
> to support development work on your linux system
>
> (see either www.xfree86.org or www.x.org)
also
> /usr/X11R6/lib/libXm.so* not found.
> Please check out your motif installation.
> Could not find Motif (or Lesstif)
> Cannot run poplog with Motif even if X libraries installed
Chris: has the location of the X11 stuff changed in FC5?
Are you sure you have motif installed? (libXm.so needed).
(One problem with linux is that it keeps changing and breaking things,
especially RedHat based linux. In contrast the Solaris version of poplog
last compiled in 1999 still works.)
Because it could not find the X11 facilities it should have tried
linking poplog without X. But there are not enough checks in the
installation script it seems, so it tried linking poplog only without
motif
> running ./LINK_USING_NEWPOP nomotif
> relinking without motif
> ...
> trying to run /usr/local/poplog/v15.6/pop/pop/poplink_cmnd.nomotif.sh
To my surprise that seems to have worked. Maybe the X11 stuff was found
by the linker in a new place?
> checking for newpop11 after poplink_cmnd
> -rwxr-xr-x 1 root root 1797584 Mar 30 10:26 newpop11
> copying newpop11 to basepop11
So it managed to link newpop11, and made that basepop11.
Then
> Try to rebuild newpop, poplink, poplibr, popc, system images
This seems to have worked OK
> System images made in popsys are:
>
> -rw-r--r-- 1 root root 113460 Mar 30 10:26 /usr/local/poplog/v15.6/pop/pop/newpop.psv
> -rw-r--r-- 1 root root 478272 Mar 30 10:26 /usr/local/poplog/v15.6/pop/pop/popc.psv
> -rw-r--r-- 1 root root 134208 Mar 30 10:26 /usr/local/poplog/v15.6/pop/pop/poplibr.psv
> -rw-r--r-- 1 root root 199744 Mar 30 10:26 /usr/local/poplog/v15.6/pop/pop/poplink.psv
> System images appear to have been created OK
Going back to your attempt at re-installation
> rm: cannot remove `/usr/local/bin/poplog': No such file or directory
Not important: failed to remove something that was not there.
> ./INSTALL_BHAM_LINUX_POPLOG: line 341: cd: /usr/local/man/man1: No
> such file or directory
Has FC5 given up using /usr/local/man for man files? Where do local man
files go now? Maybe that bit of the script will have to be changed.
> Now run newpop to re-link, rebuild indexes, etc.
> /usr/local/poplog/v15.6/pop/src/newpop -link -x=-xt -norsv
> Sussex Poplog Version 15.6
>
> Standard images made in popsavelib are:
>
> total 0
> newpop did not work.
Running newpop failed -- I don't know why
> /usr/local/poplog/v15.6/pop/src/newpop: line 21: 13802 Segmentation
> fault corepop +$popsys/newpop.psv "$@"
This looks like the malloc problem mentioned a couple of weeks ago fixed
using the following on FC4:
[from a previous message by AS]
> sysctl -w kernel.randomize_va_space=0
>
> and after that the saved images started every time!
>
> So I have inserted the following in /etc/sysctl.conf
>
> # Prevent problems starting saved images
> kernel.randomize_va_space=0
You reported that that had worked for you also. Did you do this in FC5
before trying to run or install Poplog?
Because newpop failed, it went back to the previous basepop11
> Try using old basepop11 with /usr/local/poplog/v15.6/pop/com/mkstartup
> ;;; MAKING IMAGE /usr/local/poplog/v15.6/pop/lib/psv/startup.psv
then
> Startup saved image appears to have been created OK
> Try /usr/local/poplog/v15.6/pop/com/makeimages, for prolog, lisp, ml
> Running mkplog
It seemed to be able to run the scripts for creating the saved images
for prolog.psv, clisp.psv and pml.psv
That implies that the startup.psv saved image had been created OK and
pop11 should work.
Were the saved images created?
Chris, what does this show?
ls -l $usepop/pop/lib/psv/
Chris also writes:
> (a) if I just run the existing images,
what existing images? i.e. what version of poplog?
> I get
>
> pop11: relocation error: pop11: symbol errno, version GLIBC_2.0 not defined in
> file libc.so.6 with link time reference
>
> which is the long-standing `don't treat errno as an extern variable` issue finally
> been given teeth. Something will Have To Be Done.
I thought we had completely eliminated the errno problem from poplog a
few years ago, with help from Waldek Hebisch in June 2003.
See the revision notes in
$popsrc/errors.p
$usepop/pop/extern/lib/c_core.c
$usepop/pop/lib/lib/unix_sockets.p
Summarised in
http://www.cs.bham.ac.uk/research/poplog/bugfixes/BUGREPORTS
Anyhow a lot of stuff worked in the installation process and appears not
to have repeated the 'errno' complaint. So perhaps you were previously
using an old poplog?
Aaron
http://www.cs.bham.ac.uk/~axs/
|