I guess this should not have worked for you. After looking a little closer, the entire path was specified in the mdf file:

LOADABLE /usr/local/dx/modules_linux/PathInterpolate;

I checked another module, compiled it and left the binary in the local directory. That module ran fine.

So it appears custom modules work fine for me on both Linux (RH7) and Irix. Sorry I could not be more help.

Jeff


At 11:30 AM 7/11/01 -0400, you wrote:

I just tried that and it didn't work.  I got the same error.

I also just tried it on a NT4 system and got what appeared to be a similar
problem.

Admittedly, years ago with 3.1.4B, this sort of this worked on SGI and
other platforms...

Thanks.


Jeff Braun <[EMAIL PROTECTED]>@opendx.watson.ibm.com on 07/11/2001 10:42:08
AM

Please respond to [email protected]

Sent by:  [EMAIL PROTECTED]


To:   [email protected]
cc:
Subject:  Re: [opendx-users] custom modules on linux



Sorry one small typo:

At 08:30 AM 7/11/01 -0600, you wrote:
>I just tested a loadable module on Linux (RH7) and seem to have the same
>(similar) problem.
>
>For example, when I load PathInterpolate.mdf, I get an error "Can not load
>/usr/local/dx/modules_linux/PathInterpolate". Then when I run the network,
>I get an error the function PathInterpolate does exist.

should read "the function PathInterpolate does NOT exist."

>If I copy PathInterpolate into /usr/local/dx/modules_linux then everything
>loads and runs fine.
>
>I will check on SGI and try to look at in more detail later why the binary
>is not loading from the local directory.
>
>Jeff
>
>
>At 10:00 PM 7/10/01 -0400, you wrote:
>
>>I recently tried to move some custom loadable modules from AIX to Linux
>>(RH7).  The modules appeared to compile and link just fine on Linux.
Using
>>the same mdf on AIX but pointing to the Linux binary doesn't seem to
work.
>>I can put the module down on the canvas in the VPE.  When I execute, I
get
>>an error that the function doesn't exist.  This is consistent when I try
to
>>run in script mode and invoke the module.  I get the same error.  On AIX,
>>all of this works correctly.  Has anyone seen this problem?  It's a bit
>>puzzling.  Thanks.

Reply via email to