From: Thomas Petazzoni <thomas.petazzoni@bootlin.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH 1/1] package/lxc: switch from gnutls to openssl
Date: Sat, 27 Jul 2019 22:42:46 +0200 [thread overview]
Message-ID: <20190727224246.75bd967e@windsurf> (raw)
In-Reply-To: <20190705165040.26254-1-fontaine.fabrice@gmail.com>
Hello Fabrice,
On Fri, 5 Jul 2019 18:50:40 +0200
Fabrice Fontaine <fontaine.fabrice@gmail.com> wrote:
> Fixes:
> - http://autobuild.buildroot.org/results/c0a9565ae65336d55cdedc67adff221a7fa1a2c8
>
> Signed-off-by: Fabrice Fontaine <fontaine.fabrice@gmail.com>
Thanks, but this is not entirely convincing, for two reasons:
- The actual build failure is due to libgnutls.so using __atomic
built-ins, without being linked to libatomic.so. This is a problem
that can affect any other package that uses libgnutls.so (and a
question is why we're not seeing more failures like this, from other
packages that use libgnutls).
- Switching to openssl is certainly OK, but the lxc configure.ac logic
does just OPENSSL_LIBS='-lssl -lcrypto', which is pretty much
guaranteed to fail in static linking scenarios, as it doesn't
account for second-order dependencies of openssl (the classic -lz
missing).
Could you have a look at the libgnutls.so/libatomic.so issue, and
double check if lxc/openssl builds fine in a static linking
configuration ? For the latter, it is possible that lxc already depends
on libz for another reason, in which case the problem will not be
visible.
Thanks!
Thomas
--
Thomas Petazzoni, CTO, Bootlin
Embedded Linux and Kernel engineering
https://bootlin.com
next prev parent reply other threads:[~2019-07-27 20:42 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-07-05 16:50 [Buildroot] [PATCH 1/1] package/lxc: switch from gnutls to openssl Fabrice Fontaine
2019-07-27 20:42 ` Thomas Petazzoni [this message]
2019-07-28 9:32 ` Yann E. MORIN
2019-07-28 21:20 ` Fabrice Fontaine
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=20190727224246.75bd967e@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