Builder ffmpeg64-solaris10-i386 Build #14130

Results:

Failed

SourceStamp:

BuildSlave:

Reason:

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

Steps and Logfiles:

1. git updating ( 5 secs )
   1. stdio
2. shell  
   1. - no logs -
3. shell_1  
   1. - no logs -
4. shell_2  
   1. - no logs -
5. shell_3  
   1. - no logs -
6. shell_4  
   1. - no logs -
7. shell_5  
   1. - no logs -

Build Properties:

Forced Build Properties:

Responsible Users:

1. Kacper Michajłow

   kasper93ohnoyoudont@gmail.com

Timing:

All Changes:

:

1. Change #281829

   Category	ffmpeg
   Changed by	Kacper Michajłow <kasper93ohnoyoudont@gmail.com>
   Changed at	Mon 14 Sep 2026 23:09:36
   Repository	https://git.ffmpeg.org/ffmpeg.git
   Project	ffmpeg
   Branch	master
   Revision	b4bd8d1f646e51d486aff16c70b564a21223cee9

   Comments

   configure: drop the redundant ObjC flags from check_allcflags
   ObjC is compiled with the C flags. OBJCCFLAGS in ffbuild/common.mak
   includes CFLAGS and test_objcc() passes it as well. OBJCFLAGS is meant
   for what ObjC needs beyond C. No need to duplicate all flags there.
   
   They were needed for the short while 0ce413af9c had $CFLAGS taken out of
   test_objcc(). 189d0b83b2 put it back and left the duplication.
   
   Note that the issue is not only cosmetic duplication, for example MSVC
   cannot compile ObjC, so the check_allcflags never suceeded there. While
   the ObjC were checked last, flags were added for C/CXX, but the return
   value was always false.
   
   Signed-off-by: Kacper Michajłow <kasper93@gmail.com>

   Changed files

   • configure

2. Change #281830

   Category	ffmpeg
   Changed by	Kacper Michajłow <kasper93ohnoyoudont@gmail.com>
   Changed at	Mon 14 Sep 2026 23:09:36
   Repository	https://git.ffmpeg.org/ffmpeg.git
   Project	ffmpeg
   Branch	master
   Revision	50e64f97d901d88276599b537e7eaa61d454758a

   Comments

   configure: apply common flags to C++ as well
   0ce413af9c stopped prepending CFLAGS to CXXFLAGS and converted the call
   sites that have to reach every language, but not these. So, things were
   silently not added for C++ compilation.
   
   The impact is small, because we have only handful of C++ files, but
   still this needed fixing.
   
   Signed-off-by: Kacper Michajłow <kasper93@gmail.com>

   Changed files

   • configure

3. Change #281831

   Category	ffmpeg
   Changed by	Kacper Michajłow <kasper93ohnoyoudont@gmail.com>
   Changed at	Mon 14 Sep 2026 23:09:36
   Repository	https://git.ffmpeg.org/ffmpeg.git
   Project	ffmpeg
   Branch	master
   Revision	45ec2cae195ec43662cbdb6899caee99a6d657fc

   Comments

   configure: drop -Werror from the C++ warning probe
   0ce413af9c gave check_disable_warning() a C++ checks at a time when
   unknown_warning_flags was a single set probed with test_cflags, so it
   said nothing about what the C++ compiler accepts. The -Werror was added
   as a glue that reject C only flags from C++ compilation and probe time.
   However, after 005510501e made those flags per language and
   unknown_warning_cxxflags is now probed with test_cxxflags, so the Werror
   is no longer relevant.
   
   This is not only cosmetic change, because -Werror itself is not valid
   flag for MSVC, all tests were failing there.
   
   Signed-off-by: Kacper Michajłow <kasper93@gmail.com>

   Changed files

   • configure

4. Change #281832

   Category	ffmpeg
   Changed by	Kacper Michajłow <kasper93ohnoyoudont@gmail.com>
   Changed at	Mon 14 Sep 2026 23:09:36
   Repository	https://git.ffmpeg.org/ffmpeg.git
   Project	ffmpeg
   Branch	master
   Revision	77b9dc4159b9f4247ec29e4cd6e1c0dcc7c5caed

   Comments

   configure: check sanitizer flags before adding them
   Configure now will die and report correct error message if
   unsupported sanitizer is requested. Instead of adding flags
   unconditionally.
   
   The linker flags are added only if supported. Some compilers like MSVC,
   does not need/want them. The same goes for -fno-omit-frame-pointer which
   is added only when supported now.
   
   Probing needs the temporary files and the probed tools, neither of which
   exists where the toolchain is selected, hence the requested sanitizers
   are gathered and actual probe is defered to after toolchain is
   established.
   
   Signed-off-by: Kacper Michajłow <kasper93@gmail.com>

   Changed files

   • configure

5. Change #281833

   Category	ffmpeg
   Changed by	Kacper Michajłow <kasper93ohnoyoudont@gmail.com>
   Changed at	Mon 14 Sep 2026 23:09:36
   Repository	https://git.ffmpeg.org/ffmpeg.git
   Project	ffmpeg
   Branch	master
   Revision	8edbc167194bdbb68658ca7e59300f6cc2e8ac6d

   Comments

   configure: allow sanitizers for msvc toolchain
   MSVC spells the option the same way, see
   https://learn.microsoft.com/en-us/cpp/build/reference/fsanitize, so the
   existing handling already covers it.
   
   This allows `--toolchain=msvc-asan`.
   
   Signed-off-by: Kacper Michajłow <kasper93@gmail.com>

   Changed files

   • configure