Building with an OpenCL BLAS
Nobody has claimed this yet.
Assessment
- Difficulty
- 5/5
- Estimated time
- Over a week
- Newbie friendliness
- 25/100
- Issue type
- Feature
- Clarity
- Needs clarification
- Activity status
- Stale
- Domain
- build-system
Research direction
Start by reading the referenced blas-feedstock and the staged-recipes pull requests 3190 and 3196, then review the linked BLAS/Numpy discussion. The work is done when libgpuarray-feedstock has an agreed, documented strategy for handling builds with clBLAS and CLBlast.
Written by the indexing model from the issue text.
Description
Am working on adding two OpenCL BLASes to conda-forge. In particular am adding clBLAS and CLBlast. IIUC libgpuarray can support one or the other. So am opening this issue to discuss how we handle building libgpuarray. With CPU BLAS support we have a selection package, which determines the CPU BLAS used by all packages. Perhaps a similar strategy makes sense here.
xref: https://github.com/conda-forge/staged-recipes/pull/3190
xref: https://github.com/conda-forge/staged-recipes/pull/3196
ref: https://github.com/conda-forge/blas-feedstock
ref: https://conda-forge.hackpad.com/BLAS-Numpy-Friends-86De62hoNdT
- Dominant language
- Batchfile
- Stars
- 0
- Forks
- 7
- PR merge metrics
- No merged PRs in 30d
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Similar issues
-
Difficulty 1/5 Under an hour Newbie friendliness 90/100
-
bug
Difficulty 2/5 1-3 hours Newbie friendliness 75/100
typelevel/sbt-typelevel#929 ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 70/100
openSUSE/python-rpm-macros#219 ·
-
HMR stops working Open
Difficulty 2/5 1-3 hours Newbie friendliness 75/100
-
Difficulty 1/5 Under an hour Newbie friendliness 90/100
Qiskit/mcp-servers#221 ·