Package Details: amdapp-sdk-nocatalyst 3.0-23

Git Clone URL: https://aur.archlinux.org/amdapp-sdk.git (read-only, click to copy)
Package Base: amdapp-sdk
Description: AMD Accelerated Parallel Processing (APP) SDK, 3.0 with OpenCL 2.0 support. Libs and ICD for non-catalyst users.
Upstream URL: https://developer.amd.com/amd-accelerated-parallel-processing-app-sdk/
Licenses: custom
Groups: amdapp
Conflicts: catalyst-utils
Submitter: Vi0L0
Maintainer: rigred
Last Packager: k8ie
Votes: 84
Popularity: 0.000447
First Submitted: 2013-02-11 21:03 (UTC)
Last Updated: 2019-08-16 21:33 (UTC)

Latest Comments

« First ‹ Previous 1 .. 13 14 15 16 17 18 19 20 21 Next › Last »

vojtechkral commented on 2010-08-18 11:42 (UTC)

Updated to 2.2. Now with OpenCL 1.1 support :) Hope everything works, feel free to test...

vojtechkral commented on 2010-08-17 13:42 (UTC)

The package is now updated. Sorry for the delay, I was abroad and in a deep wilderness with no internet :) And thanks Vi0L0 for your help!

<deleted-account> commented on 2010-07-27 01:28 (UTC)

Thanks a lot ViOLO, with the first PKGBUILD works ok now :D

Vi0L0 commented on 2010-07-26 02:15 (UTC)

@Cory: thats because theres simply no llc file, and PKGBUILD of this pkg need to be updated. Both PKGBUILDs mentioned below got it - http://aur.pastebin.com/57nYwgMr and http://ix.io/Zm

<deleted-account> commented on 2010-07-25 02:44 (UTC)

What i'm doing wrong? ./FindNumDevices Supported CAL Runtime Version: 1.3.185 Found CAL Runtime Version: 1.4.696 Use -? for help CAL initialized. Finding out number of devices :- Device Count = 1 CAL shutdown successful. Press enter to exit... ./NBody sh: /opt/amdstream/bin/x86/llc: No such file or directory BUILD LOG ************************************************ Error: Compilation from LLVMIR binary to IL text failed! ************************************************ Error: clBuildProgram failed. Error code : CL_BUILD_PROGRAM_FAILURE What's the problem?

vojtechkral commented on 2010-07-06 15:30 (UTC)

Yes I know about those env vars I just didn't find any reason why set them up... The SDK seemed to work just as fine. I look into this and will possibly fix, if I have free time...