>
> Try this at command line:
>
> ldd /usr/local/lib/couchdb/bin/couchjs
>
> What does it show?
>
All dependences for couchjs show up under that command, are any out-of-date?
ldd /usr/local/lib/couchdb/bin/couchjs
libm.so.6 => /lib64/libm.so.6 (0x0000003c54c00000)
libcurl.so.4 => /usr/local/lib/libcurl.so.4 (0x00002aaaaaac9000)
libidn.so.11 => /usr/lib64/libidn.so.11 (0x0000003c5e000000)
libldap-2.3.so.0 => /usr/lib64/libldap-2.3.so.0 (0x0000003c56800000)
librt.so.1 => /lib64/librt.so.1 (0x0000003c59800000)
libssl.so.6 => /lib64/libssl.so.6 (0x0000003c5dc00000)
libcrypto.so.6 => /lib64/libcrypto.so.6 (0x0000003c5cc00000)
libdl.so.2 => /lib64/libdl.so.2 (0x0000003c54800000)
libz.so.1 => /usr/lib64/libz.so.1 (0x0000003c55400000)
libjs.so => /usr/local/spidermonkey/lib64/libjs.so (0x00002aaaaad1a000)
libpthread.so.0 => /lib64/libpthread.so.0 (0x0000003c55000000)
libcrypt.so.1 => /lib64/libcrypt.so.1 (0x0000003c62600000)
libc.so.6 => /lib64/libc.so.6 (0x0000003c54400000)
liblber-2.3.so.0 => /usr/lib64/liblber-2.3.so.0 (0x0000003c56000000)
libresolv.so.2 => /lib64/libresolv.so.2 (0x0000003c5bc00000)
libsasl2.so.2 => /usr/lib64/libsasl2.so.2 (0x0000003c55800000)
/lib64/ld-linux-x86-64.so.2 (0x0000003c54000000)
libgssapi_krb5.so.2 => /usr/lib64/libgssapi_krb5.so.2
(0x0000003c5d400000)
libkrb5.so.3 => /usr/lib64/libkrb5.so.3 (0x0000003c5d800000)
libcom_err.so.2 => /lib64/libcom_err.so.2 (0x0000003c5b800000)
libk5crypto.so.3 => /usr/lib64/libk5crypto.so.3 (0x0000003c5d000000)
libkrb5support.so.0 => /usr/lib64/libkrb5support.so.0
(0x0000003c5c400000)
libkeyutils.so.1 => /lib64/libkeyutils.so.1 (0x0000003c5c000000)
libselinux.so.1 => /lib64/libselinux.so.1 (0x0000003c56c00000)
libsepol.so.1 => /lib64/libsepol.so.1 (0x0000003c57400000)
> Also: LD_LIBRARY_PATH is a bit fragile. Better is this, so you don't need
> any environment variables:
>
> echo "/usr/local/spidermonkey/lib64" >/etc/ld.so.conf.d/spidermonkey.conf
> ldconfig
>
ok i'll try this first.
> Even better is to set LD_RUN_PATH when you build couchdb, so that it has the
> location of its library built into the binary.
>
> B.
>
...then this.
