Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Alexey Brodkin <Alexey.Brodkin@synopsys.com>
To: buildroot@busybox.net
Subject: [Buildroot] Analysis of build results for 2017-10-30
Date: Thu, 2 Nov 2017 22:30:51 +0000	[thread overview]
Message-ID: <1509661850.7985.41.camel@synopsys.com> (raw)
In-Reply-To: <20171102232155.11995715@windsurf>

Hi Thomas, all,

On Thu, 2017-11-02 at 23:21 +0100, Thomas Petazzoni wrote:
> Hello,
> 
> Quick feedback on all the build issues.
> 
> On Tue, 31 Oct 2017 23:05:19 +0100, Thomas Petazzoni wrote:
> 
> > 
> > On Tue, 31 Oct 2017 08:00:13 +0100 (CET), Thomas Petazzoni wrote:
> > 
> > > ? ? ? ? ?arc |?????????????????busybox-1.27.2 | NOK | https://urldefense.proofpoint.com/v2/url?u=http-3A__autobuild.buildroot.net_results_2cb531
> > > b9f9c75bb5dae10c02f2afeca225c65947&d=DwIFaQ&c=DPL6_X_6JkXFx7AXWqB0tg&r=lqdeeSSEes0GFDDl656eViXO7breS55ytWkhpk5R81I&m=SAoW0E6nimRIdKo5CmAKyfsXXQO
> > > z_SQmi2vzF0vzHlU&s=ZI69s1d8Fhd0U0CQ_OKm3nRZMN96MGVA18cf7tkNTqg&e= | ORPH??
> > 
> > 
> > ? CC??????console-tools/setlogcons.o
> > libbb/appletlib.c:206:8: error: 'NUM_APPLETS' undeclared (first use in this function); did you mean 'PF_APPLETALK'?
> > ? max = NUM_APPLETS;
> > 
> > What is going on here?!?
> 
> It still occurred only once,
> https://urldefense.proofpoint.com/v2/url?u=http-3A__autobuild.buildroot.net_-3Freason-3Dbusybox-2D1.27.2&d=DwIFaQ&c=DPL6_X_6JkXFx7AXWqB0tg&r=lqdeeSS
> Ees0GFDDl656eViXO7breS55ytWkhpk5R81I&m=SAoW0E6nimRIdKo5CmAKyfsXXQOz_SQmi2vzF0vzHlU&s=wzUJlrejybSwFO6Qu3hTo_4dl74GCFzSh_RgSlNUAbY&e=. Not sure what
> this means.

As I just wrote let's not spend too much time on this one before we see more manifestations.

