Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Arnout Vandecappelle <arnout@mind.be>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH] gnutls: Fix search path for libgcrypt
Date: Tue, 15 May 2012 08:27:43 +0200	[thread overview]
Message-ID: <4FB1F75F.5050100@mind.be> (raw)
In-Reply-To: <87d3661soa.fsf@macbook.be.48ers.dk>

On 05/14/12 21:14, Peter Korsgaard wrote:
>>>>>> "Arnout" == Arnout Vandecappelle<arnout@mind.be>  writes:
>
> Hi,
>
>   Arnout>   This is BTW from one of the broken configs reported in the
>   Arnout>  autobuild, from which I also had to remove some more broken
>   Arnout>  packages (ltp-testsuite, ndisc6).  It's a generic powerpc internal
>   Arnout>  toolchain.
>
> ltp-testsuite is known to be broken with the default uClibc config, but
> I wasn't aware of any ndisc6 issues. What exactly goes wrong?

   It's a gettext issue. I haven't looked at it because I was fixing something else,
and because gettext anyway had patches pending.

  There are plenty of failures in autobuild, e.g.
http://autobuild.buildroot.net/results/1405f403f53624667c3d104a4e8f0c070501a639/

  Regards,
  Arnout
-- 
Arnout Vandecappelle                               arnout at mind be
Senior Embedded Software Architect                 +32-16-286540
Essensium/Mind                                     http://www.mind.be
G.Geenslaan 9, 3001 Leuven, Belgium                BE 872 984 063 RPR Leuven
LinkedIn profile: http://www.linkedin.com/in/arnoutvandecappelle
GPG fingerprint:  7CB5 E4CC 6C2E EFD4 6E3D A754 F963 ECAB 2450 2F1F

  reply	other threads:[~2012-05-15  6:27 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
2012-05-14 19:14     ` Peter Korsgaard
2012-05-15  6:27       ` Arnout Vandecappelle [this message]
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=4FB1F75F.5050100@mind.be \
    --to=arnout@mind.be \
    --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