Builder ffmpegsos-solaris10-sparc Build #12592

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 ( 15 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 ( 7 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. Martin Storsjö

   martinohnoyoudont@martin.st

Timing:

All Changes:

:

1. Change #252774

   Category	ffmpeg
   Changed by	Martin Storsjö <martinohnoyoudont@martin.st>
   Changed at	Fri 19 Dec 2025 19:38:33
   Repository	https://git.ffmpeg.org/ffmpeg.git
   Project	ffmpeg
   Branch	master
   Revision	6149ceadebecc357f350a6979174dbd24f5dca28

   Comments

   configure: Recognize uname "Windows_NT" as using an .exe suffix
   Busybox-w32 [1] works for building ffmpeg on Windows (as an
   alternative to msys2, cygwin or WSL).
   
   On busybox-w32, "uname" returns "Windows_NT"; recognize this
   in exesuf() as having an .exe suffix.
   
   If building in this environment with a mingw toolchain, one has
   to explicitly set --target-os=mingw32. (We probably don't
   want to imply that this uname, set as target_os_default, would
   default to mingw?) But despite what is set with --target-os,
   one can't override the configure variable "host_os", which
   exesuf() has to recognize.
   
   [1] https://github.com/rmyorston/busybox-w32

   Changed files

   • configure

2. Change #252775

   Category	ffmpeg
   Changed by	Martin Storsjö <martinohnoyoudont@martin.st>
   Changed at	Fri 19 Dec 2025 19:38:33
   Repository	https://git.ffmpeg.org/ffmpeg.git
   Project	ffmpeg
   Branch	master
   Revision	06a17fdafcb3c3cd91f85b3685768d522c52286d

   Comments

   tests: Fix fate-run.sh to handle busybox-w32 absolute paths
   Busybox-w32 uses regular Windows style paths with drive letters,
   but with forward slashes; thus an absolute path starts with "c:/".
   
   Make the target_path() function in fate-run.sh (which converts a
   potentially relative path to an absolute one, under the target_path
   prefix) handle this case.
   
   With this in place, running fate tests almost works in
   busybox-w32 - only one issue remains. A patch [1] has been sent to
   upstream busybox for fixing that issue (which also is present if
   running fate tests on busybox on Linux), but it hasn't been
   responded to yet.
   
   [1] https://lists.busybox.net/pipermail/busybox/2025-December/091851.html

   Changed files

   • tests/fate-run.sh