Path: utzoo!attcan!uunet!lll-winken!sun-barr!cs.utexas.edu!milano!titan!cheung
From: cheung@titan.sw.mcc.com (Po Cheung)
Newsgroups: comp.windows.x
Subject: MIT vs OpenWindows X libraries
Message-ID: <4386@titan.sw.mcc.com>
Date: 31 Oct 90 18:03:55 GMT
References: <4355@titan.sw.mcc.com> <4219@auspex.auspex.com>
Organization: MCC, Austin, TX
Lines: 34

We are running OpenWindows on our Suns and we maintain two sets of
shared X libraries, one set from OpenWindows and the other set from
MIT X distribution.

After applying all the MIT fixes and rebuilding the entire MIT
distribution, including libraries and clients, running xterm and
linking it dynamically against the OpenWindows X libraries gives
rise to these warning messages:

Warning: Widget class VendorShell version mismatch (recompilation needed):
  widget 11004 vs. intrinsics 11003.
Warning: Widget class SimpleMenu version mismatch (recompilation needed):
  widget 11004 vs. intrinsics 11003.
Warning: Widget class VT100 version mismatch (recompilation needed):
  widget 11004 vs. intrinsics 11003.
Warning: Widget class Scrollbar version mismatch (recompilation needed):
  widget 11004 vs. intrinsics 11003.

One solution to this problem is to unsetenv LD_LIBRARY_PATH before
running any X client built with the 'fixed' MIT X libraries.

My question about a second solution :

How about we increase the minor version number of the MIT Xt library 
(to make it more recent than the OpenWindows Xt library) so that clients 
built with the MIT X libraries will always link properly without being 
affected by the setting of the LD_LIBRARY_PATH environment variable?

Is it okay to change the minor version number of the Xt library in this
respect?

Thanks,
Po Cheung
cheung@mcc.com