-
Notifications
You must be signed in to change notification settings - Fork 214
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Can't build on linux/aarch64 #112
Comments
I also tried to build it in docker on M1 Mac and the build failed with the following error:
|
I should mention @pgrivachev is the author of zetasql-npm, a fantastically useful FFI binding for zetasql. The existence of that library has me incredibly excited at the potential of Zetasql's build process targeting not only x86_64, and arm, but also WASM so that Zetasql could be executed client-side and in-browser. Just planting that seed 🌱 . |
@riordan you mentioned
Was that on a M1 mac? zetasql/java/com/google/zetasql/JniChannelProvider.java Lines 47 to 49 in fa3c85e
It would be awesome to get aarch64 support |
@leoch20 if you are just trying to use ZetaSQL on an M1 mac, you need to make sure you're using the right x86_64 JVM (and you'll need Rosetta installed for that) |
Thanks @laughedelic that did it for me |
Hello @pgrivachev! Currently I am trying to build
|
Hey @billstark! I don't remember such issue. I can only suggest using an environment that works for me:
|
I'm one of those horrible M1 Mac users screwing up the buildchain for every open source projects. So let me begin by thanking you for abstracting macos/darwin builds so they're architecture independent. It would be great if we could do the same for Linux.
Things work fine in MacOS. It gets interesting when we involve Docker.
Containers can be built for multiple architectures (e.g. x86_64 & aarch64). Docker can run either architecture, though it prefers the native architecture of the host machine. So if an ARM/aarch64 mac tries to build zetasql inside a (local default) aarch64 container, it'll fail, as linux-specific builds are tied to:
"@bazel_tools//src/conditions:linux_x86_64"
While mac/darwin builds are configured to use:
"@bazel_tools//src/conditions:darwin"
or"@platforms//os:macos"
It would be nice if linux builds could be configured independent of cpu architecture, or at least could select for linux_aarch64.
The text was updated successfully, but these errors were encountered: