[Date Prev] [Date Next] [Thread Prev] [Thread Next] Date Index Thread Index Search archive:
Date:Mon Nov 18 08:31:35 2003 
Subject:Re: Mandrake install error - cannot find -libtermcap 
From:A . Sloman 
Volume-ID:1031118.02 

Paul Broadbent wrote:

[PB]
> > > I've found the files libtermcap.so.2 and libtermcap.so.2.8 in /lib,
> > > and tried linking /lib/libtermcap to one of these, and adding links to
> > > them in /usr/lib but this makes no difference.
> >
 [AS]
> > The link would have to be
> >     libtermcap.so
> >
> > Try that and see if it works.
> > ...
 
> > ....
 [AS}
> > If you want to use the motif facilities in poplog you'll also need
> >     /usr/X11R6/lib/libXm.so
> >
> > (or libXm.so.2 or libXm.so.3)
> >

[PB]
> Thanks, I tried that

By 'that' I assume you mean making the link to libtermcap.so?


> and it then installed ok,

Did you re-run the install script from the beginning, or did you try
using the previous partly installed version and completing the
installation 'by hand'?

[PB]
> but now I'm having more
> problems running it. First when I tried to run it complianed it was
> missing libXm.so.3

I am puzzled that you did not get a complaint about this when you
were installing poplog.

> so I installed the openmotif RPM.
 
> Now when I run 'poplog xved' or 'poplog ved' or 'poplog po11' it gives
> this error message:
>
> ;;; MISHAP - SAVED IMAGE NOT FOUND
> ;;; INVOLVING:  '/usr/local/poplog/current.poplog/pop/lib/psv/startup.psv'
> ;;;
> ;;; DOING    :


That must mean it did not install OK. That startup.psv file and one in
	/usr/local/poplog/v15.53d/poplocalbin/startup.psv

would both have been produced when you ran the install script.

I suggest that you remove the whole installation

	rm -rf /usr/local/poplog/v15.53d
	rm -rf /usr/local/poplog/local

and run the install script again:

	./INSTALL_EVERYTHING_WITH_MOTIF > install.log

If any warning messages come to the screen, save them using your mouse
and email them to me, and also the contents of the install.log file.

> And when I just run 'poplog' it seems to do nothing (well nothing
> happens

the poplog script runs its argument and exits. If it gets no argument
it exits. You can also source poplog.sh to set environemt variables
so that you don't have to prefix your commands with poplog.

You should have a file that came with the original tar file

	HOW-RUN-POPLOG.txt

also here:
	http://www.cs.bham.ac.uk/research/poplog/linux-cd/HOW-RUN-POPLOG.txt

which attempts to explain in more detail.

> and when I run 'ps -ael' there it's not there).

because it finishing running if it gets nothing to run.

> I have tried creating links to
> /usr/local/poplog/current.poplog/pop/lib/psv/startup.psv from
> /usr/local/poplog/v15.53d/poplocalbin/startup.psv and
> /usr/local/poplog/v15.53d/pop/lib/psv/startup.psv

That's strange. If your installation got as far as producing
this file in $poplocalbin:

	/usr/local/poplog/v15.53d/poplocalbin/startup.psv

it should previously have produced this one (in $popsavelib):

	/usr/local/poplog/v15.53d/pop/lib/psv/startup.psv

> have
> but then it complians about it not being the same system and version,
> so I suppose that don't work it this case.

The only thing I can think of is that when  you thought the installation
process worked it did not, and you somehow have managed to re-link
the main executable
	
	/usr/local/poplog/v15.53d/pop/pop/basepop11

after creating the startup.psv file and then it did not create new
versions of startup.psv

So reinstalling from scratch with careful monitoring of what happens
should work, now that you have libtermcap.so and libXm.so in place.

> Also, I seem to remember it complaining about not having permission to
> access the x display sometime, but that error no longer occours, so I
> don't know what happened to that, because I don't remeber doing
> anything to fix that!

You could get the error if the user that owned the current X display was
different from the user trying to use it.

E.g. if you log in as yourself and start up the X window system, then in
an xterm window use 'su' to become root(superuser), you may find that
attempts to run X facilities (e.g. xfontsel) as root will produce that
error.

You can prevent it if before the 'su' command you use xhost to give
access to the display. E.g. if your machine's name is 'fred'

	xhost +fred

(you can put that in an X startup script if you have one).

Aaron