On Wed, 28 Mar 2001 16:15:32 +0100, Jonathan Riches wrote:
>Hello,
>wondering if anybody can shed some light on this? I've tried configuring
>LessTif 0.92.26 using the XFree86-4.0.3 & 4.0 binaries downloaded from the
>Cygwin site, I've encountered a problem which hasn't been apparent when
>using 0.92.6 with XFree86-4.0.
>Configured build:
>/tools/lesstif-0.92.26/configure --enable-build-21 --enable-default-21 --wit
>h-x --x-includes=/usr/X11R6/include --x-libraries=/
>usr/X11R6/lib
Everything else did build fine?
Good news, there was an unresolved issue with cygwin IIRC.
>Make error:
>Making all in uil
>make[3]: Entering directory `/home/build-tif/clients/Motif-2.0/uil'
>/bin/sh ../../../libtool --mode=link gcc -g -Wall -o newuil.exe newuil.o
>../../../lib/Uil-2.0/libUil.la ../../../lib/Mrm-2.0/libMrm.la
>../../../lib/Xm-2.0/libXm.la -L/usr/X11R6/lib -lXt -lSM -lICE -lX11
>gcc -g -Wall -o newuil.exe newuil.o
>../../../lib/Uil-2.0/.libs/libUil.a -L/usr/X11R6/lib -lXt
>../../../lib/Mrm-2.0/.libs/libMrm.a
>../../../lib/Xm-2.0/.libs/libXm.a -lXt -lSM -lICE -lX11 -L/usr/X11R6/lib -lX
>t -lSM -lICE -lX11
>../../../lib/Xm-2.0/.libs/libXm.a(Vendor.o)(.data+0x6e0): multiple
>definition of `vendorShellClassRec'
>/usr/X11R6/lib/libXt.a(Vendor.o)(.data+0x0):Vendor.c: first defined here
>../../../lib/Xm-2.0/.libs/libXm.a(Vendor.o)(.data+0x774): multiple
>definition of `vendorShellWidgetClass'
>/usr/X11R6/lib/libXt.a(Vendor.o)(.data+0x94):Vendor.c: first defined here
>collect2: ld returned 1 exit status
>make[3]: *** [newuil.exe] Error 1
>make[3]: Leaving directory `/home/build-tif/clients/Motif-2.0/uil'
newuil is nothing which you probably want to have or even need.
But anyway the problem might be that
gcc -g -Wall -o newuil.exe newuil.o
../../../lib/Uil-2.0/.libs/libUil.a -L/usr/X11R6/lib -lXt
../../../lib/Mrm-2.0/.libs/libMrm.a
../../../lib/Xm-2.0/.libs/libXm.a -lXt -lSM -lICE -lX11 -L/usr/X11R6/lib -lXt -lSM
-lICE -lX11
libXt is linked before libXm and then it comes again, etc.
The problem is that current libtool does not allows us (in a reasonable)
way to link our new libUil against our new libXm. So we only link against
libXt and this seems to trigger that problem :-\
---
Alexander Mai
[EMAIL PROTECTED]
