I had a similar problem and resolved it by uninstalling the 2.1 version of
motif_dev.  Unfortunately, I'm having other bad problems with 4.0.10 and
6.5.6f.  If I run some of the samples, I eventually get dxexec crashing with
a segmentation violation (sometimes in strcmp in src/exec/dpexec/d.c and
sometimes in other places).  The common thread between them is that they're
all happening in routines in libc.so.  Some info on the build:  I used gcc
2.95.2, mips4 ISA and n32 ABI.

I've also built an o32, mips2 version for some older systems (using an older
o32-enabled gcc).  Some of the samples crash it, but I've had more luck with
it.

Anyone have an idea what could be causing these crashes?  I've been beating
on this for a week or so with no luck.

****************************************************************************
***
Alan M. Ferrenberg ([EMAIL PROTECTED])
Manager, Research and Computational Science Support
UGA Computing and Networking Services

Get the latest information from UCNS!  Subscribe to our weekly e-mail
publication "UCNS Weekly News".  For more information, check out:

http://www.uga.edu/ucns/consult/casnews/

****************************************************************************
***


----- Original Message -----
From: <[EMAIL PROTECTED]>
To: <[email protected]>
Sent: Wednesday, February 09, 2000 8:43 AM
Subject: [opendx-dev] Bug in 4.0.10


I'm just wondering if anybody else has had this problem. I've got 4.0.10
plus
the latest patches (as of 2/8) it compiles fine on Irix 6.5.6f (well sort
of,
I'll get to that), and runs Ok until you try to open a control panel. BOOM,
core
dump with an assertion failure:

Assertion failed: r->x1 < r->x2, file Region.c, line 1242, pid 74048

Well, after much sleuthing, it appears that this error is occuring deep in
the
bowels of Motif. Now it turns out that the latest version of Irix sticks in
as
the default Motif version 2.1 (not 1.2 as on previous systems). Has anybody
else
gotten opendx to run under Motif 2.1?

The location which it blows is in src/uipp/base/ MainWindow::initialize line
250
(?):

    XtVaSetValues (this->main, XmNcommandWindowLocation,
XmCOMMAND_BELOW_WORKSPACE,
        XmNcommandWindow, this->commandArea, NULL);


Compile Problem:
The problem is in the installation of the software. Particularly, when all
of
the external libraries are added into libDX. The problem is that the search
path
in src/exec/Makefile (install-exec-local:) is hardcoded to look for the
libraries:

           lib="";                        \
            for j in /lib /usr/lib /usr/local/lib @LIBS@;  do  \

The sgi's now have 3 ABIs o32 (should almost never be used), n32, 64, and
the
libraries for each of these is stored in a different location:
o32 = /lib /usr/lib /usr/local/lib
n32 = /lib32 /usr/lib32 ..
64  = /lib64 ...

Since I compile with -n32, I had to set the line above to the following
           lib="";                        \
            for j in /usr/local/lib32 /lib32 /usr/lib32 /usr/local/lib
@LIBS@;
do  \

Note: the search path is specifically set to look in local/lib32 first (I
want
the latest stuff) and in local/lib last (some software installs here no
matter
what the ABI is).

Mark
--
   Mark Bolstad
   Manager, Visualization and Scientific Computing
   Lockheed-Martin Services Inc.
   [EMAIL PROTECTED]
   (919)-541-3604

Reply via email to