Volker Schlecht <openbsd-po...@schlecht.dev> writes: > Here's an update to the latest release of bazel 6.x > I didn't manage to build XLA (https://openxla.org) yet, but at least it > doesn't > complain about the bazel version anymore :-)
Thanks for working on the update. I played with an update to the 7.x series but it's not easy. > > ok? I built your patch on arm64 for practice. I noticed that we don't seem to have the right runtime dependencies: % bazel build WARNING: Invoking Bazel in batch mode since it is not invoked from within a workspace (below a directory having a WORKSPACE file). Extracting Bazel installation... ERROR: Couldn't find java at '/usr/local/jdk-17/bin/java'. Could you fix this? With jdk%17 installed there's another weirdness. It wasn't there with bazel-6.3.2 and is likely to be arm64-only: % bazel build WARNING: Invoking Bazel in batch mode since it is not invoked from within a workspace (below a directory having a WORKSPACE file). OpenJDK 64-Bit Server VM warning: Options -Xverify:none and -noverify were deprecated in JDK 13 and will likely be removed in a future release. java:/tmp/bazel-jni.1850915075858462602/libunix_jni.so: undefined symbol 'blake3_hash_many_neon' ERROR: The 'build' command is only supported from within a workspace (below a directory having a WORKSPACE file). See documentation at https://bazel.build/concepts/build-ref#workspace Do you have the cycles/hardware to pursue this? Thanks Greg
