Path: utzoo!utgpu!watserv1!watmath!iuvax!mailrus!bbn!diamond.bbn.com!mlandau
From: mlandau@bbn.com (Matt Landau)
Newsgroups: comp.windows.x
Subject: Re: libXt problems
Message-ID: <13483@granite.BBN.COM>
Date: 8 Feb 90 16:34:05 GMT
References: <1990Feb8.050507.15837@deimos.cis.ksu.edu>
Sender: news@bbn.com
Lines: 31

brtmac@wyatt.ksux.ksu.edu (Brett McCoy) writes:
>I have been having problems getting programs to run that use the Xt library.
>....The problem I am having is that I get the error message:
>   ld.so: call to undefined procedure __GetHostname from 0xf776a96c

Do you perchance have OpenWindows installed on the same machine?  Have 
you perhaps installed the OpenWindows version of the shared libX in 
/usr/lib, or do you run with LD_LIBRARY_PATH pointing to the OpenWindows 
lib directory?

I got the same complaint, about the same routine, from many of the X11R4 
clients when I first built them with shared libraries on my SparcStation.  
It turned out I'd forgotten to unsetenv LD_LIBRARY_PATH, which pointed at
the *OpenWindows* shared libraries, and so I was getting binaries that 
tried to mix R4 shared libraries with OpenWindows shared libraries at 
runtime.  The internal implementation details of the two systems are such
that this doesn't work.

I unsetenv LD_LIBRARY_PATH and removed any stray links in /usr/lib that 
pointed to OpenWindows libraries, and relinked all my clients.  Voila!
All the __GetHostname complaints vanished...

This raises the whole issue of what software vendors (like us) are going
to have to do to cope with different vendors' shared X libraries.  I'd
love to ship my X11-based products dynamically linked, but does this mean
I have to have two complete sets of products, one for MIT's shared libs
and another for Sun's, and rely on the customer to know which one he
really needs?  Ugh...
--
 Matt Landau		    Broken lover, you can touch me, 
 mlandau@bbn.com	      In the dark the innocent can't see.