Re: gsl module

Yes that indeed was the problem. Kind of a decieving error!
thanks alot
~~Arik

Michael Noble wrote:

>>isis> require("gsl");
>>Error linking to /data/lacuna/slang/lib/slang/v2/modules/gsl-module.so: 
>>/data/lacuna/slang/lib/slang/v2/modules/gsl-module.so: cannot open 
>>shared object file: No such file or directory
>>    
>>
>
>This message is sometimes misleading.  For example, it can be emitted
>when symbols within a shared library cannot be resolved at runtime,
>or when other binary incompatibilities arise.
>
>In this case, I wonder if the issue is mixing 64-bit code with 32?
>
>For example:
>
>	 % file /data/lacuna//slang/isis-1.4.8/bin/isis.exe 
>
>	 /data/lacuna//slang/isis-1.4.8/bin/isis.exe:
>	 ELF 32-bit LSB executable, Intel 80386, version 1 (SYSV),
>	 for GNU/Linux 2.4.1, dynamically linked (uses shared libs)
>
>but
>
> 	% file /data/lacuna/slang/lib/slang/v2/modules/gsl-module.so
>
>	 ELF 64-bit LSB shared object, AMD x86-64, version 1 (SYSV),
>	 not stripped
>
>And if I explicitly use a 32-bit slsh
>
> 	% cd /data/lacuna/slang/lib/slang/v2/modules/gsl-module.so
>
>	
> 	%  file /soft/isis/bin/slsh
>	/soft/isis/bin/slsh: ELF 32-bit LSB executable, Intel 80386 ...
>
> 	%  /soft/isis/bin/slsh
>	slsh>  import("gsl")
>
>I get the same error as you do in ISIS:
>
>	Error linking to gsl-module.so: gsl-module.so:
>	cannot open shared object file: No such file or directory
>
>Just a thought,
>Mike
>
>
>  
>


-- 
Arik Mitschang
(617)496-7237
-----------------
HEAD CXC DSOPS
-----------------
"sdrawkcab si siht"

----
You received this message because you are
subscribed to the isis-users list.
To unsubscribe, send a message to
isis-users-request_at_email.domain.hiddenwith the first line of the message as:
unsubscribe