| Commit message (Collapse) | Author | Age | Files | Lines |
|---|
| |
|
|
|
|
| |
Update based on draft-ietf-opsawg-pcap.
[skip ci]
|
| | |
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
The SuSv4 description of make at
https://pubs.opengroup.org/onlinepubs/9699919799/utilities/make.html
says, in "Makefile syntax", that "Blank lines, empty lines, and lines
with <number-sign> ( '#' ) as the first character on the line are also
known as comment lines."
In at least some versions of make, lines in the set of target rules shoe
first character is a tab and whose *second* character is a # are treated
as commands, not comments. Given that shells normally treat # as the
beginning of a comment, those end up being "commands" that do nothing
and return an exit status of 0, so they happen to work, but they
1) may cause a shell process to be created to run them;
2) cause extra output from make if it's printing comments.
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
install-sh has no longer a tab at the end of one line.
This is a follow-up to b46c2cfc9a1968e61d628ce03b2d919a1136013f.
diff --git a/Makefile.in b/Makefile.in
index cd0f01c3..80f5bc82 100644
--- a/Makefile.in
+++ b/Makefile.in
@@ -546,8 +546,7 @@ whitespacecheck:
exit 1; \
fi
@# trailing tab(s)?
- @# install-sh has a tab at the end of one line
- @if git grep -I -n ' $$' $$(git ls-files|grep -vE '^(tests/|install-sh$$)'); then \
+ @if git grep -I -n ' $$' $$(git ls-files|grep -v '^tests/'); then \
echo 'Error: Trailing tabs(s).'; \
exit 1; \
fi
.
|
| |
|
|
|
|
|
|
|
|
| |
This gives it a name similar to the other README.{operatingsystem}
files.
It also reflects that 1) 16-bit Windows is now so old and tired that
there's no need to use a name that specifically mentions a non-16-bit
version of Windows to indicates that we don't support it and 2) there's
now 64-bit Windows, so "Win32" is an out-of-date name.
|
| |
|
|
|
|
| |
This reverts commit c7f7036094bf9c48fdfa803085857a35753e938f.
This is a follow-up to 5e6aead918140299fd5b12c74dd4c728732ab47d.
|
| | |
|
| |
|
|
|
|
| |
This should avoid, with autotools, when doing parallel builds:
make[2]: *** No rule to make target '../libpcap.a', needed by
'valgrindtest'. Stop.
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
From https://www.gnu.org/software/make/manual/make.html#MAKE-Variable:
```
Recursive make commands should always use the variable MAKE, not the
explicit command name 'make', as shown here:
subsystem:
cd subdir && $(MAKE)
```
This should avoid the following warning when running 'make releasecheck'
in some cases:
make[1]: warning: jobserver unavailable: using -j1. Add '+' to parent
make rule.
|
| |
|
|
|
|
|
|
| |
This should make some functions thread-safe, even if it doesn't make
them fully-reentrant; at least some of them would requiree API changes
to full reentrancy.
This should fix #1174.
|
| | |
|
| |
|
|
|
| |
The first 5.x release was 22 years ago, the vendor stopped supporting
this OS 10 years ago.
|
| |
|
|
| |
Digital/Tru64 Unix 4.x releases were made between 1996 and 2000.
|
| |
|
|
|
|
|
|
| |
HP-UX 11.00 was released in 1997; lbl/os-hpux11.h was introduced via
commit 7ec2e59 in 2002. The only prototype in the header is for ffs(),
and HP-UX 11.31 (11i v3), which was released in 2007, has the prototype,
albeit not in the standard header. Remove lbl/os-hpux11.h and update
the lowest_set_bit() block in optimize.c to recognize HP-UX specifics.
|
| |
|
|
|
|
| |
On AIX one of the files "make all" produces is libpcap.shareda, which
then "git status" displays, but "make clean" does not remove. Make this
the opposite way around.
|
| |
|
|
|
|
| |
Same as in tcpslice and tcpdump. So long as the user finds a suitable
implementation of lex and a C99 compiler, libpcap compiles on Solaris 9
regardless of lbl/os-solaris2.h presence.
|
| |
|
|
| |
(same as in tcpslice and tcpdump)
|
| |\
| |
| | |
Remove check for C++ compiler on Haiku
|
| | | |
|
| | | |
|
| |/ |
|
| |
|
|
|
|
|
|
|
| |
AIX 4 was introduced in 1994. AIX 7.1 was introduced in 2010, it has
the ffs() prototype in <strings.h>, and libpcap builds on AIX 7.1 and
7.2 without lbl/os-aix7.h:
checking for ffs... yes
checking whether ffs is declared... yes
|
| | |
|
| | |
|
| | |
|
| |
|
|
|
|
|
| |
It is no longer created since commit
08a58700942f29139998acccb1c6ebb68beabbd9.
[skip ci]
|
| | |
|
| |
|
|
|
|
| |
appveyor]
(same as in tcpdump and tcpslice)
|
| |
|
|
| |
The file does not exist since commit 28e59ef in 2019.
|
| |
|
|
|
| |
This change allows to avoid an error on some OS, e.g. SunOS 5.10, like:
sh: !: not found
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Put autoconf-generated files in the release tarball.
Remove the corresponding task from the TODO file.
The minimum required version of autoconf is currently 2.69.
If version 2.69 or later is already installed and there is no
autoconf default, it may be necessary to set the AUTORECONF
environment variable to enable the one to use, like:
AUTORECONF=autoreconf-2.69 ./autogen.sh
or
AUTORECONF=autoreconf-2.71 ./autogen.sh
|
| |
|
|
|
|
| |
gnuc.h was removed in commit 916c01aa0a177fbdec2ddf32013ccd2155f2c518.
[skip ci]
|
| | |
|
| |
|
|
|
|
| |
config.h.in~
configure~
configure.ac~
|
| | |
|
| | |
|
| |
|
|
|
|
| |
Display errors when there are trailing space(s)/tab(s).
[skip ci]
|
| | |
|
| |
|
|
| |
[skip ci]
|
| |
|
|
|
|
|
|
|
|
|
|
|
| |
This change do, in a fresh directory from a release archive:
1) a "configure --enable-remote" and build,
2) a "cmake -DENABLE_REMOTE=yes" and build.
It may allow to find some necessary files missing in the release archive.
Define CMAKE_MESSAGE_LOG_LEVEL=NOTICE to minimize the cmake output.
Define CMAKE_RULE_MESSAGES=OFF to minimize the make output in cmake case.
[skip ci]
|
| | |
|
| | |
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
These tricky targets used "autoreconf -f" (via "make releasetar") and
they changed the VERSION and configure files locally.
If building a release candidate tar archive is needed, it's better to:
Update VERSION with rcX suffix and configure via "autoreconf -f",
commit them, add a tag and build the archive via "make releasetar".
It should display: Archive build from tag libpcap-...rcX.
Note: the "autoreconf -f" command changes the configure file in an
uncontrolled way (runstatedir, #define LARGE_OFF_T, etc.) depending on
the autoconf version.
It is necessary to choose the parts that will be added in the commit
with "git add -i".
This is a follow-up to 563c8a2caf64dde3818b5483d792561cd5b0b428.
[skip ci]
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Use the release tag if it exists or use HEAD.
Remove the "autoreconf -f" command, because it changes the configure file
locally in an uncontrolled way (runstatedir, #define LARGE_OFF_T, etc.)
depending on the autoconf version. This command is run in the release
process before a commit and we can choose the parts that will be added
in the commit.
Note:
The following target (rcX) must be updated ou removed in a next step
because it was using "autoreconf -f" (via "make releasetar") and it
changes the VERSION and configure files locally.
This change
1) Ensures that we only release files from tag/HEAD, not locally
modified ones.
2) Avoids disclosing personal data such as the username/group of the
local user.
3) Puts by default a umask of 0002, which turns off the world write bit
on files in the archive.
4) Avoids problems on some OSes (no more tar, Git builtin tar.gz
handling).
|
| |
|
|
|
| |
This change avoids listing all tests/* files in EXTRA_DIST.
(Risk of forgetting some...)
|
| |
|
|
|
|
|
|
|
| |
On platforms where a program built with a libpcap installed somewhere
other than the default system library directory must be linked with an
rpath option to cause the program to, when run, find the library with
which it was linked, specify that flag in the output from pcap-config
and the output produced by pkg-config when used with our libpcap.pc
file.
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Stick a byte-order magic number, in the host byte order of the server,
into the authentication reply.
If the authentication reply is large enough to contain that magic
number, extract it and, from it, determine whether the server's byte
order is the opposite of the client's byte order; if it's not present,
assume the server has the same byte order.
If the two byte orders are differen, do the same byte-order fixing of
the packet contents that we do when reading a pcap file or pcapng
section with the opposite byte order, so that host-byte-order fields are
converted from the byte order of the host that sent or wrote them to the
byte order of the host that received or read them.
This change will allow a client to work with all servers, regardless of
whether they provide the byte order or not, although if the server
doesn't provide the byte order, and it happens to be the opposite of the
client's byte order, packets with a link-layer header type that contains
host-byte-order fields will not be able to be processed correctly. It
also allows clients that don't handle the byte order magic number in the
authentication reply to work with all servers, as they will just discard
what they consider extra data at the end of the reply.
(Note: fixing the byte order in the server requires that the client send
a byte order indication to the server, so *either* fix works only
between an updated client and an updated server. We already have
optional data in the authentication reply, to allow updated servers and
clients to negotiate a protocol version while still allowing updated
clients to work with older servers and older clients to work with
updated servers, so this just continues that mechanism.)
|
| |
|
|
| |
As discussed on tcpdump-workers.
|
| |
|
|
|
|
|
|
| |
Correctly compute the "real" length for isochronous transfers.
When reading memory-mapped Linux capture files, fix up the "real" length
field, in case the file was written by a program doing a capture with
the bug.
|
| |
|
|
|
| |
We haven't set EXTRA_NETWORK_LIBS in a while; no reason to keep using
it.
|
