ffmpeg.git test compile fail
ffmpeg shallow git copy commit 890b8da1ce27fd365eaffefc7efcbadae9f01f2a our patches 2 and 8 fail, but this is not really my point yet .... ffmpeg.C:313:42: error: 'avcodec_close' was not declared in this scope; did you mean 'avio_close'? ffmpeg.C:476:33: error: 'avcodec_close' was not declared in this scope; did you mean 'avio_close'? ffmpeg.C:1307:37: error: 'AVFrame' {aka 'struct AVFrame'} has no member named 'interlaced_frame' ffmpeg.C:1309:37: error: 'AVFrame' {aka 'struct AVFrame'} has no member named 'interlaced_frame' ffmpeg.C:1309:66: error: 'AVFrame' {aka 'struct AVFrame'} has no member named 'top_field_first' ffmpeg.C:1311:37: error: 'AVFrame' {aka 'struct AVFrame'} has no member named 'interlaced_frame' ffmpeg.C:1311:67: error: 'AVFrame' {aka 'struct AVFrame'} has no member named 'top_field_first' ffmpeg.C:1340:36: error: 'AVFrame' {aka 'struct AVFrame'} has no member named 'key_frame' ffmpeg.C:1512:24: error: 'AVFrame' {aka 'struct AVFrame'} has no member named 'interlaced_frame' ffmpeg.C:1513:24: error: 'AVFrame' {aka 'struct AVFrame'} has no member named 'top_field_first' ffmpeg.C:3847:29: error: 'av_stream_get_side_data' was not declared in this scope; did you mean 'av_frame_get_side_data'? mplayer switched for now to branch 7.1 until it get updates. i see in doc/APIchanges 2023-05-04 - 0fc9c1f6828 - lavu 58.7.100 - frame.h Deprecate AVFrame.interlaced_frame, AVFrame.top_field_first, and AVFrame.key_frame. Add AV_FRAME_FLAG_INTERLACED, AV_FRAME_FLAG_TOP_FIELD_FIRST, and AV_FRAME_FLAG_KEY flags as replacement. but not sure how to use them yet.
I think exact conditionals should be more like 61.0.100 but for single test it worked ... for some reason our x264 failed to encode (segfault) on i686 with AVX ? but x265 worked .... this is not yet for commiting, but more like for testing with ffmpeg git. cc: ffmpeg-devel in case they have better suggestions on fixing our code for upcoming ffmpeg. cingg git URL: git://git.cinelerra-gg.org/goodguy/cinelerra run ./autogen.sh configure: ./configure --with-git-ffmpeg=https://git.ffmpeg.org/ffmpeg.git --with-single-user rm thirdparty/src/ffmpeg.git.patch2 rm thirdparty/src/ffmpeg.git.patch8 make make install run from build directory bin/cin (with DISPLAY variable set) ср, 9 апр. 2025 г., 14:49 Andrew Randrianasulu <[email protected]>:
ffmpeg shallow git copy
commit 890b8da1ce27fd365eaffefc7efcbadae9f01f2a
our patches 2 and 8 fail, but this is not really my point yet ....
ffmpeg.C:313:42: error: 'avcodec_close' was not declared in this scope; did you mean 'avio_close'? ffmpeg.C:476:33: error: 'avcodec_close' was not declared in this scope; did you mean 'avio_close'? ffmpeg.C:1307:37: error: 'AVFrame' {aka 'struct AVFrame'} has no member named 'interlaced_frame' ffmpeg.C:1309:37: error: 'AVFrame' {aka 'struct AVFrame'} has no member named 'interlaced_frame' ffmpeg.C:1309:66: error: 'AVFrame' {aka 'struct AVFrame'} has no member named 'top_field_first' ffmpeg.C:1311:37: error: 'AVFrame' {aka 'struct AVFrame'} has no member named 'interlaced_frame' ffmpeg.C:1311:67: error: 'AVFrame' {aka 'struct AVFrame'} has no member named 'top_field_first' ffmpeg.C:1340:36: error: 'AVFrame' {aka 'struct AVFrame'} has no member named 'key_frame' ffmpeg.C:1512:24: error: 'AVFrame' {aka 'struct AVFrame'} has no member named 'interlaced_frame' ffmpeg.C:1513:24: error: 'AVFrame' {aka 'struct AVFrame'} has no member named 'top_field_first' ffmpeg.C:3847:29: error: 'av_stream_get_side_data' was not declared in this scope; did you mean 'av_frame_get_side_data'?
mplayer switched for now to branch 7.1 until it get updates.
i see in doc/APIchanges
2023-05-04 - 0fc9c1f6828 - lavu 58.7.100 - frame.h Deprecate AVFrame.interlaced_frame, AVFrame.top_field_first, and AVFrame.key_frame. Add AV_FRAME_FLAG_INTERLACED, AV_FRAME_FLAG_TOP_FIELD_FIRST, and AV_FRAME_FLAG_KEY flags as replacement.
but not sure how to use them yet.
On Wed, 9 Apr 2025, Andrew Randrianasulu via Cin wrote:
for some reason our x264 failed to encode (segfault) on i686 with AVX ? but x265 worked ....
There exists in my personal cinelerra memos: if gcc-4.8.2 or older (incomplete AVX2 support), add -DENABLE_AVX2=no to libaom.cfg_params? in thirdparty/Makefile Might be something similar? _______________________________________________________________________________ Georgy Salnikov NMR Group Novosibirsk Institute of Organic Chemistry Lavrentjeva, 9, 630090 Novosibirsk, Russia Phone +7-383-3307864 Email [email protected] _______________________________________________________________________________
ср, 9 апр. 2025 г., 18:51 Georgy Salnikov <[email protected]>:
On Wed, 9 Apr 2025, Andrew Randrianasulu via Cin wrote:
for some reason our x264 failed to encode (segfault) on i686 with AVX ? but x265 worked ....
There exists in my personal cinelerra memos:
if gcc-4.8.2 or older (incomplete AVX2 support), add -DENABLE_AVX2=no to libaom.cfg_params? in thirdparty/Makefile
Might be something similar?
oh, it probably just old nasm! I had 2.13 from Slackware 14.2 and it failed for me for new x264 new nasm from Slackware 15.0 version 2.15.05 seems to be working. A bit of bummer for old systems .... :( not sure if it affect everything or just i686
_______________________________________________________________________________
Georgy Salnikov NMR Group Novosibirsk Institute of Organic Chemistry Lavrentjeva, 9, 630090 Novosibirsk, Russia Phone +7-383-3307864 Email [email protected]
_______________________________________________________________________________
In Arch, Cmake4 has been updated. I tried a build (not ffmpeg.git) without the 2 patches on x265 (which is integrated in git though) and svtav1: all OK, no errors. Then I tried a build ffmpeg.git and got a crash, I think the same your error. I've nasm 2.16.03. I attach the log. (Question: if I compile with ffmpeg.git is it necessary to remove ffmpeg.git patches 2 and 8? Before now I had never done this) I tried using ffmpeg_8.diff, but I can't apply the patch.
пт, 11 апр. 2025 г., 11:11 Andrea paz <[email protected]>:
In Arch, Cmake4 has been updated. I tried a build (not ffmpeg.git) without the 2 patches on x265 (which is integrated in git though) and svtav1: all OK, no errors.
Then I tried a build ffmpeg.git and got a crash, I think the same your error. I've nasm 2.16.03. I attach the log. (Question: if I compile with ffmpeg.git is it necessary to remove ffmpeg.git patches 2 and 8? Before now I had never done this)
they fail to apply, so instead of adapting them I just removed them for testing further ...
I tried using ffmpeg_8.diff, but I can't apply the patch.
hm ..... works here: ~/cinelerra $ cat ~/storage/downloads/ffmpeg_8.diff | patch -p1 patching file cinelerra-5.1/cinelerra/bdwrite.C patching file cinelerra-5.1/cinelerra/ffmpeg.C Hunk #2 succeeded at 478 (offset 3 lines). Hunk #3 succeeded at 1310 (offset 3 lines). Hunk #4 succeeded at 1318 (offset 3 lines). Hunk #5 succeeded at 1351 (offset 3 lines). Hunk #6 succeeded at 1527 (offset 3 lines). Hunk #7 succeeded at 3871 (offset 5 lines). patching file cinelerra-5.1/cinelerra/fileac3.C
I compiled with ffmpeg.git and patched with ffmpeg_8.diff (it works for me with -p2). I also put in the tiff patch (plus tarball) and used Cmake4. I have a crash near the end. I attach the log. To check if the tiff patch is to blame, I did a build with normal ffmpeg (not git) using the same patches. Everything works fine.
пт, 11 апр. 2025 г., 21:07 Andrea paz <[email protected]>:
I compiled with ffmpeg.git and patched with ffmpeg_8.diff (it works for me with -p2). I also put in the tiff patch (plus tarball) and used Cmake4. I have a crash near the end. I attach the log. To check if the tiff patch is to blame, I did a build with normal ffmpeg (not git) using the same patches. Everything works fine.
sr/bin/ld: impossibile trovare /home/paz/cinelerra5/cinelerra-5.1/mpeg2enc/../thirdparty/tiff-4.6.0t/libtiff/.libs/libtiff.a: File o directory non esistente /usr/bin/ld: impossibile trovare /home/paz/cinelerra5/cinelerra-5.1/mpeg2enc/../thirdparty/tiff-4.6.0t/libtiff/.libs/libtiffxx.a: File o directory non esistente /usr/bin/ld: impossibile trovare /home/paz/cinelerra5/cinelerra-5.1/mpeg2enc/../thirdparty/tiff-4.6.0t/port/.libs/libport.a: File o directory non esistente be sure you run ./autogen.sh ? so it will regenerate configure and configure will set correct oath to new libtiff ... also, may be remove old 4.6.0t tarball and rename tiff patches from 4.6.0t to 4.7.0? sorry I forgot about them ..... I see they applied fine and build of libtiff itself is fine, but then old path sneaks in and ruin compile ... sorry for time raken
In .../thirdparty/src there is also a tarball “tiff-4.6.0t.tar.xz” i.e. with an extra “t” after the 0. There are also 2 patches concerning this version with the extra “t”. I cannot find on git any tarball 4.7.0 with the extra “t” (there is a version with “orca”). I tried to delete tarball and its 2 patches, but I have a crash of which I attach the “cin_t.log”. I redid the compilation leaving tarball and the 2 patches (4.6.0) and I still have a crash of which I attach the “cin_6.log”. Finally, out of curiosity, I tried a build without thirdparty, that is, with system ffmpeg and no patches. The build is successful and I can load and work on tiff images.
сб, 12 апр. 2025 г., 12:23 Andrea paz <[email protected]>:
In .../thirdparty/src there is also a tarball “tiff-4.6.0t.tar.xz” i.e. with an extra “t” after the 0. There are also 2 patches concerning this version with the extra “t”. I cannot find on git any tarball 4.7.0 with the extra “t” (there is a version with “orca”). I tried to delete tarball and its 2 patches, but I have a crash of which I attach the “cin_t.log”.
patch -d tiff* -p1 < src/tiff-4.7.0.patch1 accuracy.c:286:3: warning: incompatible implicit declaration of built-in function ‘exit’ [-Wbuiltin-declaration-mismatch] 286 | exit(0); | ^~~~ accuracy.c:286:3: note: include ‘<stdlib.h>’ or provide a declaration of ‘exit’ make[4]: ingresso nella directory «/home/paz/cinelerra5/cinelerra-5.1/thirdparty/dav1d-0.5.1» ./compile hier.c patching file Makefile.am Hunk #1 FAILED at 60. 1 out of 1 hunk FAILED -- saving rejects to file Makefile.am.rej checking for a BSD-compatible install... make[2]: *** [Makefile:386: /home/paz/cinelerra5/cinelerra-5.1/thirdparty/../thirdparty/build/tiff.source] Error 1 so ... I need to work more on this ;) sorry I redid the compilation leaving tarball and the 2 patches (4.6.0) and
I still have a crash of which I attach the “cin_6.log”. Finally, out of curiosity, I tried a build without thirdparty, that is, with system ffmpeg and no patches. The build is successful and I can load and work on tiff images.
well, if you link to system ffmpeg and libtiff there is no miracle ;)
сб, 12 апр. 2025 г., 12:35 Andrew Randrianasulu <[email protected]>:
сб, 12 апр. 2025 г., 12:23 Andrea paz <[email protected]>:
In .../thirdparty/src there is also a tarball “tiff-4.6.0t.tar.xz” i.e. with an extra “t” after the 0. There are also 2 patches concerning this version with the extra “t”. I cannot find on git any tarball 4.7.0 with the extra “t” (there is a version with “orca”). I tried to delete tarball and its 2 patches, but I have a crash of which I attach the “cin_t.log”.
patch -d tiff* -p1 < src/tiff-4.7.0.patch1 accuracy.c:286:3: warning: incompatible implicit declaration of built-in function ‘exit’ [-Wbuiltin-declaration-mismatch] 286 | exit(0); | ^~~~ accuracy.c:286:3: note: include ‘<stdlib.h>’ or provide a declaration of ‘exit’ make[4]: ingresso nella directory «/home/paz/cinelerra5/cinelerra-5.1/thirdparty/dav1d-0.5.1» ./compile hier.c patching file Makefile.am Hunk #1 FAILED at 60. 1 out of 1 hunk FAILED -- saving rejects to file Makefile.am.rej checking for a BSD-compatible install... make[2]: *** [Makefile:386: /home/paz/cinelerra5/cinelerra-5.1/thirdparty/../thirdparty/build/tiff.source] Error 1
so ... I need to work more on this ;)
sorry
strange. I removed 4.6.0 patches and tarball, 4.6.0t tarball, renamed 4.6.0t patches to 4.7.0 patches and build on termux finished unattended? see attached git am patch that add just same 4.6.0t patches as 4.7.0
I redid the compilation leaving tarball and the 2 patches (4.6.0) and
I still have a crash of which I attach the “cin_6.log”. Finally, out of curiosity, I tried a build without thirdparty, that is, with system ffmpeg and no patches. The build is successful and I can load and work on tiff images.
well, if you link to system ffmpeg and libtiff there is no miracle ;)
@Andrew thanks to you I was able to compile CinGG with ffmpeg.git; Cmake4 and tiff-4.7.0.
Tiff extra "t" at 4.6.0 was because in 4.6.0 the developers removed a bunch of code that had not been worked on for a long time and they considered it to be a security issue. They then realized their mistake in removing that code so they put it back and added the "t" as the release number. With 4.7.0 (and no "t" needed) they added all of that code back and I did not check but would imagine they plugged any security holes. On Sat, Apr 12, 2025 at 3:24 AM Andrea paz via Cin < [email protected]> wrote:
In .../thirdparty/src there is also a tarball “tiff-4.6.0t.tar.xz” i.e. with an extra “t” after the 0. There are also 2 patches concerning this version with the extra “t”. I cannot find on git any tarball 4.7.0 with the extra “t” (there is a version with “orca”). I tried to delete tarball and its 2 patches, but I have a crash of which I attach the “cin_t.log”. I redid the compilation leaving tarball and the 2 patches (4.6.0) and I still have a crash of which I attach the “cin_6.log”. Finally, out of curiosity, I tried a build without thirdparty, that is, with system ffmpeg and no patches. The build is successful and I can load and work on tiff images. -- Cin mailing list [email protected] https://lists.cinelerra-gg.org/mailman/listinfo/cin
participants (4)
-
Andrea paz -
Andrew Randrianasulu -
Georgy Salnikov -
Phyllis Smith