From: Yann E. MORIN <yann.morin.1998@free.fr>
To: buildroot@busybox.net
Subject: [Buildroot] Analysis of build results for 2016-08-09
Date: Wed, 17 Aug 2016 11:20:09 +0200 [thread overview]
Message-ID: <20160817092009.GA5778@free.fr> (raw)
In-Reply-To: <CAFt09wOGVX9rhSgw_5MAvcEj07Vja5F79BkGbBf+UhfZC3GcpQ@mail.gmail.com>
Matthew, J?rg, All,
On 2016-08-16 21:27 -0500, Matthew Weber spake thusly:
> On Fri, Aug 12, 2016 at 4:31 AM, J?rg Krause
> <joerg.krause@embedded.rocks> wrote:
> > Am 10. August 2016 16:14:55 MESZ, schrieb Thomas Petazzoni <thomas.petazzoni@free-electrons.com>:
> >>Please find below the usual analysis of build failures. Hiroshi,
> >>Waldemar, Gustavo, Fabrice, Yann, Dagg, J?rg, Vivien, Vicente, Samuel,
> >>Peter, Joris, Alistair, please have a look below, there's some fun
> >>stuff for you! :-) Thanks for your help.
> >>
> >>Thomas
> >>
> >>On Wed, 10 Aug 2016 08:30:29 +0200 (CEST), Thomas Petazzoni wrote:
> >>
> >>> x86_64 | libtirpc-1.0.1 | NOK |
> >>http://autobuild.buildroot.net/results/715c3ff13844a030767a49731069183aa02cc5f2/
> >>
> >>config.status: error: cannot find input file: `rpcgen/Makefile.in'
> >>
> >>J?rg, you've done quite some work on libtirpc, could you have a look at
> >>this issue?
> >
> > I am on vacation until the end of next week. Sorry, someone else maybe?
>
> Took a look at this and it doesn't seem to be consistently repeatable
> ( I have yet to see it fail). I went back and it looks like this
> occasionally has popped up starting on 8/6 and 8/9 on the following
> architectures.
>
> mips - glibc, gcc5, linux headers 4.6
>
> x86_64 - musl, gcc4.9, linux headers 4.7
>
> I just kicked off builds again to repeat both failures. Hopefully I
> can catch it soon!
These two build failures occured on Andre's machine when it started
acting silly (the machine, not Andre! ;-) ).
The failures did not occur on other machines, and Andre's ainstance has
been restarted and does not seem be be acting weird any;ore.
So I'd say we should not investigate those two.
Regards,
Yann E. MORIN.
--
.-----------------.--------------------.------------------.--------------------.
| Yann E. MORIN | Real-Time Embedded | /"\ ASCII RIBBON | Erics' conspiracy: |
| +33 662 376 056 | Software Designer | \ / CAMPAIGN | ___ |
| +33 223 225 172 `------------.-------: X AGAINST | \e/ There is no |
| http://ymorin.is-a-geek.org/ | _/*\_ | / \ HTML MAIL | v conspiracy. |
'------------------------------^-------^------------------^--------------------'
next prev parent reply other threads:[~2016-08-17 9:20 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-08-10 6:30 [Buildroot] [autobuild.buildroot.net] Build results for 2016-08-09 Thomas Petazzoni
2016-08-10 14:14 ` [Buildroot] Analysis of build " Thomas Petazzoni
2016-08-10 19:36 ` Waldemar Brodkorb
2016-08-10 20:30 ` Thomas Petazzoni
2016-08-10 22:21 ` Alistair Francis
2016-08-11 20:00 ` Yann E. MORIN
2016-08-11 20:23 ` Thomas Petazzoni
2016-08-12 22:33 ` Alistair Francis
2016-08-12 9:31 ` Jörg Krause
2016-08-17 2:27 ` Matthew Weber
2016-08-17 9:20 ` Yann E. MORIN [this message]
2016-08-13 21:14 ` Vivien Didelot
2016-08-13 21:55 ` Yann E. MORIN
2016-08-13 22:14 ` Yann E. MORIN
2016-08-14 0:17 ` Arnout Vandecappelle
2016-08-14 0:37 ` Yann E. MORIN
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=20160817092009.GA5778@free.fr \
--to=yann.morin.1998@free.fr \
--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