From: bugzilla at busybox.net <bugzilla@busybox.net>
To: buildroot@busybox.net
Subject: [Buildroot] [Bug 9201] Permission denied make: *** [core-dependencies] Error 126 in Buildroot-2015.08.1
Date: Fri, 28 Oct 2016 08:15:20 +0000 [thread overview]
Message-ID: <bug-9201-163-BZaH5w8Cvb@https.bugs.busybox.net/> (raw)
In-Reply-To: <bug-9201-163@https.bugs.busybox.net/>
https://bugs.busybox.net/show_bug.cgi?id=9201
Thomas Petazzoni <thomas.petazzoni@free-electrons.com> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|NEW |RESOLVED
Resolution|--- |WORKSFORME
--- Comment #2 from Thomas Petazzoni <thomas.petazzoni@free-electrons.com> ---
This is an issue on your side: all files that have execution permissions no
longer have execution permissions. So you did something wrong when extracting
the Buildroot tarball.
I just verified the 2015.08.1 tarball, and the files causing an issue on your
side are correct in the tarball:
thomas at skate:/tmp$ tar tvf buildroot-2015.08.1.tar.gz | grep config.guess
-rwxrwxr-x root/root 45297 2015-09-06 22:57
buildroot-2015.08.1/support/gnuconfig/config.guess
thomas at skate:/tmp$ tar tvf buildroot-2015.08.1.tar.gz | grep check-host-tar.sh
-rwxrwxr-x root/root 1017 2015-09-06 22:57
buildroot-2015.08.1/support/dependencies/check-host-tar.sh
--
You are receiving this mail because:
You are on the CC list for the bug.
prev parent reply other threads:[~2016-10-28 8:15 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <bug-9201-163@https.bugs.busybox.net/>
2016-10-28 3:01 ` [Buildroot] [Bug 9201] Permission denied make: *** [core-dependencies] Error 126 in Buildroot-2015.08.1 bugzilla at busybox.net
2016-10-28 8:15 ` bugzilla at busybox.net [this message]
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-9201-163-BZaH5w8Cvb@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