From: Thomas Petazzoni <thomas.petazzoni@bootlin.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH 1/1] lxc: fix build with static libcap and shared gnutls
Date: Thu, 3 May 2018 21:40:24 +0200 [thread overview]
Message-ID: <20180503214024.71d04136@windsurf> (raw)
In-Reply-To: <20180407162234.12848-1-fontaine.fabrice@gmail.com>
Hello Fabrice,
Sorry for the slow feedback on this one.
On Sat, 7 Apr 2018 18:22:34 +0200, Fabrice Fontaine wrote:
> Fixes:
> - http://autobuild.buildroot.net/results/b655d6853c25a195df28d91512b3ffb6c654fc90
>
> Signed-off-by: Fabrice Fontaine <fontaine.fabrice@gmail.com>
So, this happens because when BR2_SHARED_LIBS=y, gnutls installs only a
shared library, while libcap installs both a static library and a
shared library.
But really, the crux of the problem is that LXC shouldn't try to build
a statically linked program when BR2_SHARED_LIBS=y. It doesn't make
sense, because we don't guarantee to provide static libraries when
BR2_SHARED_LIBS=y: some packages do build static libraries
unconditionally, but for examples the autotools packages that obey to
--disable-static will not build/install static libraries when
BR2_SHARED_LIBS=y.
And in fact, I'm wondering how your patch resolves that really. I guess
it disables GnuTLS support in such a situation, but that isn't really
the right fix IMO. I would rather disable the build of the static
version of the LXC program.
Do you think you could have a look into this ?
Thomas
--
Thomas Petazzoni, CTO, Bootlin (formerly Free Electrons)
Embedded Linux and Kernel engineering
https://bootlin.com
next prev parent reply other threads:[~2018-05-03 19:40 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-04-07 16:22 [Buildroot] [PATCH 1/1] lxc: fix build with static libcap and shared gnutls Fabrice Fontaine
2018-05-03 19:40 ` Thomas Petazzoni [this message]
2018-05-03 21:47 ` Fabrice Fontaine
2018-05-07 15:44 ` Thomas Petazzoni
2018-05-07 15:45 ` Thomas Petazzoni
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=20180503214024.71d04136@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