Builder libpcap-solaris10-amd64 Build #2821

Results:

Build successful

SourceStamp:

BuildSlave:

Reason:

The SingleBranchScheduler scheduler named 'schedule-libpcap-solaris10-amd64' triggered this build

Steps and Logfiles:

1. git update ( 4 secs )
   1. stdio
2. shell Set developer mode ( 0 secs )
   1. stdio
3. shell_1 './autogen.sh' ( 2 secs )
   1. stdio
4. shell_2 './configure' ( 8 secs )
   1. stdio
   2. config.log
5. shell_3 'gmake' ( 6 secs )
   1. stdio
6. shell_4 'rm -rf ...' ( 0 secs )
   1. stdio
7. shell_5 'gmake install ...' ( 0 secs )
   1. stdio
8. trigger triggered trigger-tcpdump-solaris10-amd64 ( 1 mins, 40 secs )
   1. - no logs -
   2. tcpdump-solaris10-amd64 #5312

Build Properties:

Forced Build Properties:

Responsible Users:

1. Guy Harris

   gharrisohnoyoudont@sonic.net

Timing:

All Changes:

:

1. Change #193218

   Category	libpcap
   Changed by	Guy Harris <gharrisohnoyoudont@sonic.net>
   Changed at	Mon 18 Mar 2024 22:24:58
   Repository	https://git.tcpdump.org/libpcap
   Project	libpcap
   Branch	master
   Revision	2d12e865c43dddf064b50b1eba276e49d750fe29

   Comments

   usb-linux: reorganize the isochronous length handling code.
   Put useful inline functions, used both by the capture code and the
   savefile length fixup code, into pcap-usb-linux-common.h; some of those
   came from, or are based on routines in, pcap-usb-linux-common.c, which
   we remove.
   
   When capturing, all we need to do is check whether a message with data
   is a "this is complete" incoming isochronous transfer event and, if so,
   use the routine to calculate its original length.
   
   Pull the routine to fix up the original length into
   pcapint_post_process().
   
   When reading savefiles, we need to do additional checks to guess whether
   the length needs fixing and to determine whether the number of
   descriptors is sane and whether we have all the descriptors; do that in
   pcapint_post_process().
   
   Add some additional checks.
   
   Call the "len" field of pcap's metadata header the "original length"
   rather than the "on-the-wire" length; that matches the terminology from
   the current versions of the pcap and pcapng specs, and doesn't imply
   that the length is the length of the packet on the transmission medium,
   as that's not always the case - for USB, it's computed based on
   information from the endpoint on which we're capturing, and may also
   include padding between isochronous data chunks.

   Changed files

   • CMakeLists.txt
   • Makefile.in
   • pcap-usb-linux-common.c
   • pcap-usb-linux-common.h
   • pcap-usb-linux.c
   • pcap-util.c
   • pcap-util.h

2. Change #193219

   Category	libpcap
   Changed by	Guy Harris <gharrisohnoyoudont@sonic.net>
   Changed at	Mon 18 Mar 2024 22:29:13
   Repository	https://git.tcpdump.org/libpcap
   Project	libpcap
   Branch	master
   Revision	5a5a422b278afde42a49ef7c6d70870e3ba9d489

   Comments

   CHANGES: another change in main and 1.10. [skip ci]

   Changed files

   • CHANGES