Path: utzoo!utgpu!news-server.csri.toronto.edu!cs.utexas.edu!usc!snorkelwacker.mit.edu!bloom-beacon!SUMEX-AIM.STANFORD.EDU!brock
From: brock@SUMEX-AIM.STANFORD.EDU
Newsgroups: comp.windows.x
Subject: Re: Xt/uil problem
Message-ID: <9012031730.AA27206@sumex-aim.stanford.edu>
Date: 3 Dec 90 17:20:35 GMT
Sender: daemon@athena.mit.edu (Mr Background)
Organization: The Internet
Lines: 22

I ran into the same problem.  It seems to be a shared library problem (there
was a discussion of a related problem on the xpert bulletin board
recently).  The UIL code uses Xt functions, such as XtMalloc, but never 
initializes the toolkit, and the linker doesn't link in all of the 
necessary parts of the library. 

If you add a call to XtInitialize() at the very end of main() in
UilMain.c, *after* the program calls exit(), it should work just fine.

Since the program *always* exits before this, the call
to XtInitialize is never reached, but the linker sees the reference and
gets the apropriate parts of the library.

OSF mentions in the release notes that Motif 1.1 was never tested with
shared libraries, so I guess we can expect little things like this to
pop up (:-D) 

Kevin Brock
brock@sumex-aim.stanford.edu


-------