Re: Argh. Why is this happening to me?

On Mon, 26 Mar 2001 20:20:18 +0100, Glynn Clements said: Blame configure. ;) It found the Motif libs, so it used them... OpenMotif 2.1.30-6 RPMs on the RedHat box, Motif 2.1 on the AIX box that gets hit by the problem as well. Additional info: ./configure --with-widgets=no --with-dialogs=no --debug=no --error-checking=none --with-mule=yes '--cflags=-Wall -Winline -Wmissing-prototypes -Wmissing-declara tions -Wno-switch -Wpointer-arith -Wno-sign-compare -Wno-uninitialized -Wshadow -g -pipe -s' 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. 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? /Valdis