Something I couldn't pull off in #192, perhaps someone can help.
The issue is that jaxlib calls another bazel build for the vendored xla, which then does not pick up the correct @com_google_absl anymore. That's despite xla having logic for processing TF_SYSTEM_LIBS, but it seems bazel isolation doesn't pass the variable down. I tried various things like
Something I couldn't pull off in #192, perhaps someone can help.
The issue is that jaxlib calls another bazel build for the vendored xla, which then does not pick up the correct
@com_google_absl
anymore. That's despite xla having logic for processingTF_SYSTEM_LIBS
, but it seems bazel isolation doesn't pass the variable down. I tried various things likeand
but to no success.