All of 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: Wed, 23 May 2018 08:02:53 +0200	[thread overview]
Message-ID: <20180523080253.06426712@windsurf> (raw)
In-Reply-To: <CAPi7W82RE+8-7eLJJ7vu4vsBfOxBHrBWrz0v3ZZG3gt+1XG+fA@mail.gmail.com>

Hello,

On Tue, 22 May 2018 23:43:00 +0200, Fabrice Fontaine wrote:

> > 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 ?
> >  
> Indeed, this seems pretty weird to me too.
> This patch to libssh2 was added recently to buildroot (see
> http://patchwork.ozlabs.org/patch/888395) by Baruch (now in cc).
> It seems that this full path is returned by the AC_LIB_HAVE_LINKFLAGS
> function, see https://github.com/libssh2/libssh2/blob/master/acinclude.m4.
> So, perhaps we could find a better patch for libssh2 instead of patching
> libcurl.

Indeed the resulting .pc file from libssh2 looks strange. But however,
I think your change to libcurl remains valid. 'pkg-config --libs' is
what should be used to get the linker flags. I don't see why libcurl
should filter the options and only keep the -l options. Other linker
options may be important.

Best regards,

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

  reply	other threads:[~2018-05-23  6:02 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
2018-05-22 21:43   ` Fabrice Fontaine
2018-05-23  6:02     ` Thomas Petazzoni [this message]
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=20180523080253.06426712@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 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.