From: Vicente Olivert Riera <Vincent.Riera@imgtec.com>
To: buildroot@busybox.net
Subject: [Buildroot] [autobuild.buildroot.net] Build results for 2014-09-20
Date: Mon, 22 Sep 2014 10:29:26 +0100 [thread overview]
Message-ID: <541FEBF6.2020500@imgtec.com> (raw)
In-Reply-To: <20140921063014.4E0101017F9@stock.ovh.net>
On 09/21/2014 07:30 AM, Thomas Petazzoni wrote:
> Build statistics for 2014-09-20
> ===============================
> mips | snappy-1ff9be9b8fafc8528ca9... | NOK | http://autobuild.buildroot.net/results/d1ec8de2950b9e4ae99e103fc012c9066d83c7a7/
Not a mips specific issue. It also fails on other architectures, like
x86_64 for instance.
It seems to be a problem with the autotools:
https://code.google.com/p/snappy/issues/detail?id=43
and
https://code.google.com/p/snappy/issues/detail?id=67
--
Vincent
prev parent reply other threads:[~2014-09-22 9:29 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-09-21 6:30 [Buildroot] [autobuild.buildroot.net] Build results for 2014-09-20 Thomas Petazzoni
2014-09-22 9:29 ` Vicente Olivert Riera [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=541FEBF6.2020500@imgtec.com \
--to=vincent.riera@imgtec.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