Building on T2SDE fails
Can anyone run cingg build on Arch or something new? https://github.com/rxrbln/t2sde/issues/278#issuecomment-3824472834 I suspect new gcc started to be more strict so our libzmpeg folder fails now ...
On 1/30/26 5:41 PM, Andrew Randrianasulu via Cin wrote:
Can anyone run cingg build on Arch or something new?
Apparently Andrey's current rpm on opensusetw (that I use) used the current gcc 15.2.1 objdump -s --section .comment /usr/bin/cin /usr/bin/cin: file format elf64-x86-64 Contents of section .comment: 0000 4743433a 20285355 5345204c 696e7578 GCC: (SUSE Linux 0010 29203135 2e322e31 20323032 35313030 ) 15.2.1 2025100 0020 3600 6
https://github.com/rxrbln/t2sde/issues/278#issuecomment-3824472834
I suspect new gcc started to be more strict so our libzmpeg folder fails now ...
_______________________________________________ Cin mailing list [email protected] To unsubscribe send an email [email protected]
My Arch has gcc 15.2.1. The build from git was successful without errors. Do I need to do any specific tests?
On Fri, Jan 30, 2026 at 10:24 PM Andrea paz via Cin <[email protected]> wrote:
My Arch has gcc 15.2.1. The build from git was successful without errors. Do I need to do any specific tests?
Thanks. I will try to replicate this error, just for now T2 does not build on my Slackware, but hopefully should build on itself in qemu VM ...
_______________________________________________ Cin mailing list -- [email protected] To unsubscribe send an email to [email protected]
сб, 31 янв. 2026 г., 04:41 Andrew Randrianasulu <[email protected]>:
On Fri, Jan 30, 2026 at 10:24 PM Andrea paz via Cin <[email protected]> wrote:
My Arch has gcc 15.2.1. The build from git was successful without errors. Do I need to do any specific tests?
Thanks.
I will try to replicate this error, just for now T2 does not build on my Slackware, but hopefully should build on itself in qemu VM ...
I think we traced failure back to wrong shell used for our configure (mksh vs bash). Dear Phyllis, I hope everything is more than less ok on your end? Can we make new release so T2 picks our fix for non-thirdparty install? While at it you can try to enable Vulkan for new appimage so Terje will have chance to test it?
_______________________________________________ Cin mailing list -- [email protected] To unsubscribe send an email to [email protected]
Andrew, did I miss something? - I checked into GIT, the 0026-Attempt-at-fixing-prefix-system-install-with-libzmpe.patch, with the changes to configure.ac and Makefile.am. - Was there another specific patch for this? Quote="I think we traced failure back to wrong shell used for our configure (mksh vs bash)." If so, I missed it. - I will gladly make a new test AppImage with enabling Vulkan, but I thought that it had to be built on a computer that had specific hardware capabilities. Am I wrong? or can I just add "--enable-vulkan" to the "configure" line? Same question about ONEVPL? On Sat, Jan 31, 2026 at 9:45 PM Andrew Randrianasulu < [email protected]> wrote:
сб, 31 янв. 2026 г., 04:41 Andrew Randrianasulu <[email protected]>:
On Fri, Jan 30, 2026 at 10:24 PM Andrea paz via Cin <[email protected]> wrote:
My Arch has gcc 15.2.1. The build from git was successful without
errors.
Do I need to do any specific tests?
Thanks.
I will try to replicate this error, just for now T2 does not build on my Slackware, but hopefully should build on itself in qemu VM ...
I think we traced failure back to wrong shell used for our configure (mksh vs bash).
Dear Phyllis, I hope everything is more than less ok on your end?
Can we make new release so T2 picks our fix for non-thirdparty install? While at it you can try to enable Vulkan for new appimage so Terje will have chance to test it?
_______________________________________________ Cin mailing list -- [email protected] To unsubscribe send an email to [email protected]
пн, 2 февр. 2026 г., 01:59 Phyllis Smith <[email protected]>:
Andrew, did I miss something? - I checked into GIT, the 0026-Attempt-at-fixing-prefix-system-install-with-libzmpe.patch, with the changes to configure.ac and Makefile.am. - Was there another specific patch for this? Quote="I think we traced failure back to wrong shell used for our configure (mksh vs bash)." If so, I missed it.
No, it should be enough, just T2's recipe fetch *release* tarball, not git commit, so install still fails there, even if we fixed that in git. - I will gladly make a new test AppImage with enabling Vulkan, but I
thought that it had to be built on a computer that had specific hardware capabilities. Am I wrong? or can I just add "--enable-vulkan" to the "configure" line? Same question about ONEVPL?
Well, good question! While building cinelerra-10 on T2SDE I noticed ffmpeg 5.1 for example outright fail to build with new vulkan headers (no configure check tight enough, I guess). Depending on what kind of vulkan sdk your build OS for new appimage have it may or may not work with different distros ... I think only way to test is try! You also can try to enable openvpl, and see if it get pulled into appimage so at least it starts on system without OneVPL installed? Mismatches still possible, with all those moving parts ...
On Sat, Jan 31, 2026 at 9:45 PM Andrew Randrianasulu < [email protected]> wrote:
сб, 31 янв. 2026 г., 04:41 Andrew Randrianasulu <[email protected]
:
On Fri, Jan 30, 2026 at 10:24 PM Andrea paz via Cin <[email protected]> wrote:
My Arch has gcc 15.2.1. The build from git was successful without
errors.
Do I need to do any specific tests?
Thanks.
I will try to replicate this error, just for now T2 does not build on my Slackware, but hopefully should build on itself in qemu VM ...
I think we traced failure back to wrong shell used for our configure (mksh vs bash).
Dear Phyllis, I hope everything is more than less ok on your end?
Can we make new release so T2 picks our fix for non-thirdparty install? While at it you can try to enable Vulkan for new appimage so Terje will have chance to test it?
_______________________________________________ Cin mailing list -- [email protected] To unsubscribe send an email to [email protected]
On 2/2/26 12:38 AM, Andrew Randrianasulu wrote:
пн, 2 февр. 2026 г., 01:59 Phyllis Smith <[email protected]>:
Andrew, did I miss something? - I checked into GIT, the 0026-Attempt-at-fixing-prefix-system-install-with-libzmpe.patch, with the changes to configure.ac <http://configure.ac> and Makefile.am. - Was there another specific patch for this? Quote="I think we traced failure back to wrong shell used for our configure (mksh vs bash)." If so, I missed it.
No, it should be enough, just T2's recipe fetch *release* tarball, not git commit, so install still fails there, even if we fixed that in git.
- I will gladly make a new test AppImage with enabling Vulkan, but I thought that it had to be built on a computer that had specific hardware capabilities. Am I wrong? or can I just add "--enable-vulkan" to the "configure" line? Same question about ONEVPL?
Well, good question!
While building cinelerra-10 on T2SDE I noticed ffmpeg 5.1 for example outright fail to build with new vulkan headers (no configure check tight enough, I guess).
Depending on what kind of vulkan sdk your build OS for new appimage have it may or may not work with different distros ... I think only way to test is try!
You also can try to enable openvpl, and see if it get pulled into appimage so at least it starts on system without OneVPL installed? Mismatches still possible, with all those moving parts ...
The build requirement package names may vary between Linux distributions. Seemingly also vulkan hwaccel, like vpl, vaapi and vdpau open-source API's already enabled, can be enabled without having the actual hardware gpu on the build machine. This was tested previously for vpl (qsv) https://lists.cinelerra-gg.org/archives/list/[email protected]/mess... To create and test presets it is at least easier to have a package build installed.
On Sat, Jan 31, 2026 at 9:45 PM Andrew Randrianasulu <[email protected]> wrote:
сб, 31 янв. 2026 г., 04:41 Andrew Randrianasulu <[email protected]>:
On Fri, Jan 30, 2026 at 10:24 PM Andrea paz via Cin <[email protected]> wrote: > > My Arch has gcc 15.2.1. The build from git was successful without errors. > Do I need to do any specific tests?
Thanks.
I will try to replicate this error, just for now T2 does not build on my Slackware, but hopefully should build on itself in qemu VM ...
I think we traced failure back to wrong shell used for our configure (mksh vs bash).
Dear Phyllis, I hope everything is more than less ok on your end?
Can we make new release so T2 picks our fix for non-thirdparty install? While at it you can try to enable Vulkan for new appimage so Terje will have chance to test it?
> > _______________________________________________ > Cin mailing list -- [email protected] > To unsubscribe send an email to [email protected]
On 2/2/26 3:37 AM, Terje J. Hanssen wrote:
On 2/2/26 12:38 AM, Andrew Randrianasulu wrote:
пн, 2 февр. 2026 г., 01:59 Phyllis Smith <[email protected]>:
Andrew, did I miss something? - I checked into GIT, the 0026-Attempt-at-fixing-prefix-system-install-with-libzmpe.patch, with the changes to configure.ac <http://configure.ac> and Makefile.am. - Was there another specific patch for this? Quote="I think we traced failure back to wrong shell used for our configure (mksh vs bash)." If so, I missed it.
No, it should be enough, just T2's recipe fetch *release* tarball, not git commit, so install still fails there, even if we fixed that in git.
- I will gladly make a new test AppImage with enabling Vulkan, but I thought that it had to be built on a computer that had specific hardware capabilities. Am I wrong? or can I just add "--enable-vulkan" to the "configure" line? Same question about ONEVPL?
Well, good question!
While building cinelerra-10 on T2SDE I noticed ffmpeg 5.1 for example outright fail to build with new vulkan headers (no configure check tight enough, I guess).
Depending on what kind of vulkan sdk your build OS for new appimage have it may or may not work with different distros ... I think only way to test is try!
You also can try to enable openvpl, and see if it get pulled into appimage so at least it starts on system without OneVPL installed? Mismatches still possible, with all those moving parts ...
The build requirement package names may vary between Linux distributions.
Seemingly also vulkan hwaccel, like vpl, vaapi and vdpau open-source API's already enabled, can be enabled without having the actual hardware gpu on the build machine.
This was tested previously for vpl (qsv) https://lists.cinelerra-gg.org/archives/list/[email protected]/mess...
To create and test presets it is at least easier to have a package build installed.
To clarify My url above, was with my own build AppImage in Dec 2024. I re-tested now on two Intel machines with: Alder Lake/DG2 and Coffee Lake/UHD 620 (ultrabook) with * cinelerra-5.1-20260120.susetw.x86_64.rpm installed: QSV transcoding works on both * CinGG-20251231-x86_64.AppImage: cant find codec h264_qsv So obviously VPL for QSV hwaccel was then enabled in the rpm build, not in the AppImage ?
On Sat, Jan 31, 2026 at 9:45 PM Andrew Randrianasulu <[email protected]> wrote:
сб, 31 янв. 2026 г., 04:41 Andrew Randrianasulu <[email protected]>:
On Fri, Jan 30, 2026 at 10:24 PM Andrea paz via Cin <[email protected]> wrote: > > My Arch has gcc 15.2.1. The build from git was successful without errors. > Do I need to do any specific tests?
Thanks.
I will try to replicate this error, just for now T2 does not build on my Slackware, but hopefully should build on itself in qemu VM ...
I think we traced failure back to wrong shell used for our configure (mksh vs bash).
Dear Phyllis, I hope everything is more than less ok on your end?
Can we make new release so T2 picks our fix for non-thirdparty install? While at it you can try to enable Vulkan for new appimage so Terje will have chance to test it?
> > _______________________________________________ > Cin mailing list -- [email protected] > To unsubscribe send an email to [email protected]
Andrew, added "--with vulkan --with-onvpl" to the configure line. This is what I get in the log:
checking for vaGetDisplayDRM in -lva-drm... yes checking for MFXCreateSession in -lvpl... no checking for vkQueueSubmit in -lvulkan... no *configure: error: requires vulkan support.* make: *** No targets specified and no makefile found. Stop.
AND *configure: error: requires onevpl support.*
On Sun, Feb 1, 2026 at 4:39 PM Andrew Randrianasulu <[email protected]> wrote:
пн, 2 февр. 2026 г., 01:59 Phyllis Smith <[email protected]>:
Andrew, did I miss something? - I checked into GIT, the 0026-Attempt-at-fixing-prefix-system-install-with-libzmpe.patch, with the changes to configure.ac and Makefile.am. - Was there another specific patch for this? Quote="I think we traced failure back to wrong shell used for our configure (mksh vs bash)." If so, I missed it.
No, it should be enough, just T2's recipe fetch *release* tarball, not git commit, so install still fails there, even if we fixed that in git.
- I will gladly make a new test AppImage with enabling Vulkan, but I
thought that it had to be built on a computer that had specific hardware capabilities. Am I wrong? or can I just add "--enable-vulkan" to the "configure" line? Same question about ONEVPL?
Well, good question!
While building cinelerra-10 on T2SDE I noticed ffmpeg 5.1 for example outright fail to build with new vulkan headers (no configure check tight enough, I guess).
Depending on what kind of vulkan sdk your build OS for new appimage have it may or may not work with different distros ... I think only way to test is try!
You also can try to enable openvpl, and see if it get pulled into appimage so at least it starts on system without OneVPL installed? Mismatches still possible, with all those moving parts ...
On Sat, Jan 31, 2026 at 9:45 PM Andrew Randrianasulu < [email protected]> wrote:
сб, 31 янв. 2026 г., 04:41 Andrew Randrianasulu <[email protected]
:
On Fri, Jan 30, 2026 at 10:24 PM Andrea paz via Cin <[email protected]> wrote:
My Arch has gcc 15.2.1. The build from git was successful without
errors.
Do I need to do any specific tests?
Thanks.
I will try to replicate this error, just for now T2 does not build on my Slackware, but hopefully should build on itself in qemu VM ...
I think we traced failure back to wrong shell used for our configure (mksh vs bash).
Dear Phyllis, I hope everything is more than less ok on your end?
Can we make new release so T2 picks our fix for non-thirdparty install? While at it you can try to enable Vulkan for new appimage so Terje will have chance to test it?
_______________________________________________ Cin mailing list -- [email protected] To unsubscribe send an email to [email protected]
пн, 2 февр. 2026 г., 22:59 Phyllis Smith <[email protected]>:
Andrew, added "--with vulkan --with-onvpl" to the configure line. This is what I get in the log:
checking for vaGetDisplayDRM in -lva-drm... yes checking for MFXCreateSession in -lvpl... no checking for vkQueueSubmit in -lvulkan... no *configure: error: requires vulkan support.* make: *** No targets specified and no makefile found. Stop.
AND *configure: error: requires onevpl support.*
you need to install onevpl-devel package, and vulkan-sdk ..... (on your build machine)
On Sun, Feb 1, 2026 at 4:39 PM Andrew Randrianasulu < [email protected]> wrote:
пн, 2 февр. 2026 г., 01:59 Phyllis Smith <[email protected]>:
Andrew, did I miss something? - I checked into GIT, the 0026-Attempt-at-fixing-prefix-system-install-with-libzmpe.patch, with the changes to configure.ac and Makefile.am. - Was there another specific patch for this? Quote="I think we traced failure back to wrong shell used for our configure (mksh vs bash)." If so, I missed it.
No, it should be enough, just T2's recipe fetch *release* tarball, not git commit, so install still fails there, even if we fixed that in git.
- I will gladly make a new test AppImage with enabling Vulkan, but I
thought that it had to be built on a computer that had specific hardware capabilities. Am I wrong? or can I just add "--enable-vulkan" to the "configure" line? Same question about ONEVPL?
Well, good question!
While building cinelerra-10 on T2SDE I noticed ffmpeg 5.1 for example outright fail to build with new vulkan headers (no configure check tight enough, I guess).
Depending on what kind of vulkan sdk your build OS for new appimage have it may or may not work with different distros ... I think only way to test is try!
You also can try to enable openvpl, and see if it get pulled into appimage so at least it starts on system without OneVPL installed? Mismatches still possible, with all those moving parts ...
On Sat, Jan 31, 2026 at 9:45 PM Andrew Randrianasulu < [email protected]> wrote:
сб, 31 янв. 2026 г., 04:41 Andrew Randrianasulu < [email protected]>:
On Fri, Jan 30, 2026 at 10:24 PM Andrea paz via Cin <[email protected]> wrote:
My Arch has gcc 15.2.1. The build from git was successful without
errors.
Do I need to do any specific tests?
Thanks.
I will try to replicate this error, just for now T2 does not build on my Slackware, but hopefully should build on itself in qemu VM ...
I think we traced failure back to wrong shell used for our configure (mksh vs bash).
Dear Phyllis, I hope everything is more than less ok on your end?
Can we make new release so T2 picks our fix for non-thirdparty install? While at it you can try to enable Vulkan for new appimage so Terje will have chance to test it?
_______________________________________________ Cin mailing list -- [email protected] To unsubscribe send an email to [email protected]
FYI, I did get --with-vulkan to compile but not --with-onevpl. Still working on and got errors when making AppImage so am not done yet.
root@fedora:~# dnf install libvpl-2.16.0-1.fc42 Updating and loading repositories: Repositories loaded. Package "libvpl-1:2.16.0-1.fc42.x86_64" is already installed.
Nothing to do. root@fedora:~# dnf install vulkan Updating and loading repositories: Repositories loaded. Package "vulkan-loader-1.4.313.0-1.fc42.x86_64" is already installed.
Nothing to do.
Problem --with-onevpl: configure: error: requires onevpl support. make: *** No targets specified and no makefile found. Stop.
On Mon, Feb 2, 2026 at 2:13 PM Andrew Randrianasulu <[email protected]> wrote:
пн, 2 февр. 2026 г., 22:59 Phyllis Smith <[email protected]>:
Andrew, added "--with vulkan --with-onvpl" to the configure line. This is what I get in the log:
checking for vaGetDisplayDRM in -lva-drm... yes checking for MFXCreateSession in -lvpl... no checking for vkQueueSubmit in -lvulkan... no *configure: error: requires vulkan support.* make: *** No targets specified and no makefile found. Stop.
AND *configure: error: requires onevpl support.*
you need to install onevpl-devel package, and vulkan-sdk ..... (on your build machine)
On Sun, Feb 1, 2026 at 4:39 PM Andrew Randrianasulu < [email protected]> wrote:
пн, 2 февр. 2026 г., 01:59 Phyllis Smith <[email protected]>:
Andrew, did I miss something? - I checked into GIT, the 0026-Attempt-at-fixing-prefix-system-install-with-libzmpe.patch, with the changes to configure.ac and Makefile.am. - Was there another specific patch for this? Quote="I think we traced failure back to wrong shell used for our configure (mksh vs bash)." If so, I missed it.
No, it should be enough, just T2's recipe fetch *release* tarball, not git commit, so install still fails there, even if we fixed that in git.
- I will gladly make a new test AppImage with enabling Vulkan, but I
thought that it had to be built on a computer that had specific hardware capabilities. Am I wrong? or can I just add "--enable-vulkan" to the "configure" line? Same question about ONEVPL?
Well, good question!
While building cinelerra-10 on T2SDE I noticed ffmpeg 5.1 for example outright fail to build with new vulkan headers (no configure check tight enough, I guess).
Depending on what kind of vulkan sdk your build OS for new appimage have it may or may not work with different distros ... I think only way to test is try!
You also can try to enable openvpl, and see if it get pulled into appimage so at least it starts on system without OneVPL installed? Mismatches still possible, with all those moving parts ...
On Sat, Jan 31, 2026 at 9:45 PM Andrew Randrianasulu < [email protected]> wrote:
сб, 31 янв. 2026 г., 04:41 Andrew Randrianasulu < [email protected]>:
On Fri, Jan 30, 2026 at 10:24 PM Andrea paz via Cin <[email protected]> wrote: > > My Arch has gcc 15.2.1. The build from git was successful without errors. > Do I need to do any specific tests?
Thanks.
I will try to replicate this error, just for now T2 does not build on my Slackware, but hopefully should build on itself in qemu VM ...
I think we traced failure back to wrong shell used for our configure (mksh vs bash).
Dear Phyllis, I hope everything is more than less ok on your end?
Can we make new release so T2 picks our fix for non-thirdparty install? While at it you can try to enable Vulkan for new appimage so Terje will have chance to test it?
> > _______________________________________________ > Cin mailing list -- [email protected] > To unsubscribe send an email to [email protected]
чт, 5 февр. 2026 г., 03:51 Phyllis Smith <[email protected]>:
FYI, I did get --with-vulkan to compile but not --with-onevpl. Still working on and got errors when making AppImage so am not done yet.
root@fedora:~# dnf install libvpl-2.16.0-1.fc42 Updating and loading repositories: Repositories loaded. Package "libvpl-1:2.16.0-1.fc42.x86_64" is already installed.
Try libvpl-devel ? https://packages.fedoraproject.org/pkgs/libvpl/libvpl-devel/
Nothing to do. root@fedora:~# dnf install vulkan Updating and loading repositories: Repositories loaded. Package "vulkan-loader-1.4.313.0-1.fc42.x86_64" is already installed.
Just in case you can add https://packages.fedoraproject.org/pkgs/vulkan-headers/vulkan-headers/ ? But may be they were already pulled in ... if you say --enable-vulkan works. Nothing to do.
Problem --with-onevpl: configure: error: requires onevpl support. make: *** No targets specified and no makefile found. Stop.
On Mon, Feb 2, 2026 at 2:13 PM Andrew Randrianasulu < [email protected]> wrote:
пн, 2 февр. 2026 г., 22:59 Phyllis Smith <[email protected]>:
Andrew, added "--with vulkan --with-onvpl" to the configure line. This is what I get in the log:
checking for vaGetDisplayDRM in -lva-drm... yes checking for MFXCreateSession in -lvpl... no checking for vkQueueSubmit in -lvulkan... no *configure: error: requires vulkan support.* make: *** No targets specified and no makefile found. Stop.
AND *configure: error: requires onevpl support.*
you need to install onevpl-devel package, and vulkan-sdk ..... (on your build machine)
On Sun, Feb 1, 2026 at 4:39 PM Andrew Randrianasulu < [email protected]> wrote:
пн, 2 февр. 2026 г., 01:59 Phyllis Smith <[email protected]>:
Andrew, did I miss something? - I checked into GIT, the 0026-Attempt-at-fixing-prefix-system-install-with-libzmpe.patch, with the changes to configure.ac and Makefile.am. - Was there another specific patch for this? Quote="I think we traced failure back to wrong shell used for our configure (mksh vs bash)." If so, I missed it.
No, it should be enough, just T2's recipe fetch *release* tarball, not git commit, so install still fails there, even if we fixed that in git.
- I will gladly make a new test AppImage with enabling Vulkan, but I
thought that it had to be built on a computer that had specific hardware capabilities. Am I wrong? or can I just add "--enable-vulkan" to the "configure" line? Same question about ONEVPL?
Well, good question!
While building cinelerra-10 on T2SDE I noticed ffmpeg 5.1 for example outright fail to build with new vulkan headers (no configure check tight enough, I guess).
Depending on what kind of vulkan sdk your build OS for new appimage have it may or may not work with different distros ... I think only way to test is try!
You also can try to enable openvpl, and see if it get pulled into appimage so at least it starts on system without OneVPL installed? Mismatches still possible, with all those moving parts ...
On Sat, Jan 31, 2026 at 9:45 PM Andrew Randrianasulu < [email protected]> wrote:
сб, 31 янв. 2026 г., 04:41 Andrew Randrianasulu < [email protected]>:
> On Fri, Jan 30, 2026 at 10:24 PM Andrea paz via Cin > <[email protected]> wrote: > > > > My Arch has gcc 15.2.1. The build from git was successful without > errors. > > Do I need to do any specific tests? > > Thanks. > > I will try to replicate this error, just for now T2 does not build on > my Slackware, but hopefully should build on itself in qemu VM ... >
I think we traced failure back to wrong shell used for our configure (mksh vs bash).
Dear Phyllis, I hope everything is more than less ok on your end?
Can we make new release so T2 picks our fix for non-thirdparty install? While at it you can try to enable Vulkan for new appimage so Terje will have chance to test it?
> > > > > > > _______________________________________________ > > Cin mailing list -- [email protected] > > To unsubscribe send an email to [email protected] >
On 2/5/26 5:28 AM, Andrew Randrianasulu wrote:
чт, 5 февр. 2026 г., 03:51 Phyllis Smith <[email protected]>:
FYI, I did get --with-vulkan to compile but not --with-onevpl. Still working on and got errors when making AppImage so am not done yet.
root@fedora:~# dnf install libvpl-2.16.0-1.fc42 Updating and loading repositories: Repositories loaded. Package "libvpl-1:2.16.0-1.fc42.x86_64" is already installed.
Try libvpl-devel ?
https://packages.fedoraproject.org/pkgs/libvpl/libvpl-devel/
Unhappily I have not my previous build environment intact. While there seemingly are some differences in packaging between Tumbleweed and Fedora, libva-devel (va-api) may also be required as a backend for vpl, and possibly also onevpl-intel-gpu-devel (?)
Nothing to do. root@fedora:~# dnf install vulkan Updating and loading repositories: Repositories loaded. Package "vulkan-loader-1.4.313.0-1.fc42.x86_64" is already installed.
Just in case you can add
https://packages.fedoraproject.org/pkgs/vulkan-headers/vulkan-headers/
?
But may be they were already pulled in ... if you say --enable-vulkan works.
Nothing to do.
Problem --with-onevpl: configure: error: requires onevpl support. make: *** No targets specified and no makefile found. Stop.
On Mon, Feb 2, 2026 at 2:13 PM Andrew Randrianasulu <[email protected]> wrote:
пн, 2 февр. 2026 г., 22:59 Phyllis Smith <[email protected]>:
Andrew, added "--with vulkan --with-onvpl" to the configure line. This is what I get in the log:
checking for vaGetDisplayDRM in -lva-drm... yes checking for MFXCreateSession in -lvpl... no checking for vkQueueSubmit in -lvulkan... no *configure: error: requires vulkan support.* make: *** No targets specified and no makefile found. Stop.
AND *configure: error: requires onevpl support.*
you need to install onevpl-devel package, and vulkan-sdk ..... (on your build machine)
On Sun, Feb 1, 2026 at 4:39 PM Andrew Randrianasulu <[email protected]> wrote:
пн, 2 февр. 2026 г., 01:59 Phyllis Smith <[email protected]>:
Andrew, did I miss something? - I checked into GIT, the 0026-Attempt-at-fixing-prefix-system-install-with-libzmpe.patch, with the changes to configure.ac <http://configure.ac> and Makefile.am. - Was there another specific patch for this? Quote="I think we traced failure back to wrong shell used for our configure (mksh vs bash)." If so, I missed it.
No, it should be enough, just T2's recipe fetch *release* tarball, not git commit, so install still fails there, even if we fixed that in git.
- I will gladly make a new test AppImage with enabling Vulkan, but I thought that it had to be built on a computer that had specific hardware capabilities. Am I wrong? or can I just add "--enable-vulkan" to the "configure" line? Same question about ONEVPL?
Well, good question!
While building cinelerra-10 on T2SDE I noticed ffmpeg 5.1 for example outright fail to build with new vulkan headers (no configure check tight enough, I guess).
Depending on what kind of vulkan sdk your build OS for new appimage have it may or may not work with different distros ... I think only way to test is try!
You also can try to enable openvpl, and see if it get pulled into appimage so at least it starts on system without OneVPL installed? Mismatches still possible, with all those moving parts ...
On Sat, Jan 31, 2026 at 9:45 PM Andrew Randrianasulu <[email protected]> wrote:
сб, 31 янв. 2026 г., 04:41 Andrew Randrianasulu <[email protected]>:
On Fri, Jan 30, 2026 at 10:24 PM Andrea paz via Cin <[email protected]> wrote: > > My Arch has gcc 15.2.1. The build from git was successful without errors. > Do I need to do any specific tests?
Thanks.
I will try to replicate this error, just for now T2 does not build on my Slackware, but hopefully should build on itself in qemu VM ...
I think we traced failure back to wrong shell used for our configure (mksh vs bash).
Dear Phyllis, I hope everything is more than less ok on your end?
Can we make new release so T2 picks our fix for non-thirdparty install? While at it you can try to enable Vulkan for new appimage so Terje will have chance to test it?
> > _______________________________________________ > Cin mailing list -- [email protected] > To unsubscribe send an email to [email protected]
As time permits, try this AppImage and please let me know if Vulkan and Onevpl capabilities are there. I cobbled together the binary on the CinGG website Download page in the testing subdirectory: vulkan_onevpl-x86_64.AppImage. It was built on kernel version 6.18.5-100, libc version 2.41. On Wed, Feb 4, 2026 at 9:29 PM Andrew Randrianasulu <[email protected]> wrote:
чт, 5 февр. 2026 г., 03:51 Phyllis Smith <[email protected]>:
FYI, I did get --with-vulkan to compile but not --with-onevpl. Still working on and got errors when making AppImage so am not done yet.
root@fedora:~# dnf install libvpl-2.16.0-1.fc42 Updating and loading repositories: Repositories loaded. Package "libvpl-1:2.16.0-1.fc42.x86_64" is already installed.
Try libvpl-devel ?
https://packages.fedoraproject.org/pkgs/libvpl/libvpl-devel/
Nothing to do. root@fedora:~# dnf install vulkan Updating and loading repositories: Repositories loaded. Package "vulkan-loader-1.4.313.0-1.fc42.x86_64" is already installed.
Just in case you can add
https://packages.fedoraproject.org/pkgs/vulkan-headers/vulkan-headers/
?
But may be they were already pulled in ... if you say --enable-vulkan works.
Nothing to do.
Problem --with-onevpl: configure: error: requires onevpl support. make: *** No targets specified and no makefile found. Stop.
On Mon, Feb 2, 2026 at 2:13 PM Andrew Randrianasulu < [email protected]> wrote:
пн, 2 февр. 2026 г., 22:59 Phyllis Smith <[email protected]>:
Andrew, added "--with vulkan --with-onvpl" to the configure line. This is what I get in the log:
checking for vaGetDisplayDRM in -lva-drm... yes checking for MFXCreateSession in -lvpl... no checking for vkQueueSubmit in -lvulkan... no *configure: error: requires vulkan support.* make: *** No targets specified and no makefile found. Stop.
AND *configure: error: requires onevpl support.*
you need to install onevpl-devel package, and vulkan-sdk ..... (on your build machine)
On Sun, Feb 1, 2026 at 4:39 PM Andrew Randrianasulu < [email protected]> wrote:
пн, 2 февр. 2026 г., 01:59 Phyllis Smith <[email protected]>:
Andrew, did I miss something? - I checked into GIT, the 0026-Attempt-at-fixing-prefix-system-install-with-libzmpe.patch, with the changes to configure.ac and Makefile.am. - Was there another specific patch for this? Quote="I think we traced failure back to wrong shell used for our configure (mksh vs bash)." If so, I missed it.
No, it should be enough, just T2's recipe fetch *release* tarball, not git commit, so install still fails there, even if we fixed that in git.
- I will gladly make a new test AppImage with enabling Vulkan, but I
thought that it had to be built on a computer that had specific hardware capabilities. Am I wrong? or can I just add "--enable-vulkan" to the "configure" line? Same question about ONEVPL?
Well, good question!
While building cinelerra-10 on T2SDE I noticed ffmpeg 5.1 for example outright fail to build with new vulkan headers (no configure check tight enough, I guess).
Depending on what kind of vulkan sdk your build OS for new appimage have it may or may not work with different distros ... I think only way to test is try!
You also can try to enable openvpl, and see if it get pulled into appimage so at least it starts on system without OneVPL installed? Mismatches still possible, with all those moving parts ...
On Sat, Jan 31, 2026 at 9:45 PM Andrew Randrianasulu < [email protected]> wrote:
> > > сб, 31 янв. 2026 г., 04:41 Andrew Randrianasulu < > [email protected]>: > >> On Fri, Jan 30, 2026 at 10:24 PM Andrea paz via Cin >> <[email protected]> wrote: >> > >> > My Arch has gcc 15.2.1. The build from git was successful without >> errors. >> > Do I need to do any specific tests? >> >> Thanks. >> >> I will try to replicate this error, just for now T2 does not build >> on >> my Slackware, but hopefully should build on itself in qemu VM ... >> > > > I think we traced failure back to wrong shell used for our configure > (mksh vs bash). > > Dear Phyllis, I hope everything is more than less ok on your end? > > Can we make new release so T2 picks our fix for non-thirdparty > install? While at it you can try to enable Vulkan for new appimage so Terje > will have chance to test it? > > >> >> >> >> > >> > _______________________________________________ >> > Cin mailing list -- [email protected] >> > To unsubscribe send an email to [email protected] >> >
On 2/5/26 8:52 PM, Phyllis Smith wrote:
As time permits, try this AppImage and please let me know if Vulkan and Onevpl capabilities are there. I cobbled together the binary on the CinGG website Download page in the testing subdirectory: vulkan_onevpl-x86_64.AppImage. It was built on kernel version 6.18.5-100, libc version 2.41.
Tested the vulkan_onevpl-x86_64.AppImage on two Intel machines , Coffee Lake / UHD 620 iGPU and Alder Lake / DG2 dGPU, both with current Slowroll. Unhappily the actual rendering methods failed: VPL: cant find codec h264_qsv or hevc_qsv. Vulkan: compression was not available. (tried to adapt and edit tje h264_vaapi preset to cin_hw_dev=vulkan which didn't work). Tested also my own appimage (20241120) where still VPL works on Leap15.6
On Wed, Feb 4, 2026 at 9:29 PM Andrew Randrianasulu <[email protected]> wrote:
чт, 5 февр. 2026 г., 03:51 Phyllis Smith <[email protected]>:
FYI, I did get --with-vulkan to compile but not --with-onevpl. Still working on and got errors when making AppImage so am not done yet.
root@fedora:~# dnf install libvpl-2.16.0-1.fc42 Updating and loading repositories: Repositories loaded. Package "libvpl-1:2.16.0-1.fc42.x86_64" is already installed.
Try libvpl-devel ?
https://packages.fedoraproject.org/pkgs/libvpl/libvpl-devel/
Nothing to do. root@fedora:~# dnf install vulkan Updating and loading repositories: Repositories loaded. Package "vulkan-loader-1.4.313.0-1.fc42.x86_64" is already installed.
Just in case you can add
https://packages.fedoraproject.org/pkgs/vulkan-headers/vulkan-headers/
?
But may be they were already pulled in ... if you say --enable-vulkan works.
Nothing to do.
Problem --with-onevpl: configure: error: requires onevpl support. make: *** No targets specified and no makefile found. Stop.
On Mon, Feb 2, 2026 at 2:13 PM Andrew Randrianasulu <[email protected]> wrote:
пн, 2 февр. 2026 г., 22:59 Phyllis Smith <[email protected]>:
Andrew, added "--with vulkan --with-onvpl" to the configure line. This is what I get in the log:
checking for vaGetDisplayDRM in -lva-drm... yes checking for MFXCreateSession in -lvpl... no checking for vkQueueSubmit in -lvulkan... no *configure: error: requires vulkan support.* make: *** No targets specified and no makefile found. Stop.
AND *configure: error: requires onevpl support.*
you need to install onevpl-devel package, and vulkan-sdk ..... (on your build machine)
On Sun, Feb 1, 2026 at 4:39 PM Andrew Randrianasulu <[email protected]> wrote:
пн, 2 февр. 2026 г., 01:59 Phyllis Smith <[email protected]>:
Andrew, did I miss something? - I checked into GIT, the 0026-Attempt-at-fixing-prefix-system-install-with-libzmpe.patch, with the changes to configure.ac <http://configure.ac> and Makefile.am. - Was there another specific patch for this? Quote="I think we traced failure back to wrong shell used for our configure (mksh vs bash)." If so, I missed it.
No, it should be enough, just T2's recipe fetch *release* tarball, not git commit, so install still fails there, even if we fixed that in git.
- I will gladly make a new test AppImage with enabling Vulkan, but I thought that it had to be built on a computer that had specific hardware capabilities. Am I wrong? or can I just add "--enable-vulkan" to the "configure" line? Same question about ONEVPL?
Well, good question!
While building cinelerra-10 on T2SDE I noticed ffmpeg 5.1 for example outright fail to build with new vulkan headers (no configure check tight enough, I guess).
Depending on what kind of vulkan sdk your build OS for new appimage have it may or may not work with different distros ... I think only way to test is try!
You also can try to enable openvpl, and see if it get pulled into appimage so at least it starts on system without OneVPL installed? Mismatches still possible, with all those moving parts ...
On Sat, Jan 31, 2026 at 9:45 PM Andrew Randrianasulu <[email protected]> wrote:
сб, 31 янв. 2026 г., 04:41 Andrew Randrianasulu <[email protected]>:
On Fri, Jan 30, 2026 at 10:24 PM Andrea paz via Cin <[email protected]> wrote: > > My Arch has gcc 15.2.1. The build from git was successful without errors. > Do I need to do any specific tests?
Thanks.
I will try to replicate this error, just for now T2 does not build on my Slackware, but hopefully should build on itself in qemu VM ...
I think we traced failure back to wrong shell used for our configure (mksh vs bash).
Dear Phyllis, I hope everything is more than less ok on your end?
Can we make new release so T2 picks our fix for non-thirdparty install? While at it you can try to enable Vulkan for new appimage so Terje will have chance to test it?
> > _______________________________________________ > Cin mailing list -- [email protected] > To unsubscribe send an email to [email protected]
пт, 6 февр. 2026 г., 02:14 Terje J. Hanssen <[email protected]>:
On 2/5/26 8:52 PM, Phyllis Smith wrote:
As time permits, try this AppImage and please let me know if Vulkan and Onevpl capabilities are there. I cobbled together the binary on the CinGG website Download page in the testing subdirectory: vulkan_onevpl-x86_64.AppImage. It was built on kernel version 6.18.5-100, libc version 2.41.
Tested the vulkan_onevpl-x86_64.AppImage on two Intel machines , Coffee Lake / UHD 620 iGPU and Alder Lake / DG2 dGPU, both with current Slowroll. Unhappily the actual rendering methods failed:
VPL: cant find codec h264_qsv or hevc_qsv.
Sad. :( I wonder if it was just path mismatch like with vaapi, or something else? Can you unpack appimage, delete onevpl lib, and let it link to system's onevpl loader, like with vaapi before? Vulkan: compression was not available. (tried to adapt and edit tje
h264_vaapi preset to cin_hw_dev=vulkan which didn't work).
you need to change actual codec name, too.
ffmpeg on termux says something like ffmpeg -encoders | grep vulkan V....D av1_vulkan AV1 (Vulkan) (codec av1) V....D ffv1_vulkan FFmpeg video codec #1 (Vulkan) (codec ffv1) V....D h264_vulkan H.264/AVC (Vulkan) (codec h264) V....D hevc_vulkan H.265/HEVC (Vulkan) (codec hevc)
Tested also my own appimage (20241120) where still VPL works on Leap15.6
On Wed, Feb 4, 2026 at 9:29 PM Andrew Randrianasulu < [email protected]> wrote:
чт, 5 февр. 2026 г., 03:51 Phyllis Smith <[email protected]>:
FYI, I did get --with-vulkan to compile but not --with-onevpl. Still working on and got errors when making AppImage so am not done yet.
root@fedora:~# dnf install libvpl-2.16.0-1.fc42 Updating and loading repositories: Repositories loaded. Package "libvpl-1:2.16.0-1.fc42.x86_64" is already installed.
Try libvpl-devel ?
https://packages.fedoraproject.org/pkgs/libvpl/libvpl-devel/
Nothing to do. root@fedora:~# dnf install vulkan Updating and loading repositories: Repositories loaded. Package "vulkan-loader-1.4.313.0-1.fc42.x86_64" is already installed.
Just in case you can add
https://packages.fedoraproject.org/pkgs/vulkan-headers/vulkan-headers/
?
But may be they were already pulled in ... if you say --enable-vulkan works.
Nothing to do.
Problem --with-onevpl: configure: error: requires onevpl support. make: *** No targets specified and no makefile found. Stop.
On Mon, Feb 2, 2026 at 2:13 PM Andrew Randrianasulu < [email protected]> wrote:
пн, 2 февр. 2026 г., 22:59 Phyllis Smith <[email protected]>:
Andrew, added "--with vulkan --with-onvpl" to the configure line. This is what I get in the log:
checking for vaGetDisplayDRM in -lva-drm... yes checking for MFXCreateSession in -lvpl... no checking for vkQueueSubmit in -lvulkan... no *configure: error: requires vulkan support.* make: *** No targets specified and no makefile found. Stop.
AND *configure: error: requires onevpl support.*
you need to install onevpl-devel package, and vulkan-sdk ..... (on your build machine)
On Sun, Feb 1, 2026 at 4:39 PM Andrew Randrianasulu < [email protected]> wrote:
пн, 2 февр. 2026 г., 01:59 Phyllis Smith <[email protected]>:
> Andrew, did I miss something? > - I checked into GIT, the > 0026-Attempt-at-fixing-prefix-system-install-with-libzmpe.patch, with the > changes to configure.ac and Makefile.am. > - Was there another specific patch for this? Quote="I think we > traced failure back to wrong shell used for our configure (mksh vs bash)." > If so, I missed it. >
No, it should be enough, just T2's recipe fetch *release* tarball, not git commit, so install still fails there, even if we fixed that in git.
- I will gladly make a new test AppImage with enabling Vulkan, but I > thought that it had to be built on a computer that had specific hardware > capabilities. Am I wrong? or can I just add "--enable-vulkan" to the > "configure" line? Same question about ONEVPL? >
Well, good question!
While building cinelerra-10 on T2SDE I noticed ffmpeg 5.1 for example outright fail to build with new vulkan headers (no configure check tight enough, I guess).
Depending on what kind of vulkan sdk your build OS for new appimage have it may or may not work with different distros ... I think only way to test is try!
You also can try to enable openvpl, and see if it get pulled into appimage so at least it starts on system without OneVPL installed? Mismatches still possible, with all those moving parts ...
> On Sat, Jan 31, 2026 at 9:45 PM Andrew Randrianasulu < > [email protected]> wrote: > >> >> >> сб, 31 янв. 2026 г., 04:41 Andrew Randrianasulu < >> [email protected]>: >> >>> On Fri, Jan 30, 2026 at 10:24 PM Andrea paz via Cin >>> <[email protected]> wrote: >>> > >>> > My Arch has gcc 15.2.1. The build from git was successful >>> without errors. >>> > Do I need to do any specific tests? >>> >>> Thanks. >>> >>> I will try to replicate this error, just for now T2 does not build >>> on >>> my Slackware, but hopefully should build on itself in qemu VM ... >>> >> >> >> I think we traced failure back to wrong shell used for our >> configure (mksh vs bash). >> >> Dear Phyllis, I hope everything is more than less ok on your end? >> >> Can we make new release so T2 picks our fix for non-thirdparty >> install? While at it you can try to enable Vulkan for new appimage so Terje >> will have chance to test it? >> >> >>> >>> >>> >>> > >>> > _______________________________________________ >>> > Cin mailing list -- [email protected] >>> > To unsubscribe send an email to [email protected] >>> >>
пн, 2 февр. 2026 г., 02:38 Andrew Randrianasulu <[email protected]>:
пн, 2 февр. 2026 г., 01:59 Phyllis Smith <[email protected]>:
Andrew, did I miss something? - I checked into GIT, the 0026-Attempt-at-fixing-prefix-system-install-with-libzmpe.patch, with the changes to configure.ac and Makefile.am. - Was there another specific patch for this? Quote="I think we traced failure back to wrong shell used for our configure (mksh vs bash)." If so, I missed it.
No, it should be enough, just T2's recipe fetch *release* tarball, not git commit, so install still fails there, even if we fixed that in git.
Should be building! At least installed size and num. of files look reasonably now: https://t2linux.com/packages/cinelerra-gg
- I will gladly make a new test AppImage with enabling Vulkan, but I
thought that it had to be built on a computer that had specific hardware capabilities. Am I wrong? or can I just add "--enable-vulkan" to the "configure" line? Same question about ONEVPL?
Well, good question!
While building cinelerra-10 on T2SDE I noticed ffmpeg 5.1 for example outright fail to build with new vulkan headers (no configure check tight enough, I guess).
Depending on what kind of vulkan sdk your build OS for new appimage have it may or may not work with different distros ... I think only way to test is try!
You also can try to enable openvpl, and see if it get pulled into appimage so at least it starts on system without OneVPL installed? Mismatches still possible, with all those moving parts ...
On Sat, Jan 31, 2026 at 9:45 PM Andrew Randrianasulu < [email protected]> wrote:
сб, 31 янв. 2026 г., 04:41 Andrew Randrianasulu <[email protected]
:
On Fri, Jan 30, 2026 at 10:24 PM Andrea paz via Cin <[email protected]> wrote:
My Arch has gcc 15.2.1. The build from git was successful without
errors.
Do I need to do any specific tests?
Thanks.
I will try to replicate this error, just for now T2 does not build on my Slackware, but hopefully should build on itself in qemu VM ...
I think we traced failure back to wrong shell used for our configure (mksh vs bash).
Dear Phyllis, I hope everything is more than less ok on your end?
Can we make new release so T2 picks our fix for non-thirdparty install? While at it you can try to enable Vulkan for new appimage so Terje will have chance to test it?
_______________________________________________ Cin mailing list -- [email protected] To unsubscribe send an email to [email protected]
participants (4)
-
Andrea paz -
Andrew Randrianasulu -
Phyllis Smith -
Terje J. Hanssen