Ah, that's the problem. That machine is running client version 6.2.18 from the Ubuntu package. This is the latest version that's hit Ubuntu Jaunty (I see that Karmic will have 6.4.5, which still isn't good enough), so I'm going to assume I shouldn't be relying on this behaviour yet.
Thanks for your help, David & Eric. Michael David Anderson wrote: > Which client version are you using? > The current versions (6.6.40 and 6.10.6) > set LD_LIBRARY_PATH to include the project directory, > followed by the slot directory. > > -- David > > Michael Melanson wrote: > >> Hi everyone, >> >> I'm trying to get an application running that links against some shared >> libraries, which I ship as part of a multi-file application. >> Unfortunately, when the clients run the application, the dynamic linker >> can't find these dependencies, and so the application fails to run. I >> have checked that on my test client, all the libraries are being >> downloaded into the right directory. >> >> On the Wiki (http://boinc.berkeley.edu/trac/wiki/AppDev) it says that >> the client should be setting LD_LIBRARY_PATH to include the project >> directory when it runs the application. When I run the application >> binary from the project directory on my test client, it outputs the same >> error as appears in the logs. When I run it with LD_LIBRARY_PATH=. then >> it runs fine. This tells me that the BOINC client isn't setting >> LD_LIBRARY_PATH. >> >> Does anyone have any idea what's going on here? >> >> >> Thanks in advance, >> >> Michael Melanson >> _______________________________________________ >> boinc_dev mailing list >> [email protected] >> http://lists.ssl.berkeley.edu/mailman/listinfo/boinc_dev >> To unsubscribe, visit the above URL and >> (near bottom of page) enter your email address. >> > > _______________________________________________ boinc_dev mailing list [email protected] http://lists.ssl.berkeley.edu/mailman/listinfo/boinc_dev To unsubscribe, visit the above URL and (near bottom of page) enter your email address.
