mmm, I see it's not necessary to do: LD_LIBRARY_PATH=../../projects/test.test/, simply wrapping the application:
#!/bin/sh ../../projects/test.test/hello_cuda2 "$@" works. El 19 de octubre de 2009 13:54, Bernd Machenschalk < [email protected]> escribió: > Francisco Sanz García wrote, On 19.10.2009 12:58 Uhr: > >> Ok, then, if the script is: >> >> #!/bin/sh >> echo $PWD > /tmp/libr.log >> echo $LD_LIBRARY_PATH >> /tmp/libr.log >> LD_LIBRARY_PATH=../../projects/test.test/ >> ../../projects/test.test/hello_cuda2 "$@" >> echo $PWD >> /tmp/libr.log >> echo $LD_LIBRARY_PATH >> /tmp/libr.log >> >> then: cat libr.log >> >> ~/BOINC/samples/slots/0 >> >> > > Hm. > > Anybody has any clue why > >> ../../projects/test.test/ >> >> > > works better than > > ../../projects/test.test:.:../.. >> >> > > as LD_LIBRARY_PATH? > > Is setting the LD_LIBRARY_PATH actually necessary to make the script work? > > Or what else is affected by the script? > > From a different user I know that it works bot if you call the App as a > sub-process and exec the App, so the pid doesn't seem to make a difference. > > > Still confused... > > Bernd > > _______________________________________________ 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.
