grunwald@foobar.colorado.edu (Dirk Grunwald) (02/16/90)
I just installed Ultrix UWS 2.2 with Display Postscript. I'd like to use Display Postscript & the X11R4 toolkit at the same time. /usr/lib/libdps.a requires /usr/lib/libXext.a, which pulls in symbol ``DoAsync'' from /usr/lib/libX11.a. There is no such symbol in /usr/local/lib/libX11.a; is it safe to use /usr/lib/libX11.a with an X11R4 version of /usr/local/lib/libXt.a and libXaw.a? Or, should I just append /usr/lib/libX.a to the link path so it pulls in the needed file? I suspect I'll get duplicate symbol warnings then. Anyone got a clue? Dirk Grunwald -- Univ. of Colorado at Boulder (grunwald@foobar.colorado.edu) (grunwald@boulder.colorado.edu)
kent@wsl.dec.com (Christopher A. Kent) (02/16/90)
__DoAsyncs() is getting called as part of the DECwindows Xlib
UnlockDisplay() macro to handle any asynchronous events that have
occurred. Asynchronous events are something that's in DEC's Xlib but not
the "standard" one. Since you're not using our Xlib, you can't possibly
want to use them, so it looks like it would be safe to compile up a .o
file from this:
_DoAsyncs()
{
}
and link it in (probably between -lXext and -lX11, or earlier with a
loader command to force ld to notice the definition). I tried this with
a very simple DPS program and it appears to work.
Chris Kent Western Software Laboratory Digital Equipment Corporation
kent@decwrl.dec.com decwrl!kent (415) 853-6639dike@flume.ZK3.DEC.COM (Jeff Dike) (02/16/90)
DPS is stealing events out from behind Xlib's back in order to implement some kind of PostScript asynchronous callback. This code seems to have some relationship to the XSelectAsyncEvent and XSelectAsyncInput calls that are in our Xlib, but not in MIT's Xlib. The extra symbol (DoAsyncs) is part of the asynchronous event handling code. It is safe to use the shipped libX11.a with MIT stuff. If it doesn't work, then there is a bug in one or the other of them. Jeff Dike Digital Equipment Corp. dike@decvax.dec.com