From: Thomas Petazzoni <thomas.petazzoni@bootlin.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH 1/1] xerces: fix static linking with mbedtls
Date: Sat, 3 Nov 2018 14:48:01 +0100 [thread overview]
Message-ID: <20181103144801.1ac80511@windsurf> (raw)
In-Reply-To: <CAPi7W804TLyLN-sFX5USYT5M9ppY1FuO7nzELzZAYssmM8S5-g@mail.gmail.com>
Hello Fabrice,
On Fri, 2 Nov 2018 23:56:36 +0100, Fabrice Fontaine wrote:
> The fullpath to mbedtls library in libcurl.pc was added by
> https://patchwork.ozlabs.org/patch/917565. This patch was merged
> upstream.
> This fullpath in libssh2.pc was added by
> http://patchwork.ozlabs.org/patch/888395.
> This patch to libssh2 was not yet merged upstream so indeed we could
> find an other solution.
> For example, instead of adding $LIBMBEDCRYPTO (which contains the full
> library path returned by AC_LIB_HAVE_LINKFLAGS) to LIBS, an other
> solution would be to simply add -lmbedcrypto to LIBS.
> If you agree, I can test this proposal and send a new patch to libssh2.
Use LTLIBMBEDCRYPTO instead of LIBMBEDCRYPTO. We had the same problem
in the past, and that's how Romain Naour solved it:
http://lists.busybox.net/pipermail/buildroot/2017-May/192294.html
> > BTW, do you have a minimal defconfig that exhibits this problem?
> Nope, I used the autobuilder defconfig but I think you need
> BR2_PACKAGE_LIBSSH2_MBEDTLS=y to build libssh2 with mbedtls instead of
> openssl.
It was set in my configuration, even if not visible in the minimal
defconfig.
Thanks!
Thomas
--
Thomas Petazzoni, CTO, Bootlin
Embedded Linux and Kernel engineering
https://bootlin.com
prev parent reply other threads:[~2018-11-03 13:48 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-10-25 20:54 [Buildroot] [PATCH 1/1] xerces: fix static linking with mbedtls Fabrice Fontaine
2018-11-02 21:30 ` Thomas Petazzoni
2018-11-02 22:56 ` Fabrice Fontaine
2018-11-03 13:48 ` Thomas Petazzoni [this message]
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=20181103144801.1ac80511@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