All of lore.kernel.org
 help / color / mirror / Atom feed
From: Romain Naour <romain.naour@gmail.com>
To: buildroot@busybox.net
Subject: [Buildroot] Analysis of build results for 2016-08-08
Date: Mon, 22 Aug 2016 21:49:11 +0200	[thread overview]
Message-ID: <34622bb9-7ff7-2d15-fa97-e5ed6570034b@gmail.com> (raw)
In-Reply-To: <17850212-c769-63c4-f05b-79adc47f470c@gmail.com>

Hi Julien, Thomas,

Le 09/08/2016 ? 16:07, Romain Naour a ?crit :
> Hi Thomas, All,
> 
> [snip]
> 
>>>          arm |                host-efl-1.17.2 | NOK | http://autobuild.buildroot.net/results/89bf12f8333d47af0cb5775c859e26f300af56cc/
>>
>> edje_cc: Critical. Unable to open temp file "(null)" for pre-processor.
>>
>> Romain? This looks like a transient error, but I'm not sure.
> 
> I already seen this issue on autobuilders but I'm not able to reproduce it
> locally...

Julien, this issue occurs only on your autobuilder, can you verify if it
reproducible. If yes, can you send me the usual files log (config.log, build log
etc)

http://autobuild.buildroot.net/?reason=host-efl-1.17.2

Best regards,
Romain

  reply	other threads:[~2016-08-22 19:49 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-08-09  6:30 [Buildroot] [autobuild.buildroot.net] Build results for 2016-08-08 Thomas Petazzoni
2016-08-09 12:15 ` [Buildroot] Analysis of build " Thomas Petazzoni
2016-08-09 12:25   ` Gary Bisson
2016-08-09 12:34     ` Thomas Petazzoni
2016-08-09 13:27   ` Ezequiel Garcia
2016-08-09 14:07   ` Romain Naour
2016-08-22 19:49     ` Romain Naour [this message]
2016-08-25  7:29       ` Julien Boibessot
2016-08-25 22:37         ` Arnout Vandecappelle
2016-09-03 15:05           ` Julien Boibessot
2016-09-05  8:14             ` Arnout Vandecappelle
2016-09-05  9:15               ` Yann E. MORIN
     [not found]         ` <975a1c39-2a4d-164c-411b-8357601b570f@essensium.com>
2016-08-26 21:29           ` Romain Naour
2016-08-09 17:58   ` Yann E. MORIN
2016-08-09 21:23     ` 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=34622bb9-7ff7-2d15-fa97-e5ed6570034b@gmail.com \
    --to=romain.naour@gmail.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 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.