From: Baruch Siach <baruch@tkos.co.il>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH v4] bandwidthd: Version bump to fix autobuilder errors
Date: Thu, 21 Aug 2014 13:55:57 +0300 [thread overview]
Message-ID: <20140821105557.GI2405@tarshish> (raw)
In-Reply-To: <53F5CD25.2030300@gmail.com>
Hi Nathaniel,
On Thu, Aug 21, 2014 at 06:42:45PM +0800, Nathaniel Roach wrote:
> On 21/08/14 18:34, Baruch Siach wrote:
> > On Thu, Aug 21, 2014 at 06:24:55PM +0800, Nathaniel Roach wrote:
> >> Thanks to Romain Naour, we've found that certain tests
> >> in configure fail if their dependencies aren't tested for
> >> beforehand.
> >> depends on BR2_USE_MMU # fork()
> >> + select BR2_PACKAGE_ZLIB
> >
> > Is bandwidthd using libz directly? If not, libpng already selects
> > BR2_PACKAGE_ZLIB so this may not actually be needed?
>
> You are correct, it's only through libpng that zlib is used. I put it in
> there as a safeguard because bandwidthd's configure script does test for
> it's existence, as the libpng tests can fail without first testing for zlib.
>
> The above issue should be covered by libpng anyway. I don't see any harm
> in it being there, but if you think it should be removed I'll undo the
> changes.
I'll let the maintainers make the final decision on that. It just feels wrong
to workaround a libpng issue in a dependent packages. At the very least there
should be a comment here (again) clearly stating that bandwidthd doesn't
actually use libz, and that once the libpng issue is fixed this dependency can
be removed.
baruch
--
http://baruch.siach.name/blog/ ~. .~ Tk Open Systems
=}------------------------------------------------ooO--U--Ooo------------{=
- baruch at tkos.co.il - tel: +972.2.679.5364, http://www.tkos.co.il -
prev parent reply other threads:[~2014-08-21 10:55 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-08-21 10:24 [Buildroot] [PATCH v4] bandwidthd: Version bump to fix autobuilder errors Nathaniel Roach
2014-08-21 10:34 ` Baruch Siach
2014-08-21 10:42 ` Nathaniel Roach
2014-08-21 10:55 ` Baruch Siach [this message]
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=20140821105557.GI2405@tarshish \
--to=baruch@tkos.co.il \
--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