search

dbarnett / vim-plugin-metadata

Parse and analyze your vim plugins, from Rust & Python!
MIT License
1 stars 0 forks source link

Figure out why py-bindings fail to build on target=aarch64|armv7|s390x|ppc64le runner=ubuntu-latest #8

Open dbarnett opened 2 months ago

dbarnett commented 2 months ago

Some dimensions of the build matrix are failing to build the python bindings on ubuntu-latest for certain targets (aarch64|armv7|s390x|ppc64le).

Example failed run: https://github.com/dbarnett/rust-vim-plugin-metadata/actions/runs/10641094800/job/29501798954

The failures have

error: failed to run custom build command for `tree-sitter-vim v0.4.0`

in the output. They also have a bunch of warnings like

warning: tree-sitter-vim@0.4.0: src/tree_sitter/parser.h:183:5: error: 'for' loop initial declarations are only allowed in C99 mode

but it's not clear if those are actually related to the failure.

dbarnett commented 2 months ago

For reference, if the C99 warning is relevant, I can find other reports of it related to tree-sitter (example: https://github.com/nvim-treesitter/nvim-treesitter/issues/2383).

dbarnett commented 2 months ago

FWIW, I tried passing -vv to cargo via maturin and still didn't seem to get any meaningful error message: https://github.com/dbarnett/rust-vim-plugin-metadata/actions/runs/10647989880/job/29516562651

Context: -vv is supposed to show build script output according to https://doc.rust-lang.org/cargo/reference/build-scripts.html#outputs-of-the-build-script:

If you would like to see the output directly in your terminal, invoke Cargo as “very verbose” with the -vv flag.

...and maturin --help

-vv: Show debug logging and use cargo build -vv