All of lore.kernel.org
 help / color / mirror / Atom feed
From: Thomas Petazzoni <thomas.petazzoni@bootlin.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH v1 1/2] package/snort: needs zlib
Date: Sat, 11 Jan 2020 14:20:56 +0100	[thread overview]
Message-ID: <20200111142056.66ddf3d1@windsurf> (raw)
In-Reply-To: <20200110223837.170e8e3f@gmx.net>

On Fri, 10 Jan 2020 22:38:37 +0100
Peter Seiderer <ps.report@gmx.net> wrote:

> On Fri, 10 Jan 2020 22:07:19 +0100, Thomas Petazzoni <thomas.petazzoni@bootlin.com> wrote:
> 
> > On Fri, 10 Jan 2020 18:28:17 +0100
> > Peter Seiderer <ps.report@gmx.net> wrote:
> >  
> > > Fixes:
> > >
> > >   checking zlib.h usability... no
> > >   checking zlib.h presence... no
> > >   checking for zlib.h... no
> > >
> > >      ERROR!  zlib header not found, go get it from
> > >      http://www.zlib.net
> > >
> > > Signed-off-by: Peter Seiderer <ps.report@gmx.net>  
> >
> > Since when is zlib needed? We've add the snort package for quite some
> > time. Is it due to the bump to 2.9.15 in December ?  
> 
> No, I think it is a side effect of 'package/libpcap: remove unnecessary dependency
> on zlib' ([1]) as snort selects/depends on libpcap...

Ah, yes, indeed.

Thanks,

Thomas
-- 
Thomas Petazzoni, CTO, Bootlin
Embedded Linux and Kernel engineering
https://bootlin.com

  reply	other threads:[~2020-01-11 13:20 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-01-10 17:28 [Buildroot] [PATCH v1 1/2] package/snort: needs zlib Peter Seiderer
2020-01-10 17:28 ` [Buildroot] [PATCH v1 2/2] package/snort: bump version to 2.9.15.1 Peter Seiderer
2020-01-10 21:07 ` [Buildroot] [PATCH v1 1/2] package/snort: needs zlib Thomas Petazzoni
2020-01-10 21:38   ` Peter Seiderer
2020-01-11 13:20     ` Thomas Petazzoni [this message]
2020-01-11 14:52 ` 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=20200111142056.66ddf3d1@windsurf \
    --to=thomas.petazzoni@bootlin.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 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.