From: "Jörg Krause" <joerg.krause@embedded.rocks>
To: buildroot@busybox.net
Subject: [Buildroot] [autobuild.buildroot.net] Build results for 2016-03-21
Date: Tue, 22 Mar 2016 22:15:14 +0100 [thread overview]
Message-ID: <1458681314.1990.22.camel@embedded.rocks> (raw)
In-Reply-To: <20160322073023.CC980102FD4@stock.ovh.net>
On Di, 2016-03-22 at 08:30 +0100, Thomas Petazzoni wrote:
> Build statistics for 2016-03-21
> ===============================
>
> ?????????arm |??????????????ipsec-tools-0.8.2 | NOK |
> http://autobuild.buildroot.net/results/9f1a08dbb14f74c3dcb2b8868383a9
> a7ebb725f4/
musl build issues. I am working on this to get a solution accepted by
upstream.
Best regards
J?rg Krause
prev parent reply other threads:[~2016-03-22 21:15 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-03-22 7:30 [Buildroot] [autobuild.buildroot.net] Build results for 2016-03-21 Thomas Petazzoni
2016-03-22 17:38 ` François Perrad
2016-03-22 20:59 ` Romain Naour
2016-03-22 21:15 ` Jörg Krause [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=1458681314.1990.22.camel@embedded.rocks \
--to=joerg.krause@embedded.rocks \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.