-
Notifications
You must be signed in to change notification settings - Fork 110
Troubleshooting
Leonardo Solis V edited this page Sep 21, 2019
·
10 revisions
When you don't know what to do ...
In case vendor-specific variables (e.g., $AMDAPPSDKROOT
) are utilized for the OpenCL setup specified in the user guideline, make sure they are correctly defined. Otherwise, resolve their definition manually.
For example, the shared library for an AMD GPU accelerator might be located in a different path to that defined by $AMDAPPSDKROOT
. In that case, it could be found this way:
% echo $AMDAPPSDKROOT
/opt/AMDAPPSDK-3.0
% cat /etc/ld.so.conf.d/amdgpu-pro-x86_64.conf
/opt/amdgpu-pro/lib/x86_64-linux-gnu
% ls -asl /opt/amdgpu-pro/lib/x86_64-linux-gnu
...
0 lrwxrwxrwx 1 root root 14 Nov 30 2016 libOpenCL.so -> libOpenCL.so.1
28 -rw-r--r-- 1 root root 27336 Nov 30 2016 libOpenCL.so.1
% export GPU_INCLUDE_PATH=$AMDAPPSDKROOT/include
% export GPU_LIBRARY_PATH=/opt/amdgpu-pro/lib/x86_64-linux-gnu
Check vendor specific guidelines to setup both OpenCL platform correctly!
Go to Wiki home.
AutoDock for GPUs and other accelerators.
Contents