From: bugzilla at busybox.net <bugzilla@busybox.net>
To: buildroot@busybox.net
Subject: [Buildroot] [Bug 12536] New: Linux-Headers extracting failure
Date: Tue, 04 Feb 2020 03:51:47 +0000 [thread overview]
Message-ID: <bug-12536-163@https.bugs.busybox.net/> (raw)
https://bugs.busybox.net/show_bug.cgi?id=12536
Bug ID: 12536
Summary: Linux-Headers extracting failure
Product: buildroot
Version: 2019.11.1
Hardware: All
OS: All
Status: NEW
Severity: normal
Priority: P5
Component: Other
Assignee: unassigned at buildroot.uclibc.org
Reporter: melanie at trash-mail.com
CC: buildroot at uclibc.org
Target Milestone: ---
Buildroot fails with the following error message:
>>> linux-headers custom Extracting
/home/user/pi/my/dl/linux/tarball | tar --strip-components=1 -C
/home/user/pi/my/output/build/linux-headers-custom -xf -
/bin/sh: /home/user/pi/my/dl/linux/tarball: Permission denied
tar: This does not look like a tar archive
tar: Exiting with failure status due to previous errors
make[1]: *** [package/pkg-generic.mk:172:
/home/user/pi/my/output/build/linux-headers-custom/.stamp_extracted] Error 2
make: *** [Makefile:84: _all] Error 2
The failure is caused by this command-line:
/home/user/pi/my/dl/linux/tarball | tar --strip-components=1 -C
/home/user/pi/my/output/build/linux-headers-custom -xf -
To fix this issue, the following command works for me:
tar --strip-components=1 -C /home/user/pi/my/output/build/linux-headers-custom
-xf /home/user/pi/my/dl/linux/tarball
--
You are receiving this mail because:
You are on the CC list for the bug.
next reply other threads:[~2020-02-04 3:51 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-02-04 3:51 bugzilla at busybox.net [this message]
2020-02-04 7:01 ` [Buildroot] [Bug 12536] Linux-Headers extracting failure bugzilla at busybox.net
2020-02-04 9:14 ` bugzilla at busybox.net
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-12536-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