From: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH 1/2] package/links: add optional support for libevent
Date: Tue, 16 Feb 2016 23:11:04 +0100 [thread overview]
Message-ID: <20160216231104.643353ad@free-electrons.com> (raw)
In-Reply-To: <1455137922-18060-1-git-send-email-bernd.kuhls@t-online.de>
Dear Bernd Kuhls,
On Wed, 10 Feb 2016 21:58:41 +0100, Bernd Kuhls wrote:
> When libevent was compiled before, links will use it as optional
> dependency:
>
> $ output/host/usr/bin/i586-buildroot-linux-uclibc-readelf -a output/target/usr/bin/links | grep NEEDED
> 0x00000001 (NEEDED) Shared library: [liblzma.so.5]
> 0x00000001 (NEEDED) Shared library: [libbz2.so.1.0]
> 0x00000001 (NEEDED) Shared library: [libz.so.1]
> 0x00000001 (NEEDED) Shared library: [libevent-2.0.so.5]
> 0x00000001 (NEEDED) Shared library: [libc.so.1]
>
> (xz support will be added with the next patch of this series)
>
> Signed-off-by: Bernd Kuhls <bernd.kuhls@t-online.de>
> ---
> package/links/links.mk | 4 ++++
> 1 file changed, 4 insertions(+)
I've applied both patches to master. However, could you send another
patch that forces --with-<foo>/--without-<foo> ? Since we were not
doing that for other dependencies, I applied your patches as-is, but I
would like to see those options added explicitly.
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:11 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-02-10 20:58 [Buildroot] [PATCH 1/2] package/links: add optional support for libevent Bernd Kuhls
2016-02-10 20:58 ` [Buildroot] [PATCH 2/2] package/links: add optional support for xz Bernd Kuhls
2016-02-16 22:11 ` Thomas Petazzoni [this message]
2016-02-20 14:21 ` [Buildroot] [PATCH 1/2] package/links: add optional support for libevent Bernd Kuhls
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=20160216231104.643353ad@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