From: bugzilla at busybox.net <bugzilla@busybox.net>
To: buildroot@busybox.net
Subject: [Buildroot] [Bug 4363] New: Make sure that copied linux and busybox defconfig are writable before modifying
Date: Sat, 22 Oct 2011 03:28:45 +0000 (UTC) [thread overview]
Message-ID: <bug-4363-163@https.bugs.busybox.net/> (raw)
https://bugs.busybox.net/show_bug.cgi?id=4363
Summary: Make sure that copied linux and busybox defconfig are
writable before modifying
Product: buildroot
Version: unspecified
Platform: PC
OS/Version: Linux
Status: NEW
Severity: normal
Priority: P5
Component: Other
AssignedTo: unassigned at buildroot.uclibc.org
ReportedBy: d_mo1234 at yahoo.com
CC: buildroot at uclibc.org
Estimated Hours: 0.0
Created attachment 3661
--> https://bugs.busybox.net/attachment.cgi?id=3661
patch file
I use buildroot in a source controlled environment, with a custom target
skeleton, custom linux defconfig, and custom busybox defconfig. If the custom
defconfigs are not checked out, then they are read-only. So when linux.mk and
busybox.mk copy their respective customized defconfig to output/build, they get
copied as read-only. Then, buildroot tries to modify these files based on the
.config settings, it fails. (You have to manually open permissions to get the
mods operations to work, and move on.) This problem can be avoided by opening
permissions after the copy.
To this end, a patch file is attached.
--
Configure bugmail: https://bugs.busybox.net/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are on the CC list for the bug.
next reply other threads:[~2011-10-22 3:28 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-10-22 3:28 bugzilla at busybox.net [this message]
2011-10-22 12:17 ` [Buildroot] [Bug 4363] Make sure that copied linux and busybox defconfig are writable before modifying bugzilla at busybox.net
2011-10-22 22:48 ` bugzilla at busybox.net
2011-10-22 23:12 ` bugzilla at busybox.net
2011-10-22 23:12 ` bugzilla at busybox.net
2011-10-31 13:45 ` bugzilla at busybox.net
2011-11-01 1:29 ` bugzilla at busybox.net
2013-11-14 0:20 ` bugzilla at busybox.net
2014-02-09 21:23 ` 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-4363-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