From: Alexander Aring <alex.aring@gmail.com>
To: ptxdist@pengutronix.de
Subject: Re: [ptxdist] [PATCH] libpcap: version bump to 1.4.0
Date: Mon, 27 Jan 2014 08:41:48 +0100 [thread overview]
Message-ID: <20140127074147.GA20893@omega> (raw)
In-Reply-To: <20130603115740.GF1939@pengutronix.de>
On Mon, Jun 03, 2013 at 01:57:40PM +0200, Michael Olbrich wrote:
> On Fri, May 31, 2013 at 06:18:21PM +0200, Alexander Aring wrote:
> > Bump libpcap version to 1.4.0.
> >
> > Changes:
> > - Add --enable-bluetooth configure parameter only if LIBPCAP_BLUETOOTH
> > is set.
> > - Add --disable-universal to disable build for Mac OS.
> > - Add --enable-shared to build shared library.
> >
> > Both are default parameter but we avoid a change of default behaviour
> > here.
> >
> > Remove patch 0001-add-CFLAGS-CPPFLAGS-and-LDFLAGS-to-Makefile.in.patch:
> > - This patch is already mainline see:
> > https://github.com/the-tcpdump-group/libpcap/commit/3a089e628c2ef39efdb64c53a7566052917ae974
> >
> > Update other patches to current version and put a signed-off by me in
> > the commit message.
> >
> > Change 0002-pcap-config-add-SYSROOT-support.patch patch to add SYSROOT
> > dir only in includedir and libdir variable, so it's easier to maintain.
> >
>
> I think this patch can be avoided by setting
> *_MAKE_OPT and *_INSTALL_OPT, right?
>
> I'll test this after the release as well.
>
ping here too. Should test the avoid of this patch and resend this patch
with wireshark on top?
With an old libpcap version, wireshark displays that I am using a known broken
protocol and I don't know what happens there when I take a capture it.
- Alex
--
ptxdist mailing list
ptxdist@pengutronix.de
next prev parent reply other threads:[~2014-01-27 7:42 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-05-31 16:18 Alexander Aring
2013-06-03 11:57 ` Michael Olbrich
2014-01-27 7:41 ` Alexander Aring [this message]
2014-01-30 9:01 ` Michael Olbrich
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=20140127074147.GA20893@omega \
--to=alex.aring@gmail.com \
--cc=ptxdist@pengutronix.de \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox