Curl links to various system libraries

[vbraun]

I'm not sure this is really a problem, but curl picks up nss, nspr, cyrus sasl, and openldap from the system libraries on my machine:

$ ldd /home/vbraun/.hashdist/bld/curl/w65k3ck32gj7/lib/libcurl.so
    linux-vdso.so.1 (0x00007ffdcc1f1000)
    libidn.so.11 => /home/vbraun/.hashdist/bld/curl/w65k3ck32gj7/lib/../../../libidn/3gj4oyyum5cw/lib/libidn.so.11 (0x00007f54e08de000)
    libssl.so.1.0.0 => /home/vbraun/.hashdist/bld/curl/w65k3ck32gj7/lib/../../../openssl/yvzdmkilwjmd/lib/libssl.so.1.0.0 (0x00007f54e0664000)
    libcrypto.so.1.0.0 => /home/vbraun/.hashdist/bld/curl/w65k3ck32gj7/lib/../../../openssl/yvzdmkilwjmd/lib/libcrypto.so.1.0.0 (0x00007f54e0210000)
    liblber-2.4.so.2 => /lib64/liblber-2.4.so.2 (0x00007f54dffc9000)
    libldap-2.4.so.2 => /lib64/libldap-2.4.so.2 (0x00007f54dfd76000)
    libz.so.1 => /home/vbraun/.hashdist/bld/curl/w65k3ck32gj7/lib/../../../zlib/v6anirfvk2op/lib/libz.so.1 (0x00007f54dfb5c000)
    libc.so.6 => /lib64/libc.so.6 (0x00007f54df79b000)
    libdl.so.2 => /lib64/libdl.so.2 (0x00007f54df596000)
    libresolv.so.2 => /lib64/libresolv.so.2 (0x00007f54df37b000)
    libsasl2.so.3 => /lib64/libsasl2.so.3 (0x00007f54df15d000)
    libssl3.so => /lib64/libssl3.so (0x00007f54def1b000)
    libsmime3.so => /lib64/libsmime3.so (0x00007f54decf4000)
    libnss3.so => /lib64/libnss3.so (0x00007f54de9cc000)
    libnssutil3.so => /lib64/libnssutil3.so (0x00007f54de79f000)
    libplds4.so => /lib64/libplds4.so (0x00007f54de59b000)
    libplc4.so => /lib64/libplc4.so (0x00007f54de395000)
    libnspr4.so => /lib64/libnspr4.so (0x00007f54de156000)
    libpthread.so.0 => /lib64/libpthread.so.0 (0x00007f54ddf39000)
    /lib64/ld-linux-x86-64.so.2 (0x00005638e5a1e000)
    libcrypt.so.1 => /lib64/libcrypt.so.1 (0x00007f54ddd02000)
    librt.so.1 => /lib64/librt.so.1 (0x00007f54ddafa000)
    libfreebl3.so => /lib64/libfreebl3.so (0x00007f54dd87c000)

Thats potentially a problem for reproducible builds if it drags in that many host specifics?

[ahmadia]

Thats potentially a problem for reproducible builds if it drags in that many host specifics?

Absolutely, thanks for noting this. I'd say maybe half of those are fairly portable libraries, but I don't know/recognize the other half.

[jcftang]

I've tried packaging nss and nspr but I wasn't too sucessful the last time I tried

[certik]

That's definitely a problem --- the philosophy of Hashdist is that if you want to link to system wide libraries, you can. But if you don't want to, you can build everything from source. So we have to fix this.