Builder libpcap-solaris11-sparc Build #170

Results:

Build successful

SourceStamp:

BuildSlave:

Reason:

The SingleBranchScheduler scheduler named 'schedule-libpcap-solaris11-sparc' triggered this build

Steps and Logfiles:

1. git update ( 4 secs )
   1. stdio
2. shell './build_matrix.sh' ( 4 hrs, 2 mins, 9 secs )
   1. stdio
   2. config.log
3. trigger triggered trigger-tcpdump-solaris11-sparc ( 1 hrs, 14 mins, 24 secs )
   1. - no logs -
   2. tcpdump-solaris11-sparc #181

Build Properties:

Forced Build Properties:

Responsible Users:

1. Denis Ovsienko

   denisohnoyoudont@ovsienko.info

Timing:

All Changes:

:

1. Change #278487

   Category	libpcap
   Changed by	Denis Ovsienko <denisohnoyoudont@ovsienko.info>
   Changed at	Mon 17 Aug 2026 11:27:13
   Repository	https://git.tcpdump.org/libpcap
   Project	libpcap
   Branch	master
   Revision	faa0f0f53bbc0c5a6a00e39442f537d853da3d4a

   Comments

   Add tests for the PCAP_BSWAP_ macros.

   Changed files

   • testprogs/TESTrun
   • testprogs/translatetest.c

2. Change #278488

   Category	libpcap
   Changed by	Denis Ovsienko <denisohnoyoudont@ovsienko.info>
   Changed at	Mon 17 Aug 2026 11:27:14
   Repository	https://git.tcpdump.org/libpcap
   Project	libpcap
   Branch	master
   Revision	f24d2e43be71d100ea723958cb59b8efa5ed1b35

   Comments

   Detect __builtin_ctz() directly.
   LLVM has been implementing the builtin since release 1.6.  LLVM release
   2.1 had introduced Clang, which originally started to define GCC version
   macros the same way as GCC 4.0.1 and later went up to GCC 4.2.1.  Clang
   release 10.0 had introduced the "-fgnuc-version=" command-line option to
   override this default behaviour.  This way, the current guard condition
   of GCC >= 3.4 usually matches Clang as well, but this is neither obvious
   nor certain.
   
   TinyCC does not define GCC version macros, its latest stable release at
   the time of this writing ("0.9.27", __TINYC__ == 927) does not support
   the builtin.  Later development snapshots started to support the builtin
   whilst still declaring __TINYC__ to 927, later __TINYC__ became 928, but
   the version is still "0.9.28rc".  This way, the current guard condition
   does not match TinyCC and cannot be extended to match, in a reliable
   manner, versions that support the builtin.
   
   Reduce this problem space to the only factor that matters: whether the
   compiler in fact implements the builtin.  This detects the expected
   results for:
   
   * GCC 14.2.0 (positive)
   * Clang 19.1.7 (positive)
   * TinyCC 0.9.27 (negative)
   * TinyCC 0.9.28rc mob@2be0218b (positive)
   * Sun C 5.15 (negative)

   Changed files

   • CMakeLists.txt
   • cmakeconfig.h.in
   • configure.ac
   • optimize.c