From: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH] gnutls: Fix search path for libgcrypt
Date: Sun, 13 May 2012 09:02:16 +0200 [thread overview]
Message-ID: <20120513090216.215c50bb@skate> (raw)
In-Reply-To: <4FAEC2F4.1060802@mind.be>
Le Sat, 12 May 2012 22:07:16 +0200,
Arnout Vandecappelle <arnout@mind.be> a ?crit :
> > Last WE, I started investigating the problem, and found out that just
> > compiling gnutls wasn't enough to reproduce the problem. The problem
> > was starting to occur when libintl was built before libgcrypt. In this
> > case, libgcrypt.la had -lintl in its dependencies, and in turn,
> > libintl.la had -lc in its dependencies. Then, libtool expands this -lc
> > into the full path to libc.so.
> After the patch, that doesn't seem to make a difference for me.
> I did the following after a successful build:
> make libgcrypt-dirclean gnutls-dirclean; make
>
> That succeeded. Then I did
> rm -f {staging,target}/{usr/,}lib/*intl*
> rm -rf build/gettext*
> make libgpg-error-dirclean libgcrypt-dirclean gnutls-dirclean
> make gnutls; make
>
> That still succeeded. (It looks like libgpg-error is missing a
> dependency on gettext/libintl, though.) And finally, just to
> be sure:
> rm -f {staging,target}/{usr/,}lib/*intl*
> rm -rf build/gettext*
> make libgpg-error-dirclean libgcrypt-dirclean gnutls-dirclean
> make libintl; make
>
> Also succeeded. That pretty much covers the libintl dependency,
> right?
It should yes. I will test your patch and see if it improves the
situation.
> A heavy-handed approach would be to generate the patched
> binutils for known-to-be-faulty external toolchains.
>
> A simple approach would be to use the patched binutils on the test
> machines :-)
None of these approaches are really easy to do, unfortunately :-(
> BTW, how come this problem doesn't manifest itself more often?
> There are many packages with -lintl in their .la dependencies, so all
> of them should fail regularly, no?
That's a good question indeed.
Thomas
--
Thomas Petazzoni, Free Electrons
Kernel, drivers, real-time and embedded Linux
development, consulting, training and support.
http://free-electrons.com
next prev parent reply other threads:[~2012-05-13 7:02 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-05-12 18:27 [Buildroot] [PATCH] gnutls: Fix search path for libgcrypt Arnout Vandecappelle
2012-05-12 19:07 ` Thomas Petazzoni
2012-05-12 20:07 ` Arnout Vandecappelle
2012-05-13 7:02 ` Thomas Petazzoni [this message]
2012-05-14 19:14 ` Peter Korsgaard
2012-05-15 6:27 ` Arnout Vandecappelle
2012-05-15 7:44 ` 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=20120513090216.215c50bb@skate \
--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