My build problems are solved.  I downloaded the latest LessTif, which fixed
the undefined reference problem, and I found the solution to the yylineno
problem in the archives.

Thanks,
Ray

----- Original Message -----
From: "Raymond C. Maple" <[EMAIL PROTECTED]>
To: <[email protected]>
Sent: Friday, February 16, 2001 10:11 PM
Subject: Re: [opendx-dev] Unresolved reference XmObjectAtPoint


> Here is some more info.
>
> The Lesstif libraries are version 0.89.9.  As I said before, I have tried
> both the 1.2 and 2.0 versions provided by Suse.
>
> The following configure command was applied to a fresh unpacking of the
tar
> file
>
>
./configure --prefix=/usr/local/dx-4.1.0 --enable-installhtml=no --with-dps=
> no --with-fpx=no --with-hdf=no --with-ttf=no --with-javadx=no --with-x
>
> make resulted in:
>
> [successful compilations clipped]
> Making all in dxui
> make[3]: Entering directory `/home/rmaple/opendx/dx-4.1.0/src/uipp/dxui'
> c++  -g -O2 -I/usr/X11R6/include  -o dxui  ColormapDefinition.o
> [lots of object files clipped]
> Main.o ../dxuilib/libDXUI.a   ../base/libBASE.a
>
../widgets/libWIDGETS.a   -L/usr/X11R6/lib  -L/usr/local/lib  -lm -lXm -lXmu
>  -lXt -lX11 -lXext -lnsl -lnetcdf -lcdf -ltiff -ljpeg -lpng -lbz2 -lz -ldl
 -
> lg++ -lm -lSM -lICE -lXm -lXext -lXt -lX11 -L/usr/X11R6/lib
> ../dxuilib/libDXUI.a(netyacc.o): In function `yyparse':
> /usr/share/bison.simple:265: multiple definition of `yylineno'
>
../dxuilib/libDXUI.a(Network.o)(.bss+0x1c):/home/rmaple/opendx/dx-4.1.0/src/
> uipp/dxuilib/../base/Base.h: first defined here
> ../widgets/libWIDGETS.a(Image.o): In function `Arm':
> /home/rmaple/opendx/dx-4.1.0/src/uipp/widgets/Image.c:451: undefined
> reference to `XmObjectAtPoint'
> ../widgets/libWIDGETS.a(SlideBar.o): In function `Help':
> /home/rmaple/opendx/dx-4.1.0/src/uipp/widgets/SlideBar.c:670: undefined
> reference to `XmObjectAtPoint'
> collect2: ld returned 1 exit status
> make[3]: *** [dxui] Error 1
> make[3]: Leaving directory `/home/rmaple/opendx/dx-4.1.0/src/uipp/dxui'
> make[2]: *** [all-recursive] Error 1
> make[2]: Leaving directory `/home/rmaple/opendx/dx-4.1.0/src/uipp'
> make[1]: *** [all-recursive] Error 1
> make[1]: Leaving directory `/home/rmaple/opendx/dx-4.1.0/src'
> make: *** [all-recursive] Error 1
>
> I just noticed I also have a problem with a multiply defined yylineno.  I
> remember reading about a fix for that problem, but I don't remember what
is
> was.  If anyone can help with that one too, I would appreciate it.
>
> Raymond Maple
>
>
> ----- Original Message -----
> From: "Suhaib Siddiqi" <[EMAIL PROTECTED]>
> To: "'Raymond C. Maple '" <[EMAIL PROTECTED]>
> Sent: Friday, February 16, 2001 9:16 PM
> Subject: RE: [opendx-dev] Unresolved reference XmObjectAtPoint
>
>
> > How about trying MOTIF 2.1.3? Visit http://www.motifzone.net and
downlaod
> > from there precompiled MOTIF libraries for Linux.
> >
> > It would be helpful if you post the cut-and-paste of error message?
> > The XmObjectAtPoint is ib libXm.so(a) of MOTIF 2.1.3
> >
> > libXm.a:GadgetUtil.o:         U _XmObjectAtPoint
> > libXm.a:MenuShell.o:         U _XmObjectAtPoint
> > libXm.a:MenuUtil.o:         U _XmObjectAtPoint
> > libXm.a:Manager.o:         U _XmObjectAtPoint
> > libXm.a:RCMenu.o:         U _XmObjectAtPoint
> > libXm.a:Xm.o:000003c8 T _XmObjectAtPoint
> > libXm.a:ObsoXme.o:         U _XmObjectAtPoint
> >
> > Either your Lesstif libraries are missing this symbol (at least) or your
> > MOSt probably your link order of libraries is __wrong__ and symbols are
> not
> > getting resolved because of it.
> >
> > Suhaib
> >
> > -----Original Message-----
> > From: Raymond C. Maple
> > To: [email protected]
> > Sent: 2/16/2001 9:07 PM
> > Subject: [opendx-dev] Unresolved reference XmObjectAtPoint
> >
> > Hello,
> >    I am attempting to build opendx 4.1.0 under Suse linux 6.3.  The
> > compile goes OK, but the build fails on the linking of dxui with an
> > XmObjectAtPoint unresolved reference.  I have tried both the 1.2 and 2.0
> > Motif clones.  I also tried the updated Lesstif that shipped with Suse
> > 6.4, with the same results.  Is there a known fix for this problem?
> >
> >  BTW, I am currently using the precompiled 4.0.10 Suse 6.3 binaries
> > downloaded from the web page.  There are a LOT of problems with
> > interactors, that I hope are fixed in 4.1.0.
> >
> > Thanks,
> > Ray Maple
> >
> >
>
>
>

Reply via email to