Path: utzoo!utgpu!news-server.csri.toronto.edu!cs.utexas.edu!sun-barr!apple!agate!ucbvax!osf.org!dbrooks
From: dbrooks@osf.org
Newsgroups: comp.windows.x.motif
Subject: Re: Xt not calling not calling Motif Vendor Initialize on RS/6000?
Message-ID: <9102271507.AA12380@osf.osf.org>
Date: 27 Feb 91 15:07:06 GMT
Sender: daemon@ucbvax.BERKELEY.EDU
Distribution: inet
Organization: The Internet
Lines: 18

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?

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?

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)?

David Brooks
Systems Engineering
Open Software Foundation