wmk@fed.FRB.GOV (William M. Kules) (11/09/90)
[ I am sending this to Sun's hotline, as well as posting it to comp.windows.x and comp.windows.open-look. ] We are running both MIT X11 R4 (fix-18) and OpenWindows 2.0. I've looked at the shared and static linking libraries and have a few questions about them and other X and OpenWindows issues. I understand (from Larry Cable's article in comp.windows.x) that the Xt Intrinsics library (libXt) and include files are direct recompilations of MIT's Xt code, up to and including fix-13. Is the same true for libX11, libXau, and libXext? In other words, has Sun modified the MIT X11 stuff? I noticed that in Sun's libX11.so, there is also a libX11.sa (for external, initialized data used by the shared library), but MIT's version lacks that file. Can someone explain why? Why does one shared X11 library from Sun appear with two separate version numbers (1.0 and 4.3, the 4.3 libs are symlinks to the 1.0 libs)? Are they interchangeable with the MIT versions? This means that the X11 applications will attempt to link against the OpenWindows libraries first, since MIT has a lower version (4.2). This sometimes causes annoying warning messages from ld.so. Why does Guide link against libX instead of libX11? I thought libX went away with the demise of X10, and that all new applications are supposed to link against libX11. Many thanks, Bill Kules, Automation and Research Computing | Internet: wmk@fed.FRB.GOV Federal Reserve Board, Washington, DC | UUCP: uunet!fed!wmk "Recycling: Just do it, dammit!" | Phone: (202) 452-3933