-
Notifications
You must be signed in to change notification settings - Fork 5
Open
Labels
enhancementNew feature or requestNew feature or requeststatus: triageIndicates an issue has been assigned for investigation.Indicates an issue has been assigned for investigation.
Description
Dear developers,
I'm struggling getting a self-consistent set of wheels for v0.7.1 with ROCm 7.0 that, when put together into a wheelhouse can be installed alongside. Currently I get jax and jaxlib from ROCm/jax (branch rocm-jaxlib-v0.7.1) and plugin and pjrt from here (branch rocm-jax-v0.7.1)since this is how to do it at the moment as far as I understood. However there are several issues:
- to strip 'dev0-selfbuilt' from the resulting jaxlib-wheel to make it findable as a proper dependency of jax, one has to add
--bazel_options="--action_env=ML_WHEEL_TYPE=release"to the build since the environment variable JAX_RELEASE or JAXLIB_RELEASE are currently ignored for jaxlib apparently. - despite specifying '--rocm_version' correctly to '7' which is necessary since otherwise the plugin cannot be found at runtime, during installation however the dependency resolution from jax is still looking for plugins labeled with 'rocm60'. This is when specifying
jax[rocm]for pip. Specific extrasrocm60orrocm7are not available it seems.
For experimenting around personally this is all not an issue but in order to provide jax 0.7.1 with rocm on our systems in an automated fashion a standard installation workflow would be highly desirable.
ROCm Version
ROCM 7.0.1
Reactions are currently unavailable
Metadata
Metadata
Assignees
Labels
enhancementNew feature or requestNew feature or requeststatus: triageIndicates an issue has been assigned for investigation.Indicates an issue has been assigned for investigation.
Type
Projects
Status
Todo