Use ${S} explicitly for generated config files
PATCH 1/1 bootimage: Use ${S} explicitly for generated config files
In reply to Darren HartThe syslinux and grub-efi classes were generating config files in the current working directory. This caused a failure due to a race in the creation of the directories leading to cwd changing and the build failing to find the config files. While this has been addressed in bitbake, it is better to use an explicit path.
While ${WORKDIR} may seem a more appropriate place, the recipe already uses ${S} for the "hdd" and "cd" construction, so we use ${S} here to keep things consolidated and consistent and address the issue with minimal change.
--- meta/classes/grub-efi.bbclass | 8 +++----- meta/classes/syslinux.bbclass | 4 ++-- 2 files changed, 5 insertions(+), 7 deletions(-)
meta/classes/grub-efi.bbclass +3 -5
@@ -16,7 +16,7 @@ do_bootimg[depends] += "grub-efi-${TARGET_ARCH}-native:do_deploy" -GRUBCFG = "grub.cfg" +GRUBCFG = "${S}/grub.cfg" GRUB_TIMEOUT ?= "10" #FIXME: build this from the machine config GRUB_OPTS ?= "serial --unit=0 --speed=115200 --word=8 --parity=no --stop=1"
@@ -56,7 +56,7 @@ grubefi_iso_populate() { # FIXUP the <EFIDIR> token in the config # FIXME: This can be dropped once mkdosfs is fixed - sed -i "s@<EFIDIR>@${EFIDIR}@g" ${GRUB_ISODIR}/${GRUBCFG} + sed -i "s@<EFIDIR>@${EFIDIR}@g" ${GRUB_ISODIR}/$(basename "${GRUBCFG}") } grubefi_hddimg_populate() {
@@ -64,7 +64,7 @@ grubefi_hddimg_populate() { # FIXUP the <EFIDIR> token in the config # FIXME: This can be dropped once mkdosfs is fixed - sed -i "s@<EFIDIR>@@g" ${GRUB_HDDDIR}/${GRUBCFG} + sed -i "s@<EFIDIR>@@g" ${GRUB_HDDDIR}/$(basename "${GRUBCFG}") } # FIXME: The <EFIDIR> token can be replaced with ${EFIDIR} once the
@@ -90,8 +90,6 @@ python build_grub_cfg() { if not cfile: raise bb.build.FuncFailed('Unable to read GRUBCFG') - #bb.mkdirhier(os.path.dirname(cfile)) - try: cfgfile = file(cfile, 'w') except OSError:
meta/classes/syslinux.bbclass +2 -2
@@ -15,8 +15,8 @@ do_bootimg[depends] += "syslinux:do_populate_sysroot \ syslinux-native:do_populate_sysroot" -SYSLINUXCFG = "syslinux.cfg" -SYSLINUXMENU = "menu" +SYSLINUXCFG = "${S}/syslinux.cfg" +SYSLINUXMENU = "${S}/menu" SYSLINUX_ISODIR = "${ISODIR}/isolinux" SYSLINUX_HDDDIR = "${HDDDIR}"
Signature · 1 line
1.7.6.4
cover Use ${S} explicitly for generated config files
The following changes since commit e57935dc18d576feb1003b48e7cdc72a444131b8:
Revert "classes/buildhistory: add new output history collection class" (2011-12-01 23:00:52 +0000)
are available in the git repository at:
git://git.yoctoproject.org/user-contrib/dvhart/oe-core efi/cfgpath
http://git.yoctoproject.org/cgit.cgi/user-contrib/dvhart/oe-core/log/?h=efi/cfgpath
Darren Hart (1):
bootimage: Use ${S} explicitly for generated config files
meta/classes/grub-efi.bbclass | 8 +++----- meta/classes/syslinux.bbclass | 4 ++-- 2 files changed, 5 insertions(+), 7 deletions(-)
Signature · 1 line
1.7.6.4
Richard Purdie
AppliedRe: [PATCH 1/1] bootimage: Use ${S} explicitly for generated config files
In reply to Darren HartQuoted 11 lines · Darren Hart
The syslinux and grub-efi classes were generating config files in the current working directory. This caused a failure due to a race in the creation of the directories leading to cwd changing and the build failing to find the config files. While this has been addressed in bitbake, it is better to use an explicit path.
While ${WORKDIR} may seem a more appropriate place, the recipe already uses ${S} for the "hdd" and "cd" construction, so we use ${S} here to keep things consolidated and consistent and address the issue with minimal change.
Quoted 5 lines
Signed-off-by Darren Hart <[email protected]>--- meta/classes/grub-efi.bbclass | 8 +++----- meta/classes/syslinux.bbclass | 4 ++-- 2 files changed, 5 insertions(+), 7 deletions(-)
Merged to master, thanks.
Richard