Builder ffmpegsos-solaris10-sparc Build #12092

Results:

Failed shell_2 shell_3 shell_4 shell_5

SourceStamp:

BuildSlave:

Reason:

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

Steps and Logfiles:

1. git update ( 17 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 ( 14 secs )
   1. stdio
   2. config.log
6. shell_4 'gmake fate-rsync' failed ( 0 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. Kacper Michajłow

   kasper93ohnoyoudont@gmail.com

Timing:

All Changes:

:

1. Change #242150

   Category	ffmpeg
   Changed by	Kacper Michajłow <kasper93ohnoyoudont@gmail.com>
   Changed at	Tue 05 Aug 2025 18:31:04
   Repository	https://git.ffmpeg.org/ffmpeg.git
   Project	ffmpeg
   Branch	master
   Revision	5b3d6c046002fe51a5f20059b7d529e4fbc6caa4

   Comments

   configure: don't use dangling temp file state
   There was implicit assumption that the $TMPC file is empty when doing
   --cpu=host checks. This breaks if any check is done before that.
   
   Signed-off-by: Kacper Michajłow <kasper93@gmail.com>

   Changed files

   • configure

2. Change #242151

   Category	ffmpeg
   Changed by	Kacper Michajłow <kasper93ohnoyoudont@gmail.com>
   Changed at	Tue 05 Aug 2025 18:31:04
   Repository	https://git.ffmpeg.org/ffmpeg.git
   Project	ffmpeg
   Branch	master
   Revision	50408c55ac4c1f56c9e90d120bbc6cfc6034351a

   Comments

   configure: filter link flags separately for MSVC
   This avoids adding flags that cl.exe doesn't understand.
   
   Fixes cases where external libraries pkg-config file adds `-L` to the
   cflags, strip it before passing to cl.exe.
   
   Signed-off-by: Kacper Michajłow <kasper93@gmail.com>

   Changed files

   • configure

3. Change #242152

   Category	ffmpeg
   Changed by	Kacper Michajłow <kasper93ohnoyoudont@gmail.com>
   Changed at	Tue 05 Aug 2025 18:31:05
   Repository	https://git.ffmpeg.org/ffmpeg.git
   Project	ffmpeg
   Branch	master
   Revision	bc012ac9187b00fa8ea0e1d000ceff684775d5ee

   Comments

   configure: treat unrecognized flags as errors on MSVC
   This is important for feature checking to work correctly.
   
   It can happen that an unrecognized flag passes the compile test with
   only a warning, while failing in preprocessor-only check with an error.
   This causes all test_cpp calls to fail and silently produces arguably
   broken MSVC builds. Also, all check_* functions don't work as expected,
   because they assume the check passed, even though there was a warning.
   
   Additionally, this brings the behavior in line with GCC/Clang based
   builds, failing early on unrecognized flags instead of silently
   continuing with warnings in the log.
   
   The /options:strict option is available starting in Visual Studio 2022
   version 17.0. Because of that, we cannot use check_cflags alone, as it
   would add this flag for older MSVC versions and produce warnings. So, we
   need to manually perform a version check. A bit of a chicken and egg
   problem.
   
   Perform the version check before adding extra flags from the user to
   ensure we don't silently fail the preprocessor check due to invalid
   flags on older MSVC versions. Note that behavior differs depending on
   whether we are compiling or only preprocessing.
   
   This fixes silent different between handling:
   
   `cl.exe -P foo c.c`
       c1: fatal error C1083: Cannot open source file: 'foo': No such file
       or directory
   
   `cl.exe -c foo c.c`
       cl : Command line warning D9024 : unrecognized source file type
       'foo', object file assumed
   
   Where -P fails, while -c throws warnings only. Of course `foo` is
   completely bogus here, but depends on the flags or configuration this
   may be unsupported argument. Or even some converted path from MSYS when
   run inside it. The objective is to always error out instead of silently
   hiding this.
   
   Use check_cflags even after the _MSC_FULL_VER check, for non-MSVC
   compilers. For example Clang-CL impersonate MSVC, but does not support
   -options:strict flag currently.
   
   Signed-off-by: Kacper Michajłow <kasper93@gmail.com>

   Changed files

   • configure