Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Carlos Santos <casantos@datacom.ind.br>
To: buildroot@busybox.net
Subject: [Buildroot] [autobuild.buildroot.net] Build results for	2016-09-02
Date: Sat, 3 Sep 2016 15:10:20 -0300 (BRT)	[thread overview]
Message-ID: <760420464.3255032.1472926220380.JavaMail.zimbra@datacom.ind.br> (raw)
In-Reply-To: <2181287.8UlWShMbI3@sagittea>

> From: "J?r?me Pouiller" <jezz@sysmic.org>
> To: buildroot at busybox.net
> Cc: "Thomas Petazzoni" <thomas.petazzoni@free-electrons.com>, "Alexey Brodkin" <Alexey.Brodkin@synopsys.com>
> Sent: Saturday, September 3, 2016 1:03:13 PM
> Subject: Re: [Buildroot] [autobuild.buildroot.net] Build results for	2016-09-02

> On Saturday 03 September 2016 08:30:33 Thomas Petazzoni wrote:
> [...]
>> mips64el |              util-linux-2.28.1 | NOK |
>> http://autobuild.buildroot.net/results/e45931629ee3f5dc45de6940a2c0983435f77e00
>>      sh4 |              util-linux-2.28.1 | NOK |
>> http://autobuild.buildroot.net/results/b3649dedd048515844675cd48b84bab74eb897f8
>>   x86_64 |              util-linux-2.28.1 | NOK |
>> http://autobuild.buildroot.net/results/26b3a4de1fb8b366727299ff5de7d59b3e521c23
> 
> wget do not accept certificate from cdn.kernel.org. It seems to be
> related to :
>   https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=409938
> 
> wget >= 1.13-1 is necessary to fix problem. I see three solutions:
>  1. Revert de76cb7da734dde2204a7ea9ff60e24cbe857ddb ("Use CDN
>     kernel.org mirror")

This can slow down the downloading of many source files.

>  2. Use http instead if https

I suspect that this would require passing "--no-hsts" to wget (did not test with an old version to confirm).

>  3. Check wget version in dependencies.sh

What would be the approach, in thes case, compiling wget as a host tool?

> Any opinion?

I'd vote for option 3, since wget 1.13.1 is already five years old. I'd ask the developer to migrate to a more up-to-date OS installation rather than spending a lot of effort to circumvent the problem in Buildroot.

Carlos Santos (Casantos)
DATACOM, P&D

  reply	other threads:[~2016-09-03 18:10 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-09-03  6:30 [Buildroot] [autobuild.buildroot.net] Build results for 2016-09-02 Thomas Petazzoni
2016-09-03 16:03 ` Jérôme Pouiller
2016-09-03 18:10   ` Carlos Santos [this message]
2016-09-03 18:36   ` Thomas Petazzoni
2016-09-03 18:59     ` Jérôme Pouiller
2016-09-03 21:23       ` Thomas Petazzoni
2016-09-05  8:05         ` Peter Korsgaard
2016-09-05  8:20           ` Jérôme Pouiller
2016-09-05  9:30           ` Yann E. MORIN
2016-09-05 16:09             ` Peter Korsgaard
2016-09-05 16:22         ` Jérôme Pouiller
2016-09-05  6:40       ` Peter Korsgaard

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=760420464.3255032.1472926220380.JavaMail.zimbra@datacom.ind.br \
    --to=casantos@datacom.ind.br \
    --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