Re: Argh. Why is this happening to me?
Valdis.Kletnieks(a)vt.edu writes:
Valdis, you are seeing a similar problem that Richard has been
reporting for a while.
The things that all the different crash seem to have in comment is
as you both have remarked
a. A _real_ motif, i.e. commericial or openmotif, not lesstif
b. Mule
will survive at most 3 invocations of 'gnuclient /etc/motd'
(and usually
crashes on trying to leave the first try). Using --with-mule=no produced
an xemacs that survived 14 invocations before I got bored. I've now cycled
through alternate builds with mule=no and mule=yes 3 times, and it seems to
only crash on Mule builds.
Diagnosis: Motif and MULE don't get along. I'm not sure what level of
show-stopper it is - I may be the only bozo trying to build with both
Mule and Motif.
More additional info: --with=mule=yes --with-xim=xlib and Athena
widgets/dialogs works as well. Seems like the instant you allow Motif
to be linked in for *anything* (even XIM) it breaks Mule.
Does just "--with-xim=xlib" do the trick? There have been patches floating
around to disable motif based xim completely because of its instability.
I've now exhausted my debugging ability on THIS one. Has *anybody* actually
had a working build with both Mule and Motif at same time?
Richard, does --with-mule=no "fix" things for you?
Jan