From: bugzilla at busybox.net <bugzilla@busybox.net>
To: buildroot@busybox.net
Subject: [Buildroot] [Bug 7370] New: ngrep - requires --with-pcap-includes fully defined to find bpf.h
Date: Mon, 8 Sep 2014 18:49:42 +0000 (UTC) [thread overview]
Message-ID: <bug-7370-163@https.bugs.busybox.net/> (raw)
https://bugs.busybox.net/show_bug.cgi?id=7370
Summary: ngrep - requires --with-pcap-includes fully defined to
find bpf.h
Product: buildroot
Version: unspecified
Platform: Other
OS/Version: Linux
Status: NEW
Severity: normal
Priority: P5
Component: Other
AssignedTo: unassigned at buildroot.uclibc.org
ReportedBy: lonnie at abelbeck.com
CC: buildroot at uclibc.org
Estimated Hours: 0.0
For the ngrep package, with the following change:
--
- --with-pcap-includes=$(STAGING_DIR)/usr/include \
+ --with-pcap-includes=$(STAGING_DIR)/usr/include/pcap \
--
The bpf.h include file is now properly found, such that the following are
defined in config.h:
--
#define HAVE_DLT_RAW 1
#define HAVE_DLT_LOOP 1
#define HAVE_DLT_LINUX_SLL 1
#define HAVE_DLT_IEEE802_11 1
#define HAVE_DLT_IEEE802_11_RADIO 1
--
One benefit is that "ngrep -d any" now works since HAVE_DLT_LINUX_SLL is
defined.
--
Configure bugmail: https://bugs.busybox.net/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are on the CC list for the bug.
next reply other threads:[~2014-09-08 18:49 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-09-08 18:49 bugzilla at busybox.net [this message]
2014-09-08 18:55 ` [Buildroot] [Bug 7370] ngrep - requires --with-pcap-includes fully defined to find bpf.h bugzilla at busybox.net
2014-10-22 10:35 ` bugzilla at busybox.net
2014-10-22 20:49 ` bugzilla at busybox.net
2014-10-23 5:56 ` bugzilla at busybox.net
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=bug-7370-163@https.bugs.busybox.net/ \
--to=bugzilla@busybox.net \
--cc=buildroot@busybox.net \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.