From: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH v2 1/1] zlib-ng: new package
Date: Sat, 25 Nov 2017 13:31:40 +0100 [thread overview]
Message-ID: <20171125133140.68d1bd5a@windsurf.lan> (raw)
In-Reply-To: <1509858069-12976-1-git-send-email-stefan.froberg@petroprogram.com>
Hello,
On Sun, 5 Nov 2017 05:01:09 +0000, Stefan Fr?berg wrote:
> package/Config.in | 1 +
> package/zlib-ng/Config.in | 7 +++++++
> package/zlib-ng/zlib-ng.hash | 10 ++++++++++
> package/zlib-ng/zlib-ng.mk | 13 +++++++++++++
> 4 files changed, 31 insertions(+)
You forgot to update the DEVELOPERS file.
However, there is a bigger problem: zlib-ng overwrites zlib. I.e, both
install the same libz.so and libz.so.1 libraries.
So installing both packages at the same time does not make sense. So,
we need to do something like jpeg/libjpeg/jpeg-turbo.
Could you look into doing this ?
Thanks!
Thomas
--
Thomas Petazzoni, CTO, Free Electrons
Embedded Linux and Kernel engineering
http://free-electrons.com
next prev parent reply other threads:[~2017-11-25 12:31 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-11-05 5:01 [Buildroot] [PATCH v2 1/1] zlib-ng: new package Stefan Fröberg
2017-11-25 12:31 ` Thomas Petazzoni [this message]
2017-11-26 19:32 ` Stefan Fröberg
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=20171125133140.68d1bd5a@windsurf.lan \
--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