Date: Sun, 2 Sep 2012 18:57:00 +0200 From: Kurt Jaeger <pi@opsec.eu> To: bug-followup@FreeBSD.org, peterjeremy@optushome.com.au Cc: freebsd-net@freebsd.org Subject: Re: ports/124825: tcpdump/print-pfsync feature request submitted to tcpdump on sourceforge Message-ID: <20120902165700.GA21474@home.opsec.eu> In-Reply-To: <20111230192212.GJ52832@home.opsec.eu> References: <20111230192212.GJ52832@home.opsec.eu>
next in thread | previous in thread | raw e-mail | index | archive | help
Hi! > I added some pointer to your PR at: > > https://sourceforge.net/tracker/?func=detail&atid=469576&aid=3467532&group_id=53066 The answer to that pointer was from http://sourceforge.net/users/guy_harris/ -------- I, at least, have no plan to include anything that requires that, in order to build tcpdump, a -I flag that points to a header file that's internal to some project's source tree rather than being installed under /usr/include. Unfortunately, both packet-pfsync.c and pf_print_state.c, in both that patch and in OpenBSD, will build only if the include path includes the source directory for the pfctl command, so I'm not going to do any more work on this until at least one OS makes all the required include files public headers installed in /usr/include or a directory under that. -------- So, if /usr/src/sbin/pfctl/Makefile would install pfctl.h and pfctl_parser.h into /usr/include/net, the tcpdump people would include print-pfsync.c. Any chance for this ? -- pi@opsec.eu +49 171 3101372 8 years to go !
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20120902165700.GA21474>