add loongarch64 support for BUILD#2987
Conversation
|
Thanks for adding. Happy to land this but we are currently failing builds. Debugging: we already have bazel_dep(name = "platforms", version = "1.0.0") in MODULE.bazel which should be new enough, and the bazel version is 9.0.2. USE_BAZEL_VERSION is not set, and there is no It's probably the WORKSPACE. In that file, please replace the old platforms with this: |
f1de7cc to
aa4800e
Compare
|
Thanks for updating. Still seeing a build error. The cause might be that maybe() skips the archive if the module is already present, which it is: Bazel already has an older platforms built in. Please try changing the WORKSPACE block to remove the |
aa4800e to
21b10c4
Compare
ok |
|
Thanks for also trying that. I've misunderstood the problem. It is not that we are using a too old platforms module - loongarch is not yet 'supported' (added to Bazel) even in v1.0 of its platforms. (Out of curiosity, what prompted you to add @platforms//cpu:loongarch64 - are you using a locally patched version of Bazel?) To move forward, I believe we can add the following to BUILD: Then use :loongarch64 in the select() calls instead of @platforms//cpu:loongarch64. |
yes, I am using a locally patched version of Bazel from https://github.com/Loongson-Cloud-Community/bazel/tree/7.5.0 |
|
I see, thanks. We do not have that on the Github actions CI, hence we could only merge after it's added to bazel platforms (sounds like there is some movement on that), or we use the local config_setting as proposed above. |
Thank you for your review. We are trying to promote the merging of bazel and hope more people will contribute to it |
Thank you for your review. platforms already supports loongarch64, |
|
Congrats, glad to see that land :) |
No description provided.