Re: isis startup error

John E. Davis wrote:
> Roderick Johnstone <rmj_at_email.domain.hidden>>> What does `isis --version` produce?
>> linux> isis --version
>> ISIS version 1.4.7; S-Lang version 2.0.4
> [...]
>> The slang that I'm building against is that distributed with ciao 3.4. I
> 
> I am a bit puzzled by this.  On our system, ciao-3.4 distributes 
> libslang.so.1.4.9, and not libslang.so.2.0.4.
Well, there are actually several libslangs in ciao 3.4:

linux> cd /data/soft3/cxc/v3.4/linux
linux> find . -name "libslang.so*"
./lib/libslang.so
./lib/libslang.so.1
./lib/libslang.so.1.4.9
./ots/slang/lib/libslang.so
./ots/slang/lib/libslang.so.2
./ots/slang/lib/libslang.so.2.0.4
./ots/slang.v1.4.9/lib/libslang.so
./ots/slang.v1.4.9/lib/libslang.so.1
./ots/slang.v1.4.9/lib/libslang.so.1.4.9
./ots/slang.v1.4.9/src/elfobjs/libslang.so
./ots/slang.v1.4.9/src/elfobjs/libslang.so.1.4.9

I was careful to link isis against the ots/slang/lib slang.

>  What does
> 
>    ldd `/path/to/isis`
 >
 > produce?  I suspect that you are linked to /usr/lib/libslang.so.2.0.4.

linux> ldd ./isis
         linux-gate.so.1 =>  (0xffffe000)
         libreadline.so.5 => 
/data/soft3/heasoft/headas-6.2/i686-pc-linux-gnu-libc2.3.4/lib/libreadline.so.5 
(0xf7fd0000)
         libtermcap.so.2 => /lib/libtermcap.so.2 (0xf7fae000)
         libslang.so.2 => 
/data/soft3/cxc/v3.4/linux/ots/slang/lib/libslang.so.2(0xf7eeb000)
         libcfitsio_3.03.so => 
/data/soft3/heasoft/headas-6.2/i686-pc-linux-gnu-libc2.3.4/lib/libcfitsio_3.03.so 
(0xf7d6c000)
         libpng12.so.0 => /usr/lib/libpng12.so.0 (0x41655000)
         libdl.so.2 => /lib/libdl.so.2 (0x4116b000)
         libX11.so.6 => /usr/X11R6/lib/libX11.so.6 (0x41171000)
         libg2c.so.0 => /usr/lib/libg2c.so.0 (0xf7d4e000)
         libm.so.6 => /lib/tls/libm.so.6 (0x41146000)
         libgcc_s.so.1 => /lib/libgcc_s.so.1 (0x41463000)
         libc.so.6 => /lib/tls/libc.so.6 (0x41019000)
         libz.so.1 => /usr/lib/libz.so.1 (0x41252000)
         /lib/ld-linux.so.2 (0x41000000)

Sorry about the bad wrapping, but yes, it is linked against 
libslang.so.2.0.4.


> If so, I would unset all SLSH_* environment variables that ciao sets,
> as well as LD_LIBRARY_PATH, and re-run isis.

It still fails in the same way.

>  If it still fails, what
> does `locate structfuns` produce?

linux> locate structfuns
/soft3/cxc/v4.0b1/ciao-beta1-4.0/ots/share/slsh/help/structfuns.hlp
/soft3/cxc/v4.0b1/ciao-beta1-4.0/ots/share/slsh/structfuns.sl
/soft3/cxc/v3.4/linux/ots/slang/share/slsh/structfuns.sl

So, locate has to be run on the server and these files appear as 
/data/soft3/... (ie nfs mounted filesystem) on the clients. The locate 
database does not index files from nfs filesystems which is why I have 
to run it on the server and it drops the /data from the front of the 
path because it finds the structfuns.sl on the real filesystem.

I guess it seems to have the structfuns.sl and in the ots/slang tree 
which is where the libslang.so.2.0.4 is, so I'm not sure why its not 
being picked up. Maybe there is an environment variable I can set to 
force it to look there.

Thanks.

Roderick
-- 
Roderick Johnstone                          Email: rmj_at_email.domain.hiddenX-ray Astronomy Group                       Phone: +44 1223 766656
Institute of Astronomy                      Mobile:   07989 809095
Madingley Road, Cambridge CB3 0HA, UK       Fax:   +44 1223 337523