On 3 Apr 2004, Pete Goodeve wrote:
> I wrote <pete@jwgibbs.cchem.berkeley.edu>:
> >Unfortunately, I have exactly (I think) the same problem as Antonis
> >did,
It looks as if your installation failed at a slightly different
point though also when trying to run the link command. In your
case it actually started the linking process, then failed to find
a library archive.
> > but for me using tcsh doesn't help. And I'm not using GenToo
> >-- just RedHat (7.0)!
> >
> > [.....]
> >Now, I do have libXt.so in /usr/X11R6/lib -- where it should be as
> > [....]
> >[Actually, I correct myself -- I have libXt.so.6 in .../lib. There
> >is no link from an unnumbered filename. I don't think this should be
> >a problem -- the system was built from RPM this way, so I imagine
> >it's correct.]
I have met this before. During installation of RedHat you get
various options to install packages with or without support for
'development'.
Some of them (e.g. motif and some of the X libraries) are
installed without the .so link to the actual library archive if
you don't select the 'development' option.
Since linking poplog is presumably development, the missing links
cause problems. One would think that a half-sensible dynamic
linker would be able to tell that if libXt.so is missing it
should use libXt.so.6 but apparently this does not happen.
It *may* be possible to fix this by editing the file
/etc/ld.so.conf and running 'ldconfig' (both as root), but I
don't really know.
What does work is installing the .so symbolic link by hand. The
things with which users have reported problems of this sort to me
are, if I remember correctly:
/usr/X11R6/lib/libXm.so
/usr/X11R6/lib/libX11.so
/usr/X11R6/lib/libXt.so
/usr/X11R6/lib/libXext.so
On all the redhat machines I use these are symbolic links. Most
users don't have this problem, so I guess that for some reason
most users manage to select installation options that create the
symbolic links perhaps more by good luck than anything else. The
exception is motif, for which the problem often arises, so the
Poplog installation scripts put a link in $popexternlib/libXm.so
if necessary.
I suppose I could change it to do that for all of the above. It
would require modifying the code that generates the link command
script, to look in the appropriate directory.
> And I have to re-correct myself! Looking at our other (RedHat) linux
> installations, they *do* have unnumbered versions of the libraries
> hard-linked to the numbered ones. And so do most of the /usr/lib
> entries on the failing box.
>
> So I imagine that this *is* the problem. I don't really want to go in
> and add hardlinks to everything by hand, so I'll have to investigate
> why this situation exists at all, and how to fix it.
I think that if you fix just the ones listed above, installation
of poplog will work.
--
Aaron Sloman, ( http://www.cs.bham.ac.uk/~axs/ )
School of Computer Science, The University of Birmingham,
B15 2TT, UK
PAPERS: http://www.cs.bham.ac.uk/research/cogaff/
FREE TOOLS: http://www.cs.bham.ac.uk/research/poplog/freepoplog.html
http://www.cs.bham.ac.uk/research/poplog/packages/simagent.html
TALKS: http://www.cs.bham.ac.uk/~axs/misc/talks/
FREE BOOK: http://www.cs.bham.ac.uk/research/cogaff/crp/
|