Hi,

I had a similar problem with SGI and it was gone when I set the
DXSHMEM environment variable to -1.  I don't know if it's gonna help
you.


Best,
Irek

********************************************
* Ireneusz SZCZESNIAK - research assistant *
* Tel: +48 (32) 231-73-19, extension 204   *
* http://www.iitis.gliwice.pl/~iszczesniak *
********************************************

On Wed, 24 Mar 2004, Mattijs Janssens wrote:

> Date: Wed, 24 Mar 2004 16:26:51 +0000
> From: Mattijs Janssens <[EMAIL PROTECTED]>
> Reply-To: [email protected]
> To: [email protected]
> Subject: [opendx-users] irix64 port using gcc
>
> Hello,
>
> I am having trouble getting 64bit OpenDX-4.3.2 to run when using gcc as
> a compiler. The dxexec coredumps, even if I run it by itself.
>
> It works fine it I compile it 32bit with gcc.
>
> I need to compile it with gcc since I need to link in my C++ libs which
> were compiled with gcc.
>
> The error I am getting is below. Does anybody have any experience with
> gcc + dx + 64bit?
>
> Regards,
>
> Mattijs
>
> turner<138> $DXROOT/bin_sgi/dxexec
> Open Visualization Data Explorer
> More Info at www.research.ibm.com/dx
> and www.opendx.org
> Version - 4.3.2
> Memory cache will use 1792 MB (112 for small items, 1680 for large)
>
>   0:  worker here [1025145]
> Bus error (core dumped)
>
>
> --
> /*---------------------------------------------------------*\
> | ===========           Mattijs Janssens                    |
> | \\        /           Development Engineer                |
> |  \\      /                                                |
> |   \\    /             Nabla Ltd.                          |
> |    \\  /              The Mews, Picketts Lodge            |
> |     \\/               Picketts Lane, Salfords,            |
> |     F ield            Surrey RH1 5RG.                     |
> |     O peration        Tel: +44 (0)1293 821272             |
> |     A nd              Email: [EMAIL PROTECTED]       |
> |     M anipulation     URL: http://www.Nabla.co.uk         |
> \*---------------------------------------------------------*/
>

Reply via email to