From: Ed Bartosh <ed.bartosh@linux.intel.com>
To: openembedded-core@lists.openembedded.org
Subject: [PATCH] syslinux.bbclass: ensure creation of output directory
Date: Fri, 19 Aug 2016 17:46:39 +0300 [thread overview]
Message-ID: <1471617999-4050-1-git-send-email-ed.bartosh@linux.intel.com> (raw)
build_syslinux_cfg function creates syslinux configuration file.
The code assumes that the output directory exists, which is not
always the case. For example rm_work task removes rootfs directory
structure and causes build_syslinux_cfg to fail with this error:
Unable to open ../<image>-<version>/syslinux_vm.cfg
Made build_syslinux_cfg depend on output directory to ensure that
directory is created before running the function.
[YOCTO #10159]
Signed-off-by: Ed Bartosh <ed.bartosh@linux.intel.com>
---
meta/classes/syslinux.bbclass | 1 +
1 file changed, 1 insertion(+)
diff --git a/meta/classes/syslinux.bbclass b/meta/classes/syslinux.bbclass
index fa3e3ec..35d9eed 100644
--- a/meta/classes/syslinux.bbclass
+++ b/meta/classes/syslinux.bbclass
@@ -196,3 +196,4 @@ python build_syslinux_cfg () {
cfgfile.close()
}
+build_syslinux_cfg[dirs] = "${S}"
--
2.6.6
reply other threads:[~2016-08-19 14:46 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=1471617999-4050-1-git-send-email-ed.bartosh@linux.intel.com \
--to=ed.bartosh@linux.intel.com \
--cc=openembedded-core@lists.openembedded.org \
/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