Builder ffmpegsos-solaris10-i386 Build #13359

Results:

Failed shell_2 shell_3 shell_4 shell_5

SourceStamp:

BuildSlave:

Reason:

The SingleBranchScheduler scheduler named 'schedule-ffmpegsos-solaris10-i386' triggered this build

Steps and Logfiles:

1. git update ( 11 secs )
   1. stdio
2. shell 'gsed -i ...' ( 0 secs )
   1. stdio
3. shell_1 'gsed -i ...' ( 0 secs )
   1. stdio
4. shell_2 'gsed -i ...' failed ( 0 secs )
   1. stdio
5. shell_3 './configure --samples="../../../ffmpeg/fate-suite" ...' failed ( 10 secs )
   1. stdio
   2. config.log
6. shell_4 'gmake fate-rsync' failed ( 1 secs )
   1. stdio
7. shell_5 '../../../ffmpeg/fate.sh ../../../ffmpeg/fate_config_sos.sh' failed ( 0 secs )
   1. stdio
   2. configure.log
   3. compile.log
   4. test.log

Build Properties:

Forced Build Properties:

Responsible Users:

1. Andreas Rheinhardt

   andreas.rheinhardtohnoyoudont@outlook.com

Timing:

All Changes:

:

1. Change #258301

   Category	ffmpeg
   Changed by	Andreas Rheinhardt <andreas.rheinhardtohnoyoudont@outlook.com>
   Changed at	Fri 20 Feb 2026 11:59:37
   Repository	https://git.ffmpeg.org/ffmpeg.git
   Project	ffmpeg
   Branch	master
   Revision	05098eef4265c6abf680d5b8585e777d3ed743f6

   Comments

   configure: Use per-language unknown-warnings-flags
   E.g. when CC is clang, the unknown warnings flags
   are -Werror=unused-command-line-argument and
   -Werror=unknown-warning-option. These flags are currently
   also used for testing the C++ and ObjC compilers, yet
   g++ does not recognize these flags and errors out because
   of them, so that the tests fail and the parentheses,
   switch etc. warnings are not disabled for C++.
   
   Fix this by using per-language flags.
   
   Signed-off-by: Andreas Rheinhardt <andreas.rheinhardt@outlook.com>

   Changed files

   • configure

2. Change #258302

   Category	ffmpeg
   Changed by	Andreas Rheinhardt <andreas.rheinhardtohnoyoudont@outlook.com>
   Changed at	Fri 20 Feb 2026 11:59:37
   Repository	https://git.ffmpeg.org/ffmpeg.git
   Project	ffmpeg
   Branch	master
   Revision	005510501efcd1f4e8abae605a341c2a3d35df56

   Comments

   configure: Make check for accepting warnings stricter
   Clang by default allows unknown warnings and merely emits
   a Wunknown-warning-option warning which is non-fatal by default,
   making it appear as if Clang supported any warning. This patch
   rewrites the tests to always add the arguments to error out
   in case an unrecognized option is encountered.
   
   Signed-off-by: Andreas Rheinhardt <andreas.rheinhardt@outlook.com>

   Changed files

   • configure

3. Change #258303

   Category	ffmpeg
   Changed by	Andreas Rheinhardt <andreas.rheinhardtohnoyoudont@outlook.com>
   Changed at	Fri 20 Feb 2026 11:59:37
   Repository	https://git.ffmpeg.org/ffmpeg.git
   Project	ffmpeg
   Branch	master
   Revision	acde43703fea03d76c7777c26340dd80f23ea91d

   Comments

   avutil/error: Remove size from error_stringtable
   This stringtable is a concatenation of strings, with their
   own trailing \0. Without an explicit size said stringtable
   ends with two \0 (one from the last string and one more
   because it is initialized via a string literal); the explicit
   size exists to discard the last \0.
   
   Yet this makes GCC (but not Clang) think that this is an
   unterminated string, leading to warnings when
   -Wunterminated-string-initialization is enabled.
   So just remove the explicit size to avoid this.
   
   (An alternative would be to mark this as a non-string
   for GCC, but not for Clang, but this has been deemed ugly;
   another alternative would be to omit the internal \0 from
   the stringtable and use length fields instead, but
   the necessary copying code more than outweighs the size benefits
   of omitting the \0.)
   
   Signed-off-by: Andreas Rheinhardt <andreas.rheinhardt@outlook.com>

   Changed files

   • libavutil/error.c

4. Change #258304

   Category	ffmpeg
   Changed by	Andreas Rheinhardt <andreas.rheinhardtohnoyoudont@outlook.com>
   Changed at	Fri 20 Feb 2026 11:59:37
   Repository	https://git.ffmpeg.org/ffmpeg.git
   Project	ffmpeg
   Branch	master
   Revision	0b77f791912bf6355206c68b677e71cd61227036

   Comments

   avutil/attributes_internal: Add attribute_nonstring
   This attribute is used to signal to the compiler
   that an array object initialized via a string literal
   is not a real string and may lack the space for
   the trailing zero, as in char fourcc[4]="FOUR".
   
   This is in preparation for enabling
   the -Wunterminated-string-initialization warning.
   
   Reviewed-by: J. Dekker <jdek@itanimul.li>
   Signed-off-by: Andreas Rheinhardt <andreas.rheinhardt@outlook.com>

   Changed files

   • libavcodec/gif.h
   • libavformat/amr.c
   • libavformat/concatdec.c
   • libavformat/id3v2.c
   • libavformat/mccdec.c
   • libavutil/attributes_internal.h
   • libavutil/tests/blowfish.c
   • libavutil/uuid.c

5. Change #258305

   Category	ffmpeg
   Changed by	Andreas Rheinhardt <andreas.rheinhardtohnoyoudont@outlook.com>
   Changed at	Fri 20 Feb 2026 11:59:37
   Repository	https://git.ffmpeg.org/ffmpeg.git
   Project	ffmpeg
   Branch	master
   Revision	9a7e0f10526f11a22fb12f1678198c09fe41dff6

   Comments

   configure: Enable -Wunterminated-string-initialization warning
   When an array of pointers to strings is converted into
   an array of constant-length strings, one has to find out
   the maximum size of the strings. Currently no warning will
   be emitted If one forgets to account for the trailing zero,
   making this optimization dangerous (think of the scenario
   where the array will be modified without adjusting the maximum
   size of the strings).
   
   The -Wunterminated-string-initialization warning catches these cases.
   It is supported by GCC 15.1 and Clang 21. It only requires to mark
   the few instances of arrays initialized via string literals that
   are not supposed to be strings with the nonstring attribute; this
   has already been done in the previous commit.
   
   Signed-off-by: Andreas Rheinhardt <andreas.rheinhardt@outlook.com>

   Changed files

   • configure