Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Thomas Petazzoni <thomas.petazzoni@bootlin.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH 1/1] libcurl: fix build with ssh2 and static mbedtls
Date: Tue, 22 May 2018 23:06:37 +0200	[thread overview]
Message-ID: <20180522230637.49906e43@windsurf> (raw)
In-Reply-To: <20180521114108.20916-1-fontaine.fabrice@gmail.com>

Hello,

On Mon, 21 May 2018 13:41:08 +0200, Fabrice Fontaine wrote:
> The ssh2 pkg-config file could contain the following lines when build
> with a static version of mbedtls:
>    Libs: -L${libdir} -lssh2 /xxx/libmbedcrypto.a
>    Libs.private: /xxx/libmbedcrypto.a

I find it weird to have the same library in both Libs and Libs.private.

Either it's a direct dependency of ssh2 and it should be in Libs. Or
it's an indirect dependency of ssh2 and should only be used when static
linking, in which case it should be only in Libs.private.

Section thing that looks weird is: why a full path to libmbedcrypto.a
and not a -l flag ?

> This static mbedtls library must be used to correctly detect ssh2
> support and this library must be copied in libcurl.pc otherwise
> compilation of any application (such as upmpdcli) with libcurl will fail
> when trying to found mbedtls functions included in libssh2.
> So, replace pkg-config --libs-only-l by pkg-config --libs.

That being said, the libcurl change looks good to me. Did you submit it
upstream ?

Thanks,

Thomas
-- 
Thomas Petazzoni, CTO, Bootlin (formerly Free Electrons)
Embedded Linux and Kernel engineering
https://bootlin.com

  reply	other threads:[~2018-05-22 21:06 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-05-21 11:41 [Buildroot] [PATCH 1/1] libcurl: fix build with ssh2 and static mbedtls Fabrice Fontaine
2018-05-22 21:06 ` Thomas Petazzoni [this message]
2018-05-22 21:43   ` Fabrice Fontaine
2018-05-23  6:02     ` Thomas Petazzoni
2018-05-27 21:42 ` Peter Korsgaard
2018-06-17 14:57 ` Peter Korsgaard

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=20180522230637.49906e43@windsurf \
    --to=thomas.petazzoni@bootlin.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