The standard CUDA driver installer for the Mac installs only one library:
/usr/local/cuda/lib/libcuda.dylib
so applications will almost certainly need to send along any other
libraries they need. The beta Einstein application sends
libcudart.dylib, libcufft.dylib and libtlshook.dylib along with the
science app.
They rename these before sending, then at run time they copy them
into the slot directory with the proper names.
If the application also needs to access libcuda.dylib, it needs to
add /usr/local/cuda/lib/ to the library search path. The BOINC
client already adds the slot and project directories to the library
search path environment variable LD_LIBRARY_PATH.
Also, I just noticed that changesets 19972 and 20061 never made it
into the 6.10 branch. I've made those changes now and built BOINC
6.10.27 for the Mac. This should fix some ATI issues, and also adds
the slot and project directories to the library search path
environment variable DYLD_LIBRARY_PATH. However, I don't expect
these changes to affect the running of CUDA applications.
Cheers,
--Charlie
At 7:34 PM -0800 1/8/10, Paul D. Buck wrote:
>Collatz is not sending down the libs with the application but they
>cannot be found yet. I suggested adding the links to the
>application using the standard BOINC mechanisms.
>
>If I knew how to fake this locally by editing config files I would
>see if it works. Shipping only the 32-bit BOINC application has
>allowed the discovery of the GPU for CUDA. I still wonder if the
>application is being compiled in the 64-bit space and so it is not
>finding the 32-bit libraries regardless.
>
>As always, willing to lend a hand if someone tells me what they want
>me to try ... though my 8800 card is going to suck swamp water for
>doing work ...
>
>
>On Jan 8, 2010, at 2:47 PM, Charlie Fenton wrote:
>
>> This is the same problem that einst...@home is having with their
>>beta CUDA application on the Mac. We will be investigating next
>>week when they return from vacation.
>>
>> Cheers,
>> --Charlie
>>
>> At 12:07 AM -0800 1/8/10, Paul D. Buck wrote:
>>> Collatz has an application ready to go also. Though it is
>>>currently compiled as a 64-bit version.
>>>
>>> I am not sure if this is the cause of the issue where even with
>>>an app info file I cannot get work or there is something going on
>>>with the system still...
>>>
>>> Hmm, am getting work now, but also getting this error:
>>>
>>> dyld: Library not loaded: @rpath/libcudart.dylib
>>> Referenced from: /Library/Application Support/BOINC
>>>Data/slots/5/../../projects/boinc.thesonntags.com_collatz/collatz_2.01_i686-apple-darwin__cuda
>>> Reason: image not found
>>>
>>>
>>> On Jan 7, 2010, at 5:35 PM, Charlie Fenton wrote:
>>>
>>>> That is what einst...@home is doing, though they don't have that
>>>> working yet. You might want to collaborate with them. They are
>>>> setting environment variables DYLD_LIBRARY_PATH and LD_LIBRARY_PATH
>>>> in their application, and using the @rpath macro.
>>>>
>>>> The standard installation of the CUDA driver on the Mac includes only
>>>> libcuda.dylib. and this is the only one used or checked by the BOINC
>>>> client. You cannot assume that the runtime and other libraries have
>>>> be installed on the system.
>>>>
>>>> At 9:24 AM -0600 1/7/10, Jon Sonntag wrote:
>>>>
>>>>> I assume I will need to include the cuda runtime library along
>>>>>with the cuda
>>>>>
>>>>> app so that the MAC user doesn't have to set any environment
>>>>>
>>>>> variables or create symbolic links.
>>>>>
>>
_______________________________________________
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.
