colbyn
commented
4 years ago Ahh, first I don't think the LLVM_CONFIG_PATH path is a necessity (it's from a dependency called rust-bindgen), but perhaps I'm wrong (I've built this before without setting it).
Anyway in all honesty, this is a very strange error. Can you give me the full output instead of a summary? That may give me better context.
Also what is your OS?
But from what I gather, this definitely looks like an FFmpeg build issue. I wonder, this crate is supposed to be self contained, but perhaps this is still linking against some system dependency somehow (maybe the ffmpeg config flag --disable-autodetect isn't enough), and/or perhaps it's due to some untested linux distribution.
Oh, I noticed you had the --release flag set. Does this work in dev/debug mode? I.e. cargo run --example h264_video_dec, instead of cargo run --release --example h264_video_dec.
Another possibility I think, on my Mac I've built this using clang, and on Linux I'm pretty sure I've always used llvm/clang (e.g. here is a Dockerfile that builds this crate as a dependency). Maybe this is a bug in some codepath trigged by GCC. Do you have clang installed and available on your path?
Update: also just to be safe, when testing the GCC idea, rm -rf your build output dir, usually called target.
piaoger
Hi, I got build error: unknown type name '*' when trying to build this crate:
LLVM_CONFIG_PATH=/usr/local/opt/llvm/bin/llvm-config cargo run --release --example h264_video_dec
--- stderr /w/imager-io/ffmpeg-dev-rs/target/release/build/ffmpeg-dev-81b52e898a9ea16c/out/FFmpeg-FFmpeg-2722fc2/libavutil/buffer_internal.h:44:5: error: unknown type name 'atomic_uint' /w/imager-io/ffmpeg-dev-rs/target/release/build/ffmpeg-dev-81b52e898a9ea16c/out/FFmpeg-FFmpeg-2722fc2/libavutil/buffer_internal.h:89:5: error: unknown type name 'atomic_uint' /w/imager-io/ffmpeg-dev-rs/target/release/build/ffmpeg-dev-81b52e898a9ea16c/out/FFmpeg-FFmpeg-2722fc2/libavcodec/error_resilience.h:64:5: error: unknown type name 'atomic_int' ...