From Bugzilla Helper: User-Agent: Mozilla/4.0 (compatible; MSIE 6.0; Windows NT 5.1) Description of problem: 1/ bugzilla doesn't allow to post bugs about libpcap (not in the list) 2/ <pcap/pcap.h> has a bad #include statement Version-Release number of selected component (if applicable): How reproducible: Always Steps to Reproduce: #include <pcap/pcap.h> gcc -lpcap bla.c Additional info: 1/ Problem with bugzilla: There's no libpcap entry available in "RedHat Linux" selection to post bugs about it *** This is not a bug about libcap but about libpcap 2/ Bug in /usr/include/pcap/pcap.h (from libpcap package): it says #include <net/bpf.h> but there's no <net/bpf.h> (/usr/include/net/bpf.h). In fact it should say #include <pcap/net/bpf.h> because the file really is /usr/include/pcap/net/bpf.h This prevents from using lib pcap in C programs.
# rpm -q --qf "%{SOURCERPM}" libpcap tcpdump-3.6.2-12.src.rpm -----> Not a bugzilla bug, libpcap is tcpdump
hmmm... temporal workaround -I /usr/include/pcap
Created attachment 63184 [details] spec file patch for include path to use /usr/include isntead of /usr/include/pcap
Why is are the libpcap header files installed under /usr/include/pcap/ instead of just /usr/include/ which seems to match expectations. pcap.h itself seems to expect this layout and there are plenty of messages on mailing lists saying "to get this to compile on redhat do..." relating to this. FWIW I use the attached spec file patch to make things behave as expect (by me at least) on my systems...
Spec file patch was applied for tcpdump-3.6.3-17.7.3.2. Closing ERRATA.