Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH 2/2] libpcap: bump to version 1.8.1
Date: Wed, 26 Oct 2016 23:31:36 +0200	[thread overview]
Message-ID: <20161026233136.71e5ba28@free-electrons.com> (raw)
In-Reply-To: <0a7a49e96ee2626cb9d1909826751a50646630b2.1477501390.git.baruch@tkos.co.il>

Hello,

On Wed, 26 Oct 2016 20:03:10 +0300, Baruch Siach wrote:
> Drop upstream patch.
> 
> Also remove ac_cv_linux_vers caching since this check was remove in upstream
> commit f3e011b18c55ae.
> 
> Signed-off-by: Baruch Siach <baruch@tkos.co.il>
> ---
>  ....in-fix-detect-of-if_bonding.h-on-uclinux.patch | 30 ----------------------
>  package/libpcap/libpcap.hash                       |  2 +-
>  package/libpcap/libpcap.mk                         |  5 +---
>  3 files changed, 2 insertions(+), 35 deletions(-)
>  delete mode 100644 package/libpcap/0002-configure.in-fix-detect-of-if_bonding.h-on-uclinux.patch

This bump breaks the build of ngrep, see
http://autobuild.buildroot.net/results/809/80982b07bddb8092accc643f2dc8105cd17ecb37/build-end.log.
I've tested, and indeed after reverting the bump, ngrep builds fine.

Could you have a look?

Thanks!

Thomas
-- 
Thomas Petazzoni, CTO, Free Electrons
Embedded Linux, Kernel and Android engineering
http://free-electrons.com

  reply	other threads:[~2016-10-26 21:31 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-10-26 17:03 [Buildroot] [PATCH 1/2] libpcap: drop libnl headers patch Baruch Siach
2016-10-26 17:03 ` [Buildroot] [PATCH 2/2] libpcap: bump to version 1.8.1 Baruch Siach
2016-10-26 21:31   ` Thomas Petazzoni [this message]
2016-10-27  5:12     ` Baruch Siach
2016-10-26 20:05 ` [Buildroot] [PATCH 1/2] libpcap: drop libnl headers patch Thomas Petazzoni

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=20161026233136.71e5ba28@free-electrons.com \
    --to=thomas.petazzoni@free-electrons.com \
    --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