-
-
Notifications
You must be signed in to change notification settings - Fork 610
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
zellij can't build on Linux ppc64 #3378
Comments
note, this seems to be a similar failure to #3180 |
I don’t like external binaries dependencies since this kind of problem exist because of them. |
Thanks - that commit fixes this build issue!
…On Sun, May 26, 2024 at 02:31:28AM -0700, Zykino wrote:
I don’t like external binaries dependencies since this kind of problem exist because of them.
See my [feature/compile](https://github.com/Zykino/zellij/compare/feature/compile) fork’s branch (specifically [this commit](Zykino@6f37c91) for an example on passing arguments to protoc.
--
Reply to this email directly or view it on GitHub:
#3378 (comment)
You are receiving this because you authored the thread.
Message ID: ***@***.***>
|
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
zellij doesn't build on linux ppc64le (ubuntu 22.04 LTS)
cargo xtask build
fails with:Running `target/debug/xtask build` thread 'main' panicked at xtask/src/build.rs:85:22: called `Result::unwrap()` on an `Err` value: Custom { kind: Other, error: "protoc failed: action.proto: This file contains proto3 optional fields, but --experimental_allow_proto3_optional was not set.\n" }
Trying to 'skip ahead' and
cargo build
returns some failures in corosensei, which is also unsupported on ppc64le it seems (Amanieu/corosensei#18).What is it about zellij (and dependencies) that is so coupled to the underlying hardware/ABI? I'm not sure if the bug here is that another architecture needs support, or if zellij shouldn't need to be aware of the underlying arch?
The text was updated successfully, but these errors were encountered: