Builder tcpdump-solaris10-sparc Build #6254

Results:

Build successful

SourceStamp:

BuildSlave:

Reason:

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

Steps and Logfiles:

1. git update ( 18 secs )
   1. stdio
2. shell Set developer mode ( 0 secs )
   1. stdio
3. shell_1 './autogen.sh' ( 27 secs )
   1. stdio
4. shell_2 configure ( 2 mins, 56 secs )
   1. stdio
   2. config.log
5. shell_3 'gmake' ( 15 mins, 48 secs )
   1. stdio
6. shell_4 'gmake check' ( 1 mins, 21 secs )
   1. stdio
   2. failure-outputs.txt

Build Properties:

Forced Build Properties:

Responsible Users:

1. Denis Ovsienko

   denisohnoyoudont@ovsienko.info

Timing:

All Changes:

:

1. Change #276564

   Category	tcpdump
   Changed by	Denis Ovsienko <denisohnoyoudont@ovsienko.info>
   Changed at	Thu 30 Jul 2026 11:40:13
   Repository	https://git.tcpdump.org/tcpdump
   Project	tcpdump
   Branch	master
   Revision	c8b8393d898270817e3b59120739e88a2c55845c

   Comments

   Recommend "make check" in INSTALL.md. [skip ci]
   It would not be difficult to run a compiled C program in Autoconf and
   CMake to test whether the compiler uses correct floating point
   instructions for the hardware, but there is only one known case of the
   problem, on a Linux distribution that became unsupported 10 years ago
   (see GH #1344), and "make check" already does exactly the same.

   Changed files

   • INSTALL.md