Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Peter Korsgaard <jacmet@uclibc.org>
To: buildroot@busybox.net
Subject: [Buildroot] [autobuild.buildroot.net] Build results for 2012-12-29
Date: Sun, 30 Dec 2012 14:08:40 +0100	[thread overview]
Message-ID: <87ehi7u1pj.fsf@dell.be.48ers.dk> (raw)
In-Reply-To: <50E02D8F.7020504@zacarias.com.ar> (Gustavo Zacarias's message of "Sun, 30 Dec 2012 09:03:27 -0300")

>>>>> "Gustavo" == Gustavo Zacarias <gustavo@zacarias.com.ar> writes:

Hi,

 Gustavo> On 12/30/2012 07:02 AM, Peter Korsgaard wrote:
 >> These two looks related to your recent gnutls version bump. Care to have
 >> a look?

 Gustavo> Running a failing config now, i don't think i'll hit it
 Gustavo> barebones though since they look like a pretty regular config.
 Gustavo> Probably have to debootstrap.

Thanks.

 >> This is probably also related to it, but perhaps that gets fixed by
 >> Thomas' e17 update.

 Gustavo> Seems unlikely from looking at the source of ecore.
 Gustavo> Since people have been using and accustomed to gnutls-2.x
 Gustavo> which required libgcrypt they've been including it blindly.
 Gustavo> I'll test to see if it really requires libgcrypt (like
 Gustavo> ntfs-3g) or it's just probably following old gnutls
 Gustavo> instructions and fix accordingly.

Great, thanks.

 >> Did you have a look at the host-gawk issue?

 Gustavo> Yes, it seems peko-specific so my hunch says it's a distro
 Gustavo> toolchain thing. I've asked Thomas and it seems it's runnig
 Gustavo> gcc 4.3.2.  Looks like the new gawk DFA is triggering a bug or
 Gustavo> using a newer feature that it shouldn't.  Couldn't reproduce
 Gustavo> yet, so an old gentoo stage or debootstrap might help me.  So
 Gustavo> also looking into it.  A puny dual-core won't help me with
 Gustavo> getting these things solved quickly though, except libecore :)

You can always request a login to the GCC compile farm if you want to
check on gcc14:

http://gcc.gnu.org/wiki/CompileFarm

-- 
Bye, Peter Korsgaard

      reply	other threads:[~2012-12-30 13:08 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-12-30  7:34 [Buildroot] [autobuild.buildroot.net] Build results for 2012-12-29 Thomas Petazzoni
2012-12-30 10:02 ` Peter Korsgaard
2012-12-30 12:03   ` Gustavo Zacarias
2012-12-30 13:08     ` Peter Korsgaard [this message]

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=87ehi7u1pj.fsf@dell.be.48ers.dk \
    --to=jacmet@uclibc.org \
    --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