From: Gustavo Zacarias <gustavo@zacarias.com.ar>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH 1/2] libpcap: bump to version 1.7.2
Date: Wed, 11 Mar 2015 12:43:49 -0300 [thread overview]
Message-ID: <550062B5.2080000@zacarias.com.ar> (raw)
In-Reply-To: <20150311143450.GG2177@tarshish>
On 03/11/2015 11:34 AM, Baruch Siach wrote:
> Hi Gustavo,
>
> That's disappointing. Upstream actually merged this patch (commit
> 157330dcac5), but another commit (ee3296275f) broke it in another way. Is it
> possible to pass --with-libnl=/dev/null so that ${incdir} and ${libnldir}
> point to a non-existing place? That should allow removing this patch.
Hi Baruch.
I did find it odd as well, in fact missing CVE patches in the release
made me twitch a little as well.
I'll give it a shot.
Regards.
next prev parent reply other threads:[~2015-03-11 15:43 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-03-11 13:43 [Buildroot] [PATCH 1/2] libpcap: bump to version 1.7.2 Gustavo Zacarias
2015-03-11 13:43 ` [Buildroot] [PATCH 2/2] tcpdump: security bump to version 4.7.3 Gustavo Zacarias
2015-03-11 16:09 ` Peter Korsgaard
2015-03-11 14:34 ` [Buildroot] [PATCH 1/2] libpcap: bump to version 1.7.2 Baruch Siach
2015-03-11 15:43 ` Gustavo Zacarias [this message]
2015-03-11 16:34 ` Gustavo Zacarias
2015-03-11 16:39 ` Peter Korsgaard
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=550062B5.2080000@zacarias.com.ar \
--to=gustavo@zacarias.com.ar \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox