From: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH 1/1] package/tiff: add optional support for xz
Date: Tue, 16 Feb 2016 23:16:15 +0100 [thread overview]
Message-ID: <20160216231615.6a10fa95@free-electrons.com> (raw)
In-Reply-To: <1455137950-18164-3-git-send-email-bernd.kuhls@t-online.de>
Dear Bernd Kuhls,
On Wed, 10 Feb 2016 21:59:10 +0100, Bernd Kuhls wrote:
> When xz was compiled before, tiff will use it as optional dependency:
>
> $ output/host/usr/bin/i586-buildroot-linux-uclibc-readelf -a output/target/usr/lib/libtiff.so.5.2.4 | grep NEEDED
> 0x00000001 (NEEDED) Shared library: [liblzma.so.5]
> 0x00000001 (NEEDED) Shared library: [libjpeg.so.9]
> 0x00000001 (NEEDED) Shared library: [libz.so.1]
> 0x00000001 (NEEDED) Shared library: [libm.so.1]
> 0x00000001 (NEEDED) Shared library: [libc.so.1]
>
> Signed-off-by: Bernd Kuhls <bernd.kuhls@t-online.de>
> ---
> package/tiff/Config.in | 4 ++++
> package/tiff/tiff.mk | 6 ++++++
> 2 files changed, 10 insertions(+)
I've applied, but I would *really* like to see additional patches to
use --enable-<foo> explicitly for all dependencies of the tiff package.
Thanks!
Thomas
--
Thomas Petazzoni, CTO, Free Electrons
Embedded Linux, Kernel and Android engineering
http://free-electrons.com
next prev parent reply other threads:[~2016-02-16 22:16 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-02-10 20:59 [Buildroot] [PATCH 1/1] package/gdb: add optional support for xz Bernd Kuhls
2016-02-10 20:59 ` [Buildroot] [PATCH 1/1] package/libarchive: add optional support for bzip2 Bernd Kuhls
2016-02-10 21:19 ` Arnout Vandecappelle
2016-02-16 22:15 ` Thomas Petazzoni
2016-02-20 13:49 ` Bernd Kuhls
2016-02-20 23:45 ` Arnout Vandecappelle
2016-02-10 20:59 ` [Buildroot] [PATCH 1/1] package/tiff: add optional support for xz Bernd Kuhls
2016-02-16 22:16 ` Thomas Petazzoni [this message]
2016-02-10 21:14 ` [Buildroot] [PATCH 1/1] package/gdb: " Arnout Vandecappelle
2016-02-10 21:34 ` Bernd Kuhls
2016-02-16 22:19 ` Peter Korsgaard
2016-02-10 21:23 ` Arnout Vandecappelle
2016-02-10 23:04 ` Thomas Petazzoni
2016-02-16 22:14 ` 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=20160216231615.6a10fa95@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