On the main BOINC page, they announce this on August 9, 2005. That may be fine and it may not be. Will the new BOINC client be able to run with any installed version of libcurl? I run Red Hat Enterprise Linux 3 that currently has curl-devel-7.10.6-6.rhel3 as the rpm package with /usr/lib/libcurl.so.2.0.2 in it.

I have had the misfortune with other applications of having either too new (rarely) or too old (more often the case) libraries, and I would hate to be unable to run BOINC because of this. Will the developers ensure that BOINC will run with all current libcurl versions, including those in RHEL3?

---

The Boinc binary is statically linked and should include all needed libs.
You can figure it out with ldd. For example "ldd boinc_client" will show you if the binary is static or if not then it´ll show you the libs it´s liked against.

regards
Crunch3r

---

Join BOINC United now!

The Boinc binary is statically linked and should include all needed libs.
You can figure it out with ldd. For example "ldd boinc_client" will show you if the binary is static or if not then it´ll show you the libs it´s liked against.

regards
Crunch3r

Well, the present (4.43) version says:

ldd boinc
libdl.so.2 => /lib/libdl.so.2 (0x00270000)
libm.so.6 => /lib/tls/libm.so.6 (0x003fd000)
libpthread.so.0 => /lib/tls/libpthread.so.0 (0x001e8000)
libc.so.6 => /lib/tls/libc.so.6 (0x0096f000)
/lib/ld-linux.so.2 => /lib/ld-linux.so.2 (0x00c7a000)

which means it is not totally statically linked. So will libcurl be statically linked, or will it rely on a dynamically linked version on my machine? And, if the latter, will it be satisfied by any libcurl that happens to be there or will it insist on one not the same as the latest my distro supports?

Obviously, I cannot do ldd on the BOINC client that has not yet been released.

---