Terje, a little murky but for the latest where all ffmpeg plugins give errors, (1) I think it does not know where the system FFmpeg headers are: hence the inclusion you have on Slowroll of "CFLAGS=-I/usr/include/ffmpeg". (2) Below you have " /configure --single-user --without-third-party --with-system-ffmpeg" so maybe this is just a typo here BUT: --single-user should be --with-single-user --without-third-party should be --without-thirdparty and --with-system-ffmpeg is not recognized If you have time, it would be very helpful to get the build log included by adding to the end of the configure line: 2>&1 | tee log On Tue, Nov 3, 2026 at 6:25 AM Terje J. Hanssen via Cin < cin@lists.cinelerra-gg.org> wrote:
To clarify: I haven't run make install on Leap 16.1 yet; I am running the binary directly from ./bin/cin inside the source repository.
For reference, here is how I configured the build for the current test on Leap 16.1 and Slowroll:
cd ~/cingg-repo/cinelerra-5.1 ./autogen.sh ./configure --single-user --without-third-party --with-system-ffmpeg make -j$(nproc)
Looking back at our email thread from 2024 (when building on Slowroll)
https://lists.cinelerra-gg.org/archives/list/cin@lists.cinelerra-gg.org/mess...
There we used a slightly different set of flags and explicit header paths:
CFLAGS=-I/usr/include/ffmpeg ./configure --with-single-user --disable-static-build --without-thirdparty --without-libdpx
Comparing the two setups, the key differences are:
- Using --with-single-user instead of --single-user. - Adding --disable-static-build and --without-libdpx. - Passing CFLAGS=-I/usr/include/ffmpeg to explicitly point the compiler to system FFmpeg headers.
I am going to run a fresh build using the 2024 flags now to see if linking against system FFmpeg 8.1.3 on Leap 16.1 behaves differently during the startup plugin probe.
A couple of question regarding the build process:
Is running make install (with --with-single-user) necessary or beneficial when building with system FFmpeg on Leap 16.1?
While it seeminglys works on Slowroll now, could running directly from ./bin/cin without an install step affect how plugins or configuration paths are located, or cause issues during the plugin index generation stage?
Terje
Troubleshooting steps taken so far: - The .bcast5 configuration directory has been deleted and recreated multiple times, but Cingg still crashes during startup. - Three different CinGG AppImages have also been tested on the same system without startup issues.
Has anyone experienced similar path or permission issues when running a fresh source build alongside pre-existing environment configs?
Terje _______________________________________________ Cin mailing list -- cin@lists.cinelerra-gg.org To unsubscribe send an email to cin-leave@lists.cinelerra-gg.org
_______________________________________________ Cin mailing list -- cin@lists.cinelerra-gg.org To unsubscribe send an email to cin-leave@lists.cinelerra-gg.org