Skip to content

Commit f0e29af

Browse files
committed
autoconf: change the message for failure to link with libpcap.
Such a failure *might* be the result of a bug, but it might also be the result of building against a libpcap library with a different bit width from the one being used for tcpdump, or attempting to do a static build against a libpcap that doesn't support that (because it depends on other libraries, one of which is only available as a dynamic library), etc.. The latter, rather than the former, appears to be the more common case these days.
1 parent 786eaca commit f0e29af

File tree

1 file changed

+15
-10
lines changed

1 file changed

+15
-10
lines changed

aclocal.m4

Lines changed: 15 additions & 10 deletions
Original file line numberDiff line numberDiff line change
@@ -760,16 +760,21 @@ AC_DEFUN(AC_LBL_LIBPCAP,
760760
[
761761
AC_MSG_ERROR(
762762
[
763-
1. Do you try to build a 32-bit tcpdump with a 64-bit libpcap or vice versa?
764-
2. This is a bug, please follow the guidelines in CONTRIBUTING.md and include
765-
the config.log file in your report. If you have downloaded libpcap from
766-
tcpdump.org, and built it yourself, please also include the config.log
767-
file from the libpcap source directory, the Makefile from the libpcap
768-
source directory, and the output of the make process for libpcap, as
769-
this could be a problem with the libpcap that was built, and we will
770-
not be able to determine why this is happening, and thus will not be
771-
able to fix it, without that information, as we have not been able to
772-
reproduce this problem ourselves.])
763+
For some reason, linking with libpcap failed.
764+
765+
This may be a result of the way you have configured the build. For
766+
example, you may have specified a static build with a version of libpcap
767+
that cannot be linked statically, or you may have specified something
768+
that would ause a 32-bit tcpdump to be linked with a 64-bit libpcap or
769+
vice versa.
770+
771+
Please check the config.log file in the build directory. It should have
772+
a line that says "checking for pcap_loop"; following that will be a
773+
command that links a small test program with libpcap, and following that
774+
should be error messages indicating why the attempt to link failed.
775+
776+
Then check the doc/README.{platform}.md file for the platform for which
777+
you're building, to see if it gives any advice.])
773778
])
774779
])
775780

0 commit comments

Comments
 (0)