From: bugzilla at busybox.net <bugzilla@busybox.net>
To: buildroot@busybox.net
Subject: [Buildroot] [Bug 13126] New: make fails - bzip2-1.0.6.tar.gz and DirectFB-1.7.7.tar.gz aren't tarballs
Date: Thu, 30 Jul 2020 02:31:38 +0000 [thread overview]
Message-ID: <bug-13126-163@https.bugs.busybox.net/> (raw)
https://bugs.busybox.net/show_bug.cgi?id=13126
Bug ID: 13126
Summary: make fails - bzip2-1.0.6.tar.gz and
DirectFB-1.7.7.tar.gz aren't tarballs
Product: buildroot
Version: 2018.02
Hardware: PC
OS: Linux
Status: NEW
Severity: blocker
Priority: P5
Component: Other
Assignee: unassigned at buildroot.uclibc.org
Reporter: chuckb at craniac.com
CC: buildroot at uclibc.org
Target Milestone: ---
I'm cross-compiling for ARCH=arm on a 32-bit Fedora-27 system, (64-bit) Xeon
processor. All packages upgraded with yum as of July 29, 2020.
Executing make, the build fails when it gets to bzip2-1.0.6.tar.gz and then
DirectFB-1.7.7.tar.gz
The problem appears to be that these files, as downloaded during the build, are
not tarballs. They're uncompressed html files.
When I retrieved files of the same names from sources.buildroot.net, the build
appears to proceed normally. I'm new at this, so it's possible there will be
problems later, but for now the build is continuing.
My config uses default file sources:
- sources.buildroot.net
- cdn.kernel.org/pub
- ftpmirror.gnu.org
- rocks.moonscript.org
- cpan.metacpan.org
buildroot cloned on July 29, 2020.
--
You are receiving this mail because:
You are on the CC list for the bug.
next reply other threads:[~2020-07-30 2:31 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-07-30 2:31 bugzilla at busybox.net [this message]
2020-07-30 22:21 ` [Buildroot] [Bug 13126] make fails - bzip2-1.0.6.tar.gz and DirectFB-1.7.7.tar.gz aren't tarballs bugzilla at busybox.net
2022-03-07 19:44 ` 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-13126-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