All of lore.kernel.org
 help / color / mirror / Atom feed
From: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
To: buildroot@busybox.net
Subject: [Buildroot] Analysis of build results for 2017-10-30
Date: Thu, 2 Nov 2017 21:04:56 +0100	[thread overview]
Message-ID: <20171102210456.23b1576a@windsurf> (raw)
In-Reply-To: <20171102174338.GD3238@scaer>

Hello,

On Thu, 2 Nov 2017 18:43:38 +0100, Yann E. MORIN wrote:

> > The ARC special version needs:
> > 
> >         depends on BR2_HOST_GCC_AT_LEAST_4_8
> >         depends on BR2_TOOLCHAIN_GCC_AT_LEAST_4_8
> > 
> > Just like the gdb 8.0 version.
> > 
> > Yann, perhaps you could have a look at this ?  
> 
> I'm not sure how I got dragged into an ARC-related issue... ;-]

It's a Config.in dependency issue, you're the expert in that field! :-)*

[snip]

I'll look at the patch you have sent.


> > >         m68k |                   tremor-19427 | TIM | http://autobuild.buildroot.net/results/5bff9fbd24264b3515a669d585e10ef23127d569 |     
> > >       mipsel |                   tremor-19427 | TIM | http://autobuild.buildroot.net/results/d1c8e74477797b597c38186343e4d6c69b05560d |       
> > 
> > SVN repo is dead, and it locks up the build until we time out? Doesn't
> > look great. Yann? :-)  
> 
> Not sure why I got fragged into an SVN-related issue... ;-]
> 
> The repository is not dead from here, though:
> 
>     $ svn ls http://svn.xiph.org/trunk/Tremor
>     Redirecting to URL 'https://svn.xiph.org/trunk/Tremor':
>     Error validating server certificate for 'https://svn.xiph.org:443':
>      - The certificate is not issued by a trusted authority. Use the
>        fingerprint to validate the certificate manually!
>     Certificate information:
>      - Hostname: xiph.org
>      - Valid: from Mar 31 21:45:50 2016 GMT until Mar 31 21:45:50 2018 GMT
>      - Issuer: StartCom Class 2 IV Server CA, StartCom Certification
>        Authority, StartCom Ltd., IL
>      - Fingerprint:
>        B9:AF:55:63:87:0A:45:9C:BD:B9:39:43:08:DA:7C:CA:87:20:BF:11
>     (R)eject, accept (t)emporarily or accept (p)ermanently? t
>     CHANGELOG
>     COPYING
>     [...]
> 
> But there is an https redirect, and the certificate is not recognised
> somehow (my Firefox has no problem with it, though)...
> 
> We should probably at least add '--non-interactive' to have it at least
> fail if it needs to prompt.

It is not normal that we timeout. Instead, we should gracefully
fallback on using http://sources.buildroot.net/tremor-19427.tar.gz
instead.

> We could also make use of '--trust-server-cert-failures=ARG' where ARG
> is one of 'unknown-ca', 'cn-mismatch', 'expired', 'not-yet-valid' or
> 'other'. But I am a bit reluctant at silently quiesce certificate
> errors...

No, I just want the svn command to fail, and fallback to the backup
mirror, if that is possible.

> > > microblazeel |           usb_modeswitch-2.5.0 | NOK | http://autobuild.buildroot.net/results/20a9a75f701ce70c2ae434085a85ad8d34adc67b | ORPH
> > >          arm |           usb_modeswitch-2.5.0 | NOK | http://autobuild.buildroot.net/results/46844b028989808aa7340c14af22f2855ec803d8 | ORPH
> > >   
> > 
> > Not sure. Is it just:
> > 
> > 
> > make[2]: *** [jim/libjim.a] Error 1
> > make[2]: *** Waiting for unfinished jobs....
> > usb_modeswitch.c: In function 'checkSuccess':
> > usb_modeswitch.c:1579:7: warning: 'i' may be used uninitialized in this function [-Wmaybe-uninitialized]
> >     if (i == CheckSuccess-1) {
> > 
> > That makes the build fail?  
> 
> The problem is higher in the stack:
> 
>     autosetup/system.tcl:203 /home/peko/autobuild/instance-2/output/build/usb_modeswitch-2.5.0/jim/autosetup/config.guess: unable to guess system type

That Peter's gcc112 build machine that strikes again I guess.

Peter ?

Thomas
-- 
Thomas Petazzoni, CTO, Free Electrons
Embedded Linux and Kernel engineering
http://free-electrons.com

  parent reply	other threads:[~2017-11-02 20:04 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 [this message]
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
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=20171102210456.23b1576a@windsurf \
    --to=thomas.petazzoni@free-electrons.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.