Re: ROCm Some elements for January
- To: debian-ai@lists.debian.org
- Subject: Re: ROCm Some elements for January
- From: Maxime Chambonnet <maxzor@maxzor.eu>
- Date: Sat, 1 Jan 2022 17:52:24 +0100
- Message-id: <[🔎] 4dce4662-144d-1cf8-ea8e-dc7fc5aff621@maxzor.eu>
- In-reply-to: <e9754d2a-24e3-ca8d-e2e2-612968a5926d@maxzor.eu>
- References: <f1bbc6e4-b5a5-7e6a-0eca-1390f33f4469@maxzor.eu> <20667cd1-bed0-a96e-6d8b-54fc3eda5dbf@maxzor.eu> <1a3375c1-e68b-cd23-8e66-4b39184d309a@slerp.xyz> <e9754d2a-24e3-ca8d-e2e2-612968a5926d@maxzor.eu>
# I. To package-or-not-to-package AMD-LLVM
I feel like not being very far from un-bundling with a clear cut, but
not sure.
Happy new year, good news - quick update: it (quite) works!
See [1] for details.
Not sure if we can package ROCm without the AMD LLVM fork yet, would enjoy
your feedback, especially Cordell, since you know the stack, and the
potential
implications, much better.
[1]
https://github.com/ROCm-Developer-Tools/HIP/issues/2449#issuecomment-1003582954
Reply to: