Path: utzoo!utgpu!news-server.csri.toronto.edu!cs.utexas.edu!sun-barr!apple!agate!ucbvax!alfalfa.com!nazgul
From: nazgul@alfalfa.com (Kee Hinckley)
Newsgroups: comp.windows.x.motif
Subject: Re: Xt not calling not calling Motif Vendor Initialize on RS/6000?
Message-ID: <910227112441.3135@alphalpha>
Date: 27 Feb 91 16:24:41 GMT
References: <9102271507.AA12380@osf.osf.org>
Sender: daemon@ucbvax.BERKELEY.EDU
Distribution: inet
Organization: The Internet
Lines: 38

> Kee wrote:
> > Could be.  There are two versions of the routines, one in Xt and one in Xm.
> > You definitely need the Xm one.  This was a problem for me because I was
> > making them Apollo global libraries and it didn't appreciate having two
> > identically named entry points in the global name space.
> 
> How did you solve it?
I through out the Xt version and replaced it with the Xm one.  (Is there any reason
this would screw up non-Motif apps?)

> If this is an absolute restriction, it must mean the Apollo architecture forbids
> one favorite solution to the patched Selection.c problem: tacking Selection.o
> onto the end of libXm.a.  Correct?
Yes, but for more reasons than that.  Apollo shared libraries are fully linked
objects, they are not in archive format.  

> Or can the Apollo architecture stand having a static chunk of code text loaded
> from libXm.a (at ld time), and not clash with the same name in Xt (at runtime)?
I'm on weak ground here, since I basically know just enough about this stuff to
get by - you'd be better off asking some of the ex-Apollo people who are working
on OSF/1.  They could tell you in a second.

In general you can just do a replacement by "inlib"ing a piece of code before
running your own.  So you could simply force every app to link (either staticly
or dynamicly) with the the fixed piece of code and you'd be golden.  The catch
is that the Intrinsics do everything indirectly.  The catch is that the shared
library has already decided that the Selection entry points are internal.  So
it's too late to tell them to use the new selection code - it will only affect
your code.  So I'm pretty sure there's no patch short of a whole new library.
But as I say, go ping lwa@osf.org or someone and they'll tell you for sure.

Alfalfa Software, Inc.          |       Poste:  The EMail for Unix
nazgul@alfalfa.com              |       Send Anything... Anywhere
617/646-7703 (voice/fax)        |       info@alfalfa.com

I'm not sure which upsets me more; that people are so unwilling to accept
responsibility for their own actions, or that they are so eager to regulate
everyone else's.