On 11/2/26 18:51, Andrew Randrianasulu wrote:
пн, 2 нояб. 2026 г., 18:04 Terje J. Hanssen via Cin <cin@lists.cinelerra-gg.org>:
Hi team,
I have successfully compiled Cinelerra-GG from source on openSUSE Leap 16.1, using a configuration set to single-use without third-party and dynamically linked.
However, I ran into a persistent startup crash related to writing plugin indexes:
MWindow::init_plugins: can't create plugin index: /home/terje/.bcast5/Cinelerra_plugins
Interestingly, the exact same source build runs and behaves seemingly fine on openSUSE Tumbleweed-Slowroll, but on Leap 16.1 the locally built binary in ./bin/cin encounters permission or I/O errors when attempting to write to the configuration directory during initialization unless heavily overridden.
Be sure there was no errors during "make install" phase?
I think there already was report on list about make install error, may be new "make" changed something?
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