This is a proposal including a first attempt for a new ebuild for ATI/AMD's stream-sdk. The packaging changed, therefor the old one from rion overlay doesn't work anymore. Proposed package name: dev-util/ati-stream-sdk-bin-2.01.ebuild Reproducible: Always Steps to Reproduce:
Created attachment 219465 [details] the actual ebuild
Hi, In fact, the original one was taken from our repo. I just added yours[1]. You can layman -a pentoo. Thx for this ebuild! [1] http://trac.pentoo.ch/changeset/1439
Two remarks: 1. it doesnt need ati-drivers as dependency you can use it without a GPU on any CPU that supports SSE3 2. libOpenCL.so will conflict with nvidia-drivers, nvidia-drivers provides libOpenCL.so too
Created attachment 244461 [details] new ebuild for version 2.2 New ebuild for new version. The location of some files changed, dependency on ati-drivers removed, as this SDK also works on CPU.
Installed this ebuild on my ATI 5870 and everything works as expected. Thanks! Would love to see this ebuild make it into sunrise at least.
(In reply to comment #3) > Two remarks: > > 1. it doesnt need ati-drivers as dependency you can use it without a GPU on any > CPU that supports SSE3 > 2. libOpenCL.so will conflict with nvidia-drivers, nvidia-drivers provides > libOpenCL.so too > Maybe this could be fixed by not creating the symlinks in to /usr/lib but setting up LD_LIBRARY_PATH through a file in /etc/env.d ?
(In reply to comment #6) > (In reply to comment #3) > > Two remarks: > > > > 1. it doesnt need ati-drivers as dependency you can use it without a GPU on any > > CPU that supports SSE3 > > 2. libOpenCL.so will conflict with nvidia-drivers, nvidia-drivers provides > > libOpenCL.so too > > > > Maybe this could be fixed by not creating the symlinks in to /usr/lib but > setting up LD_LIBRARY_PATH through a file in /etc/env.d ? > Two more comments to the comment. First, SDK 2.2 actually supports SSE2+, sorry for being a pedant. Second,the libOpenCL conflict can be fixed in an easier way. Thanks to the ICD extension supported by NVidia and AMD, either implementation of libOpenCL is sufficient. Just have ati-stream-sdk and nvidia-drivers add a link to libopencl if no such link already exists. A correct setup of the ICD extension (/etc/OpenCL) is a requirement of both libraries anyhow.
(In reply to comment #7) > > Two more comments to the comment. First, SDK 2.2 actually supports SSE2+, sorry > for being a pedant. If you we're actually a pedant you'd check that this comment refers to earlier version of SDK which does not support SSE2 ;) > Second,the libOpenCL conflict can be fixed in an easier way. Thanks to the ICD > extension supported by NVidia and AMD, either implementation of libOpenCL is > sufficient. Just have ati-stream-sdk and nvidia-drivers add a link to libopencl > if no such link already exists. A correct setup of the ICD extension > (/etc/OpenCL) is a requirement of both libraries anyhow. I need to check that again. In theory you're right but my programs didnt work when linked against nvidia's libOpenCL (I've got /etc/OpenCL properly configured).
> If you we're actually a pedant you'd check that this comment refers to earlier > version of SDK which does not support SSE2 ;) Damn! My pedantry is weak, the response to the comment was after the SDK came out, but not the original post, I bow to your superior pedantry. > I need to check that again. In theory you're right but my programs didnt work > when linked against nvidia's libOpenCL (I've got /etc/OpenCL properly > configured). Speaking from my own experience, it works fine. I'm actually developing a OpenCL-GL render engine and simulator for both platforms at once. I installed ati-stream-sdk after the nvidia drivers, and just deleted the libOpenCL.so to get them to install. I've also reinstalled the nvidia-drivers since then, again just deleting the libOpenCL.so to get them to reinstall. At first AMD's library was more reliable but nowadays they're both stable, at least in this respect.
Created attachment 249760 [details] fixed ebuild To be able to compile the example codes some make include files (e.g. openclskdfefs.mk and openclsdkrules.mk) were missing. Therefore it is necessary to install the "make" subfolder too (if example use flag is enabled). A fixed ebuild is attached.
Created attachment 249938 [details] reworked ebuild Reworked the ebuild: OpenCL (include/CL) and cal header are now installed into /usr/include; libOpenCL and libatiocl are installed into /usr/lib(32/64) examples and docs are installed into /usr/share/doc/${PF} /opt/${PF} is kept since the original file structure and shipped versions of glut/GLEW are expected by the kernel compiler/loader but the files installed into /usr subfolders are replaced by symlinks This should simplify working with OpenCL since no extra include or linker paths have to be specified. amd64 and multilib use flags are now respected (should install only 64bit versions if no-multilib amd64 arch) Further testing and experiences are welcome
Hi, I figured I'd step in the discussion as I'm doing regular usage of both ati stream and nvidia cuda. I prefered the old ebuilds, as the one you did will block cuda sdk, and will block on nv libOpenCL.so too. Also since it's full of bins, it should clearly go in /opt/* IMHO. I made an eselect-opencl ebuild [1], along with an ati-stream ebuild [2] in the pentoo overlay. This way we can have both nv and ati sdks on the same system, and select which one we want for some opencl fun, much like the eselect opengl stuff. Still the multilib stuff needs fixing in my ebuild, but that should be now fairly easy based on your work :-) [1] http://trac.pentoo.ch/browser/portage/trunk/app-admin/eselect-opencl [2] http://trac.pentoo.ch/browser/portage/trunk/dev-util/ati-stream-sdk-bin
FYI: While it might theoretically be possible to use this SDK with nVidia cards, the license only allows usage with ATi/AMD hardware. Since AMD has renamed it to "AMD APP SDK", I would suggest ebuilds all be moved to amd-app-sdk-bin-*. Finally, version 2.1 should ideally be added to the tree also, since 2.2+ are broken for multi-GPU, and in general slower than 2.1 on the 5xxx models.
pentoo's eselect-opencl doesn't do the header symlinks...
I'm going to start the process of getting this into portage. The multilib foo in the current ebuilds need a bit of cleaning, as do a few other things. When I have a semi-workable ebuild, it will show up in my dev overlay ('c1pher'). I will likely move it into portage soon after that. @spock We should probably coordinate a bit with this as far as the potential use of eselect opencl (or however else we decide to handle the potential library collisions. I haven't dug into it enough just yet to know for sure =P) Thanks to everyone who got this ball rolling. It is making my job a lot easier!
Please be sure to add 2.1 also; there are major problems with 2.2 and 2.3: - With 2.3, performance drops by 5-10% over 2.2 and older - With both 2.2 and 2.3, OpenCL applications (and X server?) use 100% CPU (should be near 0% like with 2.1) Renaming the pentoo overlay's 2.2 ebuild to 2.1, and making the missing /usr/include/CL symlink works.
As of today ati-stream-drivers-2.3 and ati-stream-drivers-2.1 are both in my dev overlay ('c1pher') in what I believe to be a more or less working state. It would be very beneficial for people to quickly check out that overlay and test some of their code etc with my versions of the ebuilds so that I can work out any kinks before moving this to portage. Some notes: Currently, I have this blocking nvidia-cuda-*. I hope to resolve this soon in the future. If all goes well, I aim to have them hit portage this time next week.
Comments on c1pher's ebuilds: - Why are these fetch restricted? - Shouldn't the package be named ati-stream-sdk-bin? - No support for eselect?
I tried to use your overlay c1pher, but it blocks on nvidia-cuda-sdk which I need as well. I second the use of an eselect mechanism, or if that's not possible can you not use use-flags to enable installing the headers and symbolic link to the library? Perhaps only these use flags would block on nvidia-cuda-sdk?
(In reply to comment #18) > Comments on c1pher's ebuilds: > - Why are these fetch restricted? > - Shouldn't the package be named ati-stream-sdk-bin? > - No support for eselect? > Agreed, why don't you just take my crappy eselect-opencl [1] and do the needed corrections if any? Also most atiocl projects checks for a ATISTREAMSDKROOT env var to find the common makefiles and will fail miserably. [1]http://trac.pentoo.ch/browser/portage/trunk/app-admin/eselect-opencl
AMD APP SDK 2.4 released. Have anyone ebuild?
Created attachment 272449 [details] Ebuild version bump to AMD APP SDK 2.4 I've uploaded a rough and dirty ebuild that supports AMD APP SDK 2.4. It's just a modified version of the ebuild for ATI Stream SDK 2.3 from the pentoo overlay. The ebuild has been renamed to "dev-util/amd-app-sdk-bin" and the installation folder now defaults to /opt/amd-app-sdk. It installs perfectly on my 64-bit system, but I believe it needs to be modified to support 32-bit platforms. Also, for some reason it failed to create symlinks for the libOpenCL.so file. If you get errors about OpenCL programs unable to find libOpenCL.so, simply create a symlink from /opt/amd-app-sdk/lib/x86_64/libOpenCL.so to /usr/lib64/libOpenCL.so. Do the same from /opt/amd-app-sdk/lib/x86_64/libOpenCL.so.1 to /usr/lib64/libOpenCL.so.1
Please continue in the pending bug. For eselect-opencl, open a separate bug. *** This bug has been marked as a duplicate of bug 257626 ***
(In reply to comment #22) > Created attachment 272449 [details] > Ebuild version bump to AMD APP SDK 2.4 > > I've uploaded a rough and dirty ebuild that supports AMD APP SDK 2.4. It's > just a modified version of the ebuild for ATI Stream SDK 2.3 from the pentoo > overlay. > > The ebuild has been renamed to "dev-util/amd-app-sdk-bin" and the installation > folder now defaults to /opt/amd-app-sdk. It installs perfectly on my 64-bit > system, but I believe it needs to be modified to support 32-bit platforms. > Also, for some reason it failed to create symlinks for the libOpenCL.so file. > If you get errors about OpenCL programs unable to find libOpenCL.so, simply > create a symlink from /opt/amd-app-sdk/lib/x86_64/libOpenCL.so to > /usr/lib64/libOpenCL.so. Do the same from > /opt/amd-app-sdk/lib/x86_64/libOpenCL.so.1 to /usr/lib64/libOpenCL.so.1 Why is it only has KEYWORDS="amd64"
Can someone please make a ebuild for 32-bit platforms. Thank you.
I wrote an ebuild for 2.3 adapted from an ArchLinux's PKGBUILD, then bumped it to 2.4. I think its a lot uglier then the attachment 272449 [details]. Also, see https://forums.gentoo.org/viewtopic-p-6772852.html and https://bugs.gentoo.org/show_bug.cgi?id=372847 for an eselect module.
