From: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH v2] gnupg2: fix linking with intl
Date: Wed, 17 Dec 2014 09:57:37 +0100 [thread overview]
Message-ID: <20141217095737.564714af@free-electrons.com> (raw)
In-Reply-To: <548B0998.5000001@imgtec.com>
Dear Vicente Olivert Riera,
On Fri, 12 Dec 2014 15:28:24 +0000, Vicente Olivert Riera wrote:
> On 12/11/2014 06:53 PM, Thomas Petazzoni wrote:
> > Dear Vicente Olivert Riera,
> >
> > On Thu, 11 Dec 2014 12:06:51 +0000, Vicente Olivert Riera wrote:
> >
> >> +ifeq ($(BR2_PACKAGE_GETTEXT),y)
> >> +GNUPG2_DEPENDENCIES += gettext
> >> +GNUPG2_CONF_ENV += LIBS=-lintl
> >
> > Are you sure we need this LIBS part when glibc is used?
>
> Uhm..., something must have changed in the tree and right now I'm not
> able to reproduce this failure even using the same config file :/
>
> http://autobuild.buildroot.net/results/9aa/9aaca74dd3a1f82e12358530db4d5d17eb833f7f/config
This problem was related to static linking, but the
BR2_PREFER_STATIC_LIB option has been renamed to BR2_STATIC_LIBS (with
a bogus Config.in.legacy handling done by me). So if you took the old
config file, BR2_PREFER_STATIC_LIB was discarded, and you were doing a
shared library build instead of a static library build, which explains
why the problem was not appearing anymore.
Best regards,
Thomas
--
Thomas Petazzoni, CTO, Free Electrons
Embedded Linux, Kernel and Android engineering
http://free-electrons.com
next prev parent reply other threads:[~2014-12-17 8:57 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-12-11 12:06 [Buildroot] [PATCH v2] gnupg2: fix linking with intl Vicente Olivert Riera
2014-12-11 18:53 ` Thomas Petazzoni
2014-12-12 15:28 ` Vicente Olivert Riera
2014-12-17 8:57 ` Thomas Petazzoni [this message]
2015-01-05 14:04 ` Vicente Olivert Riera
2015-01-05 15:37 ` Thomas Petazzoni
2015-01-05 16:12 ` Vicente Olivert Riera
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=20141217095737.564714af@free-electrons.com \
--to=thomas.petazzoni@free-electrons.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