[Bug: 21.4.17] Xemacs and Acroread lockup issue
Stephen J. Turnbull
stephen at xemacs.org
Wed Feb 8 20:17:36 EST 2006
>>>>> "Rodney" == Rodney Sparapani <rsparapa at mcw.edu> writes:
Rodney> By the way, according to Darin's build report, he is not
Rodney> using mule so it does not appear that XIM was configured.
Not in the build report, true, but he commented that he also tried a
MULE build, and that's what Vin was responding to.
To clarify the issue, for several years --with-xim=xlib caused crashes
on several platforms, so on Motif-ly platforms (SunOS, Solaris, maybe
HP/UX?) --with-xim=motif was forced. This generally didn't matter at
that time because people almost always wanted Motif on those platforms
for consistent look and feel, but it was a latent bug.
As Athena improved and other toolkits became more usable, they _were_
used, and this behavior of configure caused --with-mule to pull in XIM
if available, on those platforms it defaults to --with-xim=motif,
which pulled in all of the basic Motif stuff as well as any other
toolkit that was specified, with the predictable results of hilarity
and confusion. A good time was had by all! Or something like that.
I'm sorry about this; I've been aware of it for a couple years, and
have made desultory efforts at improvement. But every time we
refactor the Athena detection, this stuff gets confused, and we've
never managed to get it to where it reliably produces sane results.
School of Systems and Information Engineering http://turnbull.sk.tsukuba.ac.jp
University of Tsukuba Tennodai 1-1-1 Tsukuba 305-8573 JAPAN
Ask not how you can "do" free software business;
ask what your business can "do for" free software.
More information about the XEmacs-Beta