From: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH 1/1] libssh2: fix library search path issues when zlib support enabled
Date: Sun, 29 Jun 2014 16:30:16 +0200 [thread overview]
Message-ID: <20140629163016.41256df2@free-electrons.com> (raw)
In-Reply-To: <1403878684-11934-1-git-send-email-acoffignal@geral.com>
Dear Alexandre Coffignal,
On Fri, 27 Jun 2014 16:18:04 +0200, Alexandre Coffignal wrote:
>
> Signed-off-by: Alexandre Coffignal <acoffignal@geral.com>
> ---
> package/libssh2/libssh2.mk | 3 ++-
> 1 file changed, 2 insertions(+), 1 deletion(-)
>
> diff --git a/package/libssh2/libssh2.mk b/package/libssh2/libssh2.mk
> index 19df9af..73aae8e 100644
> --- a/package/libssh2/libssh2.mk
> +++ b/package/libssh2/libssh2.mk
> @@ -28,7 +28,8 @@ endif
> # Add zlib support if enabled
> ifeq ($(BR2_PACKAGE_ZLIB),y)
> LIBSSH2_DEPENDENCIES += zlib
> -LIBSSH2_CONF_OPT += --with-libz
> +LIBSSH2_CONF_OPT += --with-libz \
> + --with-libz-prefix=$(STAGING_DIR)/usr
> else
> LIBSSH2_CONF_OPT += --without-libz
> endif
Thanks for the patch. However, I was not able to reproduce the issue,
be it on a system with zlib-dev installed or not. Can you provide more
details about the issue you're seeing?
Thanks,
Thomas
--
Thomas Petazzoni, CTO, Free Electrons
Embedded Linux, Kernel and Android engineering
http://free-electrons.com
next prev parent reply other threads:[~2014-06-29 14:30 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-06-27 14:18 [Buildroot] [PATCH 1/1] libssh2: fix library search path issues when zlib support enabled Alexandre Coffignal
2014-06-29 14:30 ` Thomas Petazzoni [this message]
2014-06-30 11:43 ` COFFIGNAL Alexandre
2014-06-30 12:02 ` Thomas Petazzoni
2014-06-30 12:33 ` Alexandre COFFIGNAL
2014-07-02 6:18 ` Arnout Vandecappelle
2014-07-02 7:26 ` Thomas Petazzoni
2014-07-02 7:49 ` Arnout Vandecappelle
2014-07-02 7:58 ` Thomas Petazzoni
2014-07-02 8:56 ` Alexandre COFFIGNAL
2014-07-02 7:53 ` Alexandre COFFIGNAL
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=20140629163016.41256df2@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 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.