Hi. Over at python-pillow, we've recently started experiencing an error when building the rav1e dependency - https://github.com/python-pillow/Pillow/actions/runs/13997677419/job/39247134664
To try and clarify things, I've created a minimal reproduction in https://github.com/radarhere/rav1e_demo, using a modified form of https://github.com/AOMediaCodec/libavif/?tab=readme-ov-file#build-using-installed-dependencies,
git clone https://github.com/AOMediaCodec/libavif.git
cmake -S libavif -B libavif/build -DAVIF_CODEC_RAV1E=LOCAL -DAVIF_LIBYUV=LOCAL
cmake --build libavif/build
You can see the result at https://github.com/radarhere/rav1e_demo/actions/runs/14006661508/job/39221374554
The error is not the same each time, but in both runs I've linked to
CUSTOMBUILD : error : failed to run custom build command for `num-traits v0.2.17` [D:\a\rav1e_demo\rav1e_demo\libavif\build\rav1e.vcxproj]
Caused by:
process didn't exit successfully: `D:\a\rav1e_demo\rav1e_demo\libavif\build\_deps\rav1e-src\target\release\build\num-traits-edebc03261ed90b9\build-script-build` (exit code: 101)
--- stderr
thread 'main' panicked at C:\Users\runneradmin\.cargo\registry\src\index.crates.io-1949cf8c6b5b557f\autocfg-1.1.0\src\lib.rs:128:20:
called `Result::unwrap()` on an `Err` value: Error { kind: Other("could not execute rustc") }
note: run with `RUST_BACKTRACE=1` environment variable to display a backtrace
CUSTOMBUILD : warning : build failed, waiting for other jobs to finish... [D:\a\rav1e_demo\rav1e_demo\libavif\build\rav1e.vcxproj]
CUSTOMBUILD : error : the 'rustc.exe' binary, normally provided by the 'rustc' component, is not applicable to the 'stable-x86_64-pc-windows-msvc' toolchain [D:\a\rav1e_demo\rav1e_demo\libavif\build\rav1e.vcxproj]
I don't imagine this is a direct problem with libavif, but if you have any thoughts, or if you're able to figure out where it should be reported to, that would be helpful.
For some more debugging info, apparently this only started with version 2.323.0 of the runner image, and installing dtolnay/rust-toolchain fixes it - but I have to imagine that this is still an error somewhere along the line. Even in the worst case scenario where dtolnay/rust-toolchain is a sudden new dependency (I consider this unlikely), I expect you'd want to know so you can document that.
Thanks for your time.
Hi. Over at python-pillow, we've recently started experiencing an error when building the rav1e dependency - https://github.com/python-pillow/Pillow/actions/runs/13997677419/job/39247134664
To try and clarify things, I've created a minimal reproduction in https://github.com/radarhere/rav1e_demo, using a modified form of https://github.com/AOMediaCodec/libavif/?tab=readme-ov-file#build-using-installed-dependencies,
You can see the result at https://github.com/radarhere/rav1e_demo/actions/runs/14006661508/job/39221374554
The error is not the same each time, but in both runs I've linked to
I don't imagine this is a direct problem with libavif, but if you have any thoughts, or if you're able to figure out where it should be reported to, that would be helpful.
For some more debugging info, apparently this only started with version 2.323.0 of the runner image, and installing dtolnay/rust-toolchain fixes it - but I have to imagine that this is still an error somewhere along the line. Even in the worst case scenario where dtolnay/rust-toolchain is a sudden new dependency (I consider this unlikely), I expect you'd want to know so you can document that.
Thanks for your time.