From: Yann E. MORIN <yann.morin.1998@free.fr>
To: buildroot@busybox.net
Subject: [Buildroot] raspberry3_defconfig error
Date: Sun, 10 Jul 2016 20:26:42 +0200 [thread overview]
Message-ID: <20160710182642.GE3688@free.fr> (raw)
In-Reply-To: <HK2PR0401MB1329D3F86C57BD1E93FC6137B33E0@HK2PR0401MB1329.apcprd04.prod.outlook.com>
Mike, All,
On 2016-07-10 18:04 +0000, Foxtrot Mike spake thusly:
> I am trying to create a customized linux for raspberry pi 3. I have
> installed buildroot2016.5 with all the dependencies. I am trying to
> compile everything with the default configuration file by executing:
>
> $ make raspberrypi3_defconfig
> $ make
>
> It fails with the following errors:
>
> >>> linux-headers 26f3b72a9c049be10e6af196252283e1f6ab9d1f Downloading
A common reason for the RPi kernel to fail downloading is that upstream
often rebase their branches. However, I just checked, and the commit we
reference is still present in the RPi Linux tree.
> Doing full clone
> Cloning into bare repository
> 'linux-headers-26f3b72a9c049be10e6af196252283e1f6ab9d1f'...
> remote: Counting objects: 5034470, done.
> remote: Compressing objects: 100% (2553/2553), done.
> error: RPC failed; curl 56 SSL read:
> error:00000000:lib(0):func(0):reason(0), errno 104
> fatal: The remote end hung up unexpectedly
> fatal: early EOF
> fatal: index-pack failed
cURL error 56 is "Failure in receiving network data." so probably a
network issue between you and github.
Did that error happen in both of your build tests?
Did it happen right when starting downloading, or did it happen after a
while?
> --2016-07-11 01:48:20--
> http://sources.buildroot.net/linux-26f3b72a9c049be10e6af196252283e1f6ab9d1f.tar.gz
> Resolving sources.buildroot.net (sources.buildroot.net)... 176.9.16.109
> Connecting to sources.buildroot.net
> (sources.buildroot.net)|176.9.16.109|:80... connected.
> HTTP request sent, awaiting response... 404 Not Found
> 2016-07-11 01:48:22 ERROR 404: Not Found.
Indeed, s.b.o. does not cache those files.
Regards,
Yann E. MORIN.
--
.-----------------.--------------------.------------------.--------------------.
| Yann E. MORIN | Real-Time Embedded | /"\ ASCII RIBBON | Erics' conspiracy: |
| +33 662 376 056 | Software Designer | \ / CAMPAIGN | ___ |
| +33 223 225 172 `------------.-------: X AGAINST | \e/ There is no |
| http://ymorin.is-a-geek.org/ | _/*\_ | / \ HTML MAIL | v conspiracy. |
'------------------------------^-------^------------------^--------------------'
next prev parent reply other threads:[~2016-07-10 18:26 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-07-10 18:04 [Buildroot] raspberry3_defconfig error Foxtrot Mike
2016-07-10 18:26 ` Yann E. MORIN [this message]
2016-07-12 8:46 ` Peter Korsgaard
[not found] <HK2PR0401MB13294C8912D14A1661BA2510B33E0@HK2PR0401MB1329.apcprd04.prod.outlook.com>
2016-07-10 19:20 ` Foxtrot Mike
2016-07-10 21:02 ` 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=20160710182642.GE3688@free.fr \
--to=yann.morin.1998@free.fr \
--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