[Xastir] segfault
Tom Russo
russo at bogodyn.org
Fri Jan 12 15:48:19 EST 2007
On Fri, Jan 12, 2007 at 12:46:28PM -0800, we recorded a bogon-computron collision of the <archer at eskimo.com> flavor, containing:
> On Fri, 12 Jan 2007, Curt, WE7U wrote:
>
> > Look for __LSB__ in messages_gui.c and you'll see where I did
> > exactly this fix for the LSB version.
> >
> > If we had a hook whereby we could tell whether we were compiled with
> > Lesstif or Motif, we could do the same thing for Lesstif and solve
> > this segfault problem in a more general way. If you have any ideas
> > along these lines, pass them along. I'm thinking we'll have to do a
> > query to the Xm library to get the version string and then grep for
> > lesstif from there, or else do some checking in
> > acinclude.m4/configure.ac then set a variable so that we can use
> > #ifdef's.
>
> At this URL:
>
> <http://www.sxemacs.org/list-archives/html/sxemacs-patches/2006-05/msg00063.html>
>
> They do a check for "LESSTIF_VERSION":
>
>
> - if test "$have_motif" = "yes"; then
> - dnl autodetect lesstif
> - AC_MSG_CHECKING(for Lesstif)
> - AC_EGREP_CPP(yes,
> -[#include <Xm/Xm.h>
> -#ifdef LESSTIF_VERSION
> -yes
> -#endif
> -], have_lesstif=yes, have_lesstif=no)
> - AC_MSG_RESULT($have_lesstif)
> - fi
>
>
> Does this seem like a reasonable way to go about it?
Seems about as reasonable as any. I have never used "AC_EGREP_CPP" before,
but it's a clever approach that relies only on whether Xm.h defines the
macro in question.
--
Tom Russo KM5VY SAR502 DM64ux http://www.swcp.com/~russo/
Tijeras, NM QRPL#1592 K2#398 SOC#236 AHTB#1 http://kevan.org/brain.cgi?DDTNM
"And, isn't sanity really just a one-trick pony anyway? I mean all you get is
one trick, rational thinking, but when you're good and crazy, oooh, oooh,
oooh, the sky is the limit!" --- The Tick
More information about the Xastir
mailing list