> > > ?????????arc |???????????????????ffmpeg-3.3.5 | NOK | https://urldefense.proofpoint.com/v2/url?u=http-
> > > 3A__autobuild.buildroot.net_results_b8fd41b127ab7702a2b69998076d737ea2e092b5&d=DwIFaQ&c=DPL6_X_6JkXFx7AXWqB0tg&r=lqdeeSSEes0GFDDl656eViXO7breS55
> > > ytWkhpk5R81I&m=SAoW0E6nimRIdKo5CmAKyfsXXQOz_SQmi2vzF0vzHlU&s=id9_4gCi8sNYG1DOhijn81A1Q54eebDnpM1PyF0n3RQ&e= |?????
> > > ?????????arc |???????????????????ffmpeg-3.3.5 | NOK | https://urldefense.proofpoint.com/v2/url?u=http-3A__autobuild.buildroot.net_results_43c90f
> > > bad3662101ef4eb5958f73700d1ff57b38&d=DwIFaQ&c=DPL6_X_6JkXFx7AXWqB0tg&r=lqdeeSSEes0GFDDl656eViXO7breS55ytWkhpk5R81I&m=SAoW0E6nimRIdKo5CmAKyfsXXQO
> > > z_SQmi2vzF0vzHlU&s=jQSJNcBcuOTAEj4CB77TeJherexKlUNtXrlf6NAS4MU&e= |?????
> > > ?????????arc |???????????????????ffmpeg-3.3.5 | NOK | https://urldefense.proofpoint.com/v2/url?u=http-3A__autobuild.buildroot.net_results_a152a1
> > > 90108986392346efbba001b9dd0bdc89bc&d=DwIFaQ&c=DPL6_X_6JkXFx7AXWqB0tg&r=lqdeeSSEes0GFDDl656eViXO7breS55ytWkhpk5R81I&m=SAoW0E6nimRIdKo5CmAKyfsXXQO
> > > z_SQmi2vzF0vzHlU&s=KF6aCgUc-UaJozlh0VzdCWa7_6K5deiQzaatTTvXPs8&e= |?????
> > > ?????????arc |???????????????????ffmpeg-3.3.5 | NOK | https://urldefense.proofpoint.com/v2/url?u=http-3A__autobuild.buildroot.net_results_60d442
> > > 46fe6a54b02b53564761807204b9a190d0&d=DwIFaQ&c=DPL6_X_6JkXFx7AXWqB0tg&r=lqdeeSSEes0GFDDl656eViXO7breS55ytWkhpk5R81I&m=SAoW0E6nimRIdKo5CmAKyfsXXQO
> > > z_SQmi2vzF0vzHlU&s=F9ANvupxEY3G1UFbyoeVY8IN30fn5d92A8cRAsN1d6I&e= |???????
> > 
> > libavcodec/vp9dsp_template.c:1685:1: internal compiler error: Segmentation fault
> > 
> > Alexey, could you have a look ?
> 
> Alexey, this continues to happen:
> https://urldefense.proofpoint.com/v2/url?u=http-3A__autobuild.buildroot.net_-3Freason-3Dffmpeg-2D3.3.5&d=DwIFaQ&c=DPL6_X_6JkXFx7AXWqB0tg&r=lqdeeSSEe
> s0GFDDl656eViXO7breS55ytWkhpk5R81I&m=SAoW0E6nimRIdKo5CmAKyfsXXQOz_SQmi2vzF0vzHlU&s=3_daceeHk2UEFoExTryReYH8JdlkdARTaxBDDQVNuf4&e=. Should we disable
> this package on ARC ?

Please not disable ffmpeg for ARC :)
The fix is in ARC tools update [the one to the final release].

> > > ?????????arc |??????????????stress-ng-0.06.15 | NOK | https://urldefense.proofpoint.com/v2/url?u=http-3A__autobuild.buildroot.net_results_296b14
> > > 584c200593f88af75cdda65c4ca03cd863&d=DwIFaQ&c=DPL6_X_6JkXFx7AXWqB0tg&r=lqdeeSSEes0GFDDl656eViXO7breS55ytWkhpk5R81I&m=SAoW0E6nimRIdKo5CmAKyfsXXQO
> > > z_SQmi2vzF0vzHlU&s=TMAIAi0joOmhtuYC0EOziiVpJPEqM-9kDTxX6WI40Io&e= |???????
> > 
> > stress-fp-error.c: In function 'stress_fp_error':
> > stress-fp-error.c:100:10: error: 'FE_INVALID' undeclared (first use in this function); did you mean 'EINVAL'?
> > ????EDOM, FE_INVALID);
> > ??????????^~~~~~~~~~
> > 
> > We already exclude nios2, we should probably exclude ARC as well.
> > Alexey, do you confirm?
> 
> Alexey, I've disabled stress-ng on ARC. If you get to fix the <fenv.h>
> support in glibc, we can re-enable it.

Sure, sounds like a plan!

So it looks like so far we don't have any critical failures for ARC and
the only thing to look at is "stress-ng".

Thanks for all the help with fixing our issues!

-Alexey

  reply	other threads:[~2017-11-02 22:30 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 [this message]
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
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=1509661850.7985.41.camel@synopsys.com \
    --to=alexey.brodkin@synopsys.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