Just in case you are interested, you can see why it compiles on anything
other than alphax in uipp/widgets/XmDX.h. Its a temp variable that the
macro doesn't reference on other architectures. Looks to like just
declaring it is right. Looks like the declaration was accidentally removed
in CVS version 1.10.
Greg
Randall Hopper
<[EMAIL PROTECTED]> To:
[email protected]
Sent by: cc:
[EMAIL PROTECTED] Subject: [opendx-users] Re:
OpenDX 4.2 Compiling trouble on Tru64 Unix
son.ibm.com
08/23/2002 02:31 PM
Please respond to
opendx-users
Richard Cook:
|I've had some adventures trying to get OpenDX 4.2 to compile on our
|Compaq Tru64 Unix machines here. First, there were several errors of
|the type:
|ColorMapEditor.c: In function `SetValues':
|ColorMapEditor.c:889: `dx_l' undeclared (first use in this function)
|For the record, I fixed each of these by adding as the first line of
|the function in which the error occured the following:
|XtArgVal dx_l;
Good question. After doing a few quick greps, I'm not sure off-hand how DX
is compiling. I notice your solution in some spots:
#if defined(alphax)
XtArgVal dx_l;
#endif
but not others.
|Unresolved:
|yylineno
|collect2: ld returned 1 exit status
|*** Exit 1
|
|In reference to earlier threads about this being caused by yacc or
|bison
...
|gps01{rcook}104: which yacc
|/usr/bin/yacc
Yep. Or flex. Do this after configure:
> grep LEX Makefile
to see what DX is running. Here on our SGI net we're running flex, without
any special options. But with some flex's on other platforms, I've had to
add "-l" to the flex command-line in the post-configure Makefiles before
building to get this defined (easy with a recursive perl run: find . -name
Makefile | xargs perl -pi -e 's/flex/flex -l/'). Probably a flex
version-related problem, but I'm not a yacc/flex expert.
Randy
--
Randall Hopper (mailto:[EMAIL PROTECTED])
Lockheed Martin Operation Support
EPA Scientific Visualization Center
US EPA N127-01; RTP, NC 27711
