Rick Scott writes:
> This is possibly a typo on our part. It occurs in Vendor.c, and a different
> version of the code is used depending whether XtSpecificationRelease < 6. So it
> seems that when you are linking against the LessTif 2.0 library Vendor.c thinks
> that XtSpecificationRelease < 6. However when you link against the 1.2 library
> it is 6 or greater??
>
> In any case one side of the #if has _XtwaitForSomething (which looks wrong),
> and the other side has _XtWaitForSomething (which is what is in my R6 lib).
>
>
> On 16-Dec-00 at 01:12, Ti Kan ([EMAIL PROTECTED]) wrote:
> > gcc -o xmcd callback.o cdfunc.o command.o dbprog.o geom.o help.o
> > hotkey.o main.o userreg.o widget.o wwwwarp.o ../common_d/libutil.a
> ../cdinfo_d/libcdinfo.a ../libdi_d/libdi.a -O -L/usr/X11R6/lib
> /home/ti/src/X11/lesstif-0.92.0.uw2/lib/Xm-2.0/.libs/libXm.a -lXt -lX11 -lSM
> -lICE -lsocket -lnsl
> /home/ti/src/X11/lesstif-0.92.0.uw2/lib/Xm-2.0/.libs/libXm.a(Vendor.o): In
> function `WaitForWM':
> > Vendor.o(.text+0x15cf): undefined reference to `_XtwaitForSomething'
Actually this is a problem on my part. It turns out that my system has both
X11R5 and X11R6 on it, and configure found the X11R5 headers first, so
it generated Makefiles that looks there. If I add
--x-includes=/usr/X11R6/include --x-libraries=/usr/X11R6/lib to the
configure line then this problem does not occur.
BTW, configure seems to use different algorithms looking for X headers
and Motif headers. It seems to find the Motif headers in /usr/X11R6 first...
-Ti (author of xmcd, xmmix)
--
/// Ti Kan Vorsprung durch Technik
/// AMB Research Laboratories, Sunnyvale, CA. USA
/// [EMAIL PROTECTED]
////// http://www.ibiblio.org/tkan/
///
