Package Details: aocl-gcc 5.2.0-1

Git Clone URL: https://aur.archlinux.org/aocl.git (read-only, click to copy)
Package Base: aocl
Description: AMD Optimizing CPU Libraries
Upstream URL: https://www.amd.com/en/developer/aocl.html
Licenses: custom
Submitter: disc-kuraudo
Maintainer: disc-kuraudo (jclds139, ninetailedtori)
Last Packager: ninetailedtori
Votes: 4
Popularity: 0.44
First Submitted: 2019-10-04 14:02 (UTC)
Last Updated: 2026-01-04 21:06 (UTC)

Latest Comments

1 2 3 Next › Last »

ninetailedtori commented on 2026-01-10 20:14 (UTC)

@Rainbowu sha256sum parse should not be broken right now, it works flawlessly on our side. Can you paste the output of the sha256 checksum command in your term?

Rainbowu commented on 2025-12-24 02:24 (UTC) (edited on 2025-12-24 07:34 (UTC) by Rainbowu)

sha256sum parse is broken, been parsed to .deb file sha256sum. you can change regex to grep --perl-regexp '\w{64}(?=\<\/span\>)' --only-matching to find aocl-aocc, and sed -n '3 p' to find aocl-gcc, but remember use regex with web page never stable

ninetailedtori commented on 2025-11-27 19:49 (UTC) (edited on 2025-12-23 20:58 (UTC) by ninetailedtori)

Please see https://github.com/ninetailedtori/Improved-PKGBUILDs/tree/aocl for improved pkgbuild, including automatically pulling tarball as well as upstream signatures.

Changes have been pushed, on the 29th, to include all upstream automatic pulling and sig checks. Many thanks to our downloaders and those who've voted for us!

ninetailedtori commented on 2025-11-27 18:39 (UTC)

@disc-kuraudo do you mind if I modify all the aocl packages to have pkgbuild pull the tarballs automatically? It's a little...unneat to have it managed as manual download currently.

eggplant commented on 2025-10-30 08:13 (UTC)

@disc-kuraudo hi, the file modulefile is failing sha256sums check:

==> Making package: aocl 5.1.0-1 (Thu 30 Oct 2025 01:12:13 AM PDT)
==> Retrieving sources...
  -> Found aocl-linux-aocc-5.1.0.tar.gz
  -> Found aocl-linux-gcc-5.1.0.tar.gz
  -> Found aocl-aocc.install
  -> Found aocl-gcc.install
  -> Found modulefile
==> Validating source files with sha256sums...
    aocl-linux-aocc-5.1.0.tar.gz ... Passed
    aocl-linux-gcc-5.1.0.tar.gz ... Passed
    aocl-aocc.install ... Passed
    aocl-gcc.install ... Passed
    modulefile ... FAILED
==> ERROR: One or more files did not pass the validity check!
error: failed to download sources for 'aocl-5.1.0-1 (aocl-aocc)': 
error: packages failed to build: aocl-5.1.0-1 (aocl-aocc)

Meron35 commented on 2025-10-21 09:11 (UTC)

This is failing to build due to the sha256sums for modulefile not matching.

disc-kuraudo commented on 2024-03-24 11:00 (UTC)

I've put you as a co-maintainer, feel free to apply fixes that you see fit.

jclds139 commented on 2024-03-24 01:35 (UTC) (edited on 2024-03-24 01:35 (UTC) by jclds139)

I've made another PKGBUILD patch, this time to clear out the remaining ${pkgdir} references that were lingering in FFTW's pkgconfig and CMake files. With that, building and linking against the provided libfftw3* should be less error prone now.

Once again, I've put it on GitHub for merging if you desire: https://github.com/jclds139/aur-aocl

jclds139 commented on 2023-10-18 19:32 (UTC)

I've made an updated PKGBUILD which includes instructions for enabling AOCL with /etc/ld.so.conf.d as well as patching libflame.so to add the missing dependency on libblis-mt.so. This allows libflame.so to be used as liblapack.so globally.

I've posted it on GitHub so it can be merged if you're amenable. https://github.com/jclds139/aur-aocl

disc-kuraudo commented on 2023-02-14 19:34 (UTC) (edited on 2023-02-14 19:36 (UTC) by disc-kuraudo)

AMD sneakily updated this again under the same release name w/o notice.

If you have the old tarballs laying around in the directory of the PKGBUILD, move/delete them and re-download manually...

1 2 3 Next › Last »