All of lore.kernel.org
 help / color / mirror / Atom feed
From: Matthew Weber <matthew.weber@rockwellcollins.com>
To: buildroot@busybox.net
Subject: [Buildroot] Analysis of build results for 2017-10-30
Date: Wed, 8 Nov 2017 10:16:16 -0600	[thread overview]
Message-ID: <CANQCQpY2fsEJkaU1-0_Sg+Mqb3sH_m_TLxUPCAT6DRRUwWVgsg@mail.gmail.com> (raw)
In-Reply-To: <CAJtjsKZ-OFFehKRd-XD79XobUnUqGpFqRcXL4P1d-cqaFHoKmg@mail.gmail.com>

Johan,

On Wed, Nov 8, 2017 at 6:49 AM, Johan Oudinet <johan.oudinet@gmail.com> wrote:
> Hi Thomas, all,
>
> On Tue, Oct 31, 2017 at 11:05 PM, Thomas Petazzoni
> <thomas.petazzoni@free-electrons.com> wrote:
>>
>>>          arm |        host-erlang-rebar-2.6.4 | TIM | http://autobuild.buildroot.net/results/6c4c7b3094bd48a72786f5be3d760f0356557403 |
>>>          arm |        host-erlang-rebar-2.6.4 | TIM | http://autobuild.buildroot.net/results/a17d5eb1aac01dab19412aa28d523625577730db |
>>
>> The infamous ./bootstrap issue that consumes 100% of the CPU before
>> timing out the build job. Johan, we really need to find a solution to
>> this problem. How can we proceed to debug this?
>>
>
> The bootstrap file is an erlang script:
> #!/usr/bin/env escript
>
> When trying to reproduce this bug, I see it prints "No beam files
> found". As this message is printed quite early in this script, I guess
> the problem is in loading escript from the host. Unfortunately, I
> wasn't able to reproduce this bug on my machine, so this is only a
> guess.
> Is it possible to execute ./bootstrap --help from this machine? If the
> problem is in loading escript, it should lead to the same timeout
> error.
>

I ran the same build on that machine ( make clean host-erlang-rebar ).
It ran without error and printed the following early in the build
step.

make[1]: Entering directory
`/usr/lfs/v0/rc-buildroot/output/build/host-erlang-rebar-2.6.4'
./bootstrap
No beam files found.
Recompile: src/rebar
Recompile: src/rebar_abnfc_compiler

As a note, that machine doesn't have escript, ie I go into the
host-erlang-rebar folder and if I run the bootstrap --help I get a
escript error  (which is expected).
./bootstrap --help
/usr/bin/env: escript: No such file or directory


I'll run the complete build a few times and see if anything pops up.

Matt

  reply	other threads:[~2017-11-08 16:16 UTC|newest]

Thread overview: 43+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-10-31  7:00 [Buildroot] [autobuild.buildroot.net] Build results for 2017-10-30 Thomas Petazzoni
2017-10-31 22:05 ` [Buildroot] Analysis of build " Thomas Petazzoni
2017-11-01  2:37   ` Matthew Weber
2017-11-01  9:45     ` Thomas Petazzoni
2017-11-01 10:01       ` Alexey Brodkin
2017-11-01 10:24         ` Thomas Petazzoni
2017-11-01 10:31           ` Alexey Brodkin
2017-11-02  2:31           ` Waldemar Brodkorb
2017-11-02  8:06             ` Thomas Petazzoni
2017-11-01 13:24       ` Matthew Weber
2017-11-01 13:37         ` Thomas Petazzoni
2017-11-01 10:17   ` Samuel Martin
2017-11-01 13:40     ` Thomas Petazzoni
2017-11-01 18:03   ` Baruch Siach
2017-11-02 10:54     ` Peter Korsgaard
2017-11-03 22:31       ` Peter Korsgaard
2017-11-02 10:46   ` Peter Korsgaard
2017-11-02 17:43   ` Yann E. MORIN
2017-11-02 18:08     ` Yann E. MORIN
2017-11-02 20:04     ` Thomas Petazzoni
2017-11-02 20:55       ` Yann E. MORIN
2017-11-02 22:21   ` Thomas Petazzoni
2017-11-02 22:30     ` Alexey Brodkin
2017-11-03 11:17     ` Angelo Compagnucci
2017-11-03 13:38       ` Thomas Petazzoni
2017-11-03 13:46         ` Angelo Compagnucci
2017-11-03 13:52           ` Thomas Petazzoni
2017-11-03 14:18             ` Angelo Compagnucci
2017-11-03 14:28               ` Thomas Petazzoni
2017-11-03 14:35                 ` Angelo Compagnucci
2017-11-03 14:41                   ` Thomas Petazzoni
2017-11-04 22:18     ` Arnout Vandecappelle
2017-11-04 22:20       ` Thomas Petazzoni
2017-11-04 22:36         ` Peter Korsgaard
2017-11-05 14:40           ` Thomas Petazzoni
2017-11-05 19:36             ` Peter Korsgaard
2017-11-05 22:35               ` Thomas Petazzoni
2017-11-09 20:58       ` Alexey Brodkin
2017-11-02 22:22   ` Alexey Brodkin
2017-11-08 12:49   ` Johan Oudinet
2017-11-08 16:16     ` Matthew Weber [this message]
2017-11-08 17:33       ` Yann E. MORIN
2017-11-08 19:35         ` Matthew Weber

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=CANQCQpY2fsEJkaU1-0_Sg+Mqb3sH_m_TLxUPCAT6DRRUwWVgsg@mail.gmail.com \
    --to=matthew.weber@rockwellcollins.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.