Path: utzoo!news-server.csri.toronto.edu!rutgers!mit-eddie!bloom-beacon!dont-send-mail-to-path-lines
From: doc@fajita.UUCP (Tom Dockery)
Newsgroups: comp.windows.x
Subject: Re: XInternAtom / XmInternAtom
Message-ID: <9103130022.AA04904@mfti.com>
Date: 13 Mar 91 00:22:29 GMT
Sender: daemon@athena.mit.edu (Mr Background)
Organization: The Internet
Lines: 20


With respect to my previous missive,

> ...
>       Could not load program u/mfti1/MASTER/bin.910311/bin/ibm-rs/cfwin
>       Symbol XmInternAtom in cfwin is undefined
> ...

I've discovered the problem; the IBM's update level 3003 shipped to vendors
in January, and update level 3003 shipped to *customers* last week, have a
disparity in libXm.a.  Thus, the code I compiled here wont link with my
customer's libraries.  Unfortunately, IBM's "lslpp" returns identical release
numbers of "03.01.0003.0012" from both updates.  (FLAME BRIEFLY ON) One would
think that, given a change in libraries, they could have at least incremented
one of those twelve digits to indicate some sort of difference (FLAME OFF).

Tom Dockery
Market Focus Technologies, Inc.

        standard disclaimer...