From: bugzilla at busybox.net <bugzilla@busybox.net>
To: buildroot@busybox.net
Subject: [Buildroot] [Bug 4387] New: Make sure that dest dir exists before installing mtd files
Date: Sat, 22 Oct 2011 23:45:48 +0000 (UTC) [thread overview]
Message-ID: <bug-4387-163@https.bugs.busybox.net/> (raw)
https://bugs.busybox.net/show_bug.cgi?id=4387
Summary: Make sure that dest dir exists before installing mtd
files
Product: buildroot
Version: unspecified
Platform: PC
OS/Version: Linux
Status: NEW
Severity: minor
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 3697
--> https://bugs.busybox.net/attachment.cgi?id=3697
patch file
I ran into a situation where a custom target skeleton did not have a /usr/sbin
- it relied on something else to make it (busybox?). So when mtd.mk tried to
install things to it, install bombed out. (I think that we were probably using
the new version of "make", which no longer sorts wildcards in alphabetical
order - so mtd might have been before busybox.)
I have attached a patch to make sure installation directory actually exists.
Seems like a prudent thing to do.
--
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 23:45 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-10-22 23:45 bugzilla at busybox.net [this message]
2011-10-31 13:43 ` [Buildroot] [Bug 4387] Make sure that dest dir exists before installing mtd files bugzilla at busybox.net
2011-11-01 1:46 ` bugzilla at busybox.net
2011-11-01 1:48 ` bugzilla at busybox.net
2011-11-02 11:05 ` 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-4387-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