From: Gustavo Zacarias <gustavo@zacarias.com.ar>
To: buildroot@busybox.net
Subject: [Buildroot] [autobuild.buildroot.net] Build results for 2012-12-29
Date: Sun, 30 Dec 2012 09:03:27 -0300 [thread overview]
Message-ID: <50E02D8F.7020504@zacarias.com.ar> (raw)
In-Reply-To: <87r4m7uacj.fsf@dell.be.48ers.dk>
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?
Running a failing config now, i don't think i'll hit it barebones though
since they look like a pretty regular config.
Probably have to debootstrap.
> This is probably also related to it, but perhaps that gets fixed by
> Thomas' e17 update.
Seems unlikely from looking at the source of ecore.
Since people have been using and accustomed to gnutls-2.x which required
libgcrypt they've been including it blindly.
I'll test to see if it really requires libgcrypt (like ntfs-3g) or it's
just probably following old gnutls instructions and fix accordingly.
> Did you have a look at the host-gawk issue?
Yes, it seems peko-specific so my hunch says it's a distro toolchain
thing. I've asked Thomas and it seems it's runnig gcc 4.3.2.
Looks like the new gawk DFA is triggering a bug or using a newer feature
that it shouldn't.
Couldn't reproduce yet, so an old gentoo stage or debootstrap might help me.
So also looking into it.
A puny dual-core won't help me with getting these things solved quickly
though, except libecore :)
Regards.
next prev parent reply other threads:[~2012-12-30 12:03 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 [this message]
2012-12-30 13:08 ` 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=50E02D8F.7020504@zacarias.com.ar \
--to=gustavo@zacarias.com.ar \
--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