Okay its very weird your CFITSIO.so isn't attempting to load *any*
libcfitsio -- I'm not sure if this is a difference in build methods or
if I'm missing something?
On our centos7 build of Starlink, I get the following from the
installed CFITSIO.so (note the libcfitsio.so.7)
ldd /starlink-build/installations/intermediate/star-nightly-onlystarlink/Perl/lib/perl5/site_perl/5.26.1/x86_64-linux/auto/Astro/FITS/CFITSIO/CFITSIO.so
linux-vdso.so.1 => (0x00007ffd439c0000)
libcfitsio.so.7 =>
/starlink-build/installations/intermediate/star-nightly/lib/libcfitsio.so.7
(0x00007f2b0dc7a000)
libm.so.6 => /lib64/libm.so.6 (0x00007f2b0d959000)
libc.so.6 => /lib64/libc.so.6 (0x00007f2b0d596000)
libcurl.so.4 => /lib64/libcurl.so.4 (0x00007f2b0d32d000)
/lib64/ld-linux-x86-64.so.2 (0x00005555cf44b000)
libidn.so.11 => /lib64/libidn.so.11 (0x00007f2b0d0f9000)
libssh2.so.1 => /lib64/libssh2.so.1 (0x00007f2b0cecf000)
libssl3.so => /lib64/libssl3.so (0x00007f2b0cc83000)
libsmime3.so => /lib64/libsmime3.so (0x00007f2b0ca5b000)
libnss3.so => /lib64/libnss3.so (0x00007f2b0c731000)
libnssutil3.so => /lib64/libnssutil3.so (0x00007f2b0c504000)
libplds4.so => /lib64/libplds4.so (0x00007f2b0c2ff000)
libplc4.so => /lib64/libplc4.so (0x00007f2b0c0fa000)
libnspr4.so => /lib64/libnspr4.so (0x00007f2b0bebc000)
libpthread.so.0 => /lib64/libpthread.so.0 (0x00007f2b0bc9f000)
libdl.so.2 => /lib64/libdl.so.2 (0x00007f2b0ba9b000)
libgssapi_krb5.so.2 => /lib64/libgssapi_krb5.so.2
(0x00007f2b0b84e000)
libkrb5.so.3 => /lib64/libkrb5.so.3 (0x00007f2b0b565000)
libk5crypto.so.3 => /lib64/libk5crypto.so.3 (0x00007f2b0b332000)
libcom_err.so.2 => /lib64/libcom_err.so.2 (0x00007f2b0b12e000)
liblber-2.4.so.2 => /lib64/liblber-2.4.so.2 (0x00007f2b0af1e000)
libldap-2.4.so.2 => /lib64/libldap-2.4.so.2 (0x00007f2b0acca000)
libz.so.1 => /lib64/libz.so.1 (0x00007f2b0aab4000)
libssl.so.10 => /lib64/libssl.so.10 (0x00007f2b0a841000)
libcrypto.so.10 => /lib64/libcrypto.so.10 (0x00007f2b0a3e0000)
librt.so.1 => /lib64/librt.so.1 (0x00007f2b0a1d7000)
libkrb5support.so.0 => /lib64/libkrb5support.so.0
(0x00007f2b09fc9000)
libkeyutils.so.1 => /lib64/libkeyutils.so.1 (0x00007f2b09dc5000)
libresolv.so.2 => /lib64/libresolv.so.2 (0x00007f2b09baa000)
libsasl2.so.3 => /lib64/libsasl2.so.3 (0x00007f2b0998d000)
libselinux.so.1 => /lib64/libselinux.so.1 (0x00007f2b09765000)
libcrypt.so.1 => /lib64/libcrypt.so.1 (0x00007f2b0952e000)
libpcre.so.1 => /lib64/libpcre.so.1 (0x00007f2b092cc000)
libfreebl3.so => /lib64/libfreebl3.so (0x00007f2b090c8000)
On Mon, 7 Jan 2019 at 10:44, Tom Marsh <[log in to unmask]> wrote:
>
> I did have LD_LIBRARY_PATH defined
>
> before setting up starlink installation environment
>
> ldd CFITSIO.so
> linux-vdso.so.1 => (0x00007ffedd1c8000)
> libm.so.6 => /lib64/libm.so.6 (0x00007fc6ecda8000)
> libc.so.6 => /lib64/libc.so.6 (0x00007fc6ec9db000)
> /lib64/ld-linux-x86-64.so.2 (0x00007fc6ed515000)
>
> after:
>
> source ~/github/starlink-sourceme.sh
> ldd CFITSIO.so
> linux-vdso.so.1 => (0x00007ffd4fb8e000)
> libm.so.6 => /lib64/libm.so.6 (0x00007fd0ffc81000)
> libc.so.6 => /lib64/libc.so.6 (0x00007fd0ff8b4000)
> /lib64/ld-linux-x86-64.so.2 (0x00007fd1003ee000)
>
> ########################################################################
>
> To unsubscribe from the STARDEV list, click the following link:
> https://www.jiscmail.ac.uk/cgi-bin/webadmin?SUBED1=STARDEV&A=1
--
Dr Sarah Graves
Scientific Programmer
East Asian Observatory/JCMT
[log in to unmask]
########################################################################
To unsubscribe from the STARDEV list, click the following link:
https://www.jiscmail.ac.uk/cgi-bin/webadmin?SUBED1=STARDEV&A=1
|