From: bugzilla at busybox.net <bugzilla@busybox.net>
To: buildroot@busybox.net
Subject: [Buildroot] [Bug 12821] New: Vagrantfile in download page still points to 2020.02
Date: Mon, 27 Apr 2020 20:02:55 +0000 [thread overview]
Message-ID: <bug-12821-163@https.bugs.busybox.net/> (raw)
https://bugs.busybox.net/show_bug.cgi?id=12821
Bug ID: 12821
Summary: Vagrantfile in download page still points to 2020.02
Product: buildroot
Version: 2020.02
Hardware: All
OS: Linux
Status: NEW
Severity: normal
Priority: P5
Component: Outdated package
Assignee: unassigned at buildroot.uclibc.org
Reporter: phernandez at luxoft.com
CC: buildroot at uclibc.org
Target Milestone: ---
I followed the instructions inside the Buildroot user manual and in section 3,
it asks you to get the Vagrantfile from
https://buildroot.org/downloads/Vagrantfile but this is still pointing to
2020.02 and should be pointing to 2020.02.1
2020.02 is not able to compile using the config file from
freescale_imx8mmevk_defconfig, it end up with the next error without image
creation:
remote: Enumerating objects: 54171, done.
remote: Counting objects: 100% (54171/54171), done.
remote: Compressing objects: 100% (9304/9304), done.
error: cannot fork() for index-pack: Cannot allocate memory
fatal: fetch-pack: unable to fork off index-pack
Detected a corrupted git cache.
This is the second time in a row; bailing out
--2020-04-24 22:54:26--
http://sources.buildroot.net/linux/linux-rel_imx_4.14.98_2.0.0_ga.tar.gz
Resolving sources.buildroot.net (sources.buildroot.net)... 104.26.1.37,
104.26.0.37, 2606:4700:20::681a:125, ...
Connecting to sources.buildroot.net (sources.buildroot.net)|104.26.1.37|:80...
connected.
HTTP request sent, awaiting response... 404 Not Found
2020-04-24 22:54:26 ERROR 404: Not Found.
--2020-04-24 22:54:26--
http://sources.buildroot.net/linux-rel_imx_4.14.98_2.0.0_ga.tar.gz
Resolving sources.buildroot.net (sources.buildroot.net)... 104.26.0.37,
104.26.1.37, 2606:4700:20::681a:25, ...
Connecting to sources.buildroot.net (sources.buildroot.net)|104.26.0.37|:80...
connected.
HTTP request sent, awaiting response... 404 Not Found
2020-04-24 22:54:27 ERROR 404: Not Found.
package/pkg-generic.mk:167: recipe for target
'/home/vagrant/Gemini/test_capxl_daemons_for_gemini/capxl/output/build/linux-headers-rel_imx_4.14.98_2.0.0_ga/.stamp_downloaded'
failed
make[1]: ***
[/home/vagrant/Gemini/test_capxl_daemons_for_gemini/capxl/output/build/linux-headers-rel_imx_4.14.98_2.0.0_ga/.stamp_downloaded]
Error 1
Makefile:84: recipe for target '_all' failed
make: *** [_all] Error 2
This is not happening in version 2020.02.1
--
You are receiving this mail because:
You are on the CC list for the bug.
next reply other threads:[~2020-04-27 20:02 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-04-27 20:02 bugzilla at busybox.net [this message]
2020-05-16 14:22 ` [Buildroot] [Bug 12821] Vagrantfile in download page still points to 2020.02 bugzilla at busybox.net
2024-06-15 14:52 ` bugzilla
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=bug-12821-163@https.bugs.busybox.net/ \
--to=bugzilla@busybox.net \
--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