Builder tcpdump-solaris11-i386 Build #94

Results:

Build successful

SourceStamp:

BuildSlave:

Reason:

The SingleBranchScheduler scheduler named 'schedule-tcpdump-solaris11-i386' triggered this build

Steps and Logfiles:

1. git update ( 5 secs )
   1. stdio
2. shell 'rm -rf ...' ( 0 secs )
   1. stdio
3. shell_1 'git clone ...' ( 4 secs )
   1. stdio
4. shell_2 './build_matrix.sh' ( 4 hrs, 48 mins, 49 secs )
   1. stdio
   2. config.log

Build Properties:

Forced Build Properties:

Responsible Users:

1. Guy Harris

   gharrisohnoyoudont@sonic.net

Timing:

All Changes:

:

1. Change #258501

   Category	tcpdump
   Changed by	Guy Harris <gharrisohnoyoudont@sonic.net>
   Changed at	Sun 22 Feb 2026 08:20:13
   Repository	https://git.tcpdump.org/tcpdump
   Project	tcpdump
   Branch	master
   Revision	984812cad2a7aa230e24ee61d35a93cab592b4db

   Comments

   tcpdump: force POSIX-style parsing of the command line.
   By default, all versions of getopt_long() that I could find do GNU-style
   parsing of command-line flags, meaning *any* command-line argument that
   begins with a "-", even if they follow an argument that doesn't begin
   with "-", is treated as an option.
   
   That breaks commands such as "tcpdump -d ip[4:4] == -1", because "-1" is
   parsed as a flag argument rather than as "minus one" in a filter
   expression.
   
   (Yes, I tested that with the last LBL release of tcpdump, 3.4, which
   didn't use getopt_long(), compiled with macOS Ventura getopt() and
   libpcap - that command *does* work there. So this is a long-standing
   regression.)
   
   Fix the test script not to implicitly assume GNU-style parsing by
   putting "-tttt" after all other command-line arguments, including a
   packet filter; put it before those arguments.  Rename the variable
   containing those arguments to make it clear that it's command-line
   arguments in general, not just option arguments.

   Changed files

   • CHANGES
   • tcpdump.c
   • tests/TESTrun