On 2018-01-24 11:23, [ext] Andreas J. Reichel wrote:
> From: Andreas Reichel <[email protected]>
>
> efibootguard.bbclass creates an iso directory,
> which sometimes is not ready yet before chdir'ing
> into this new directory. Prevent this by correctly
> fetching the result.
Can you clarify what "not ready yet" exactly means? This sounds to me
like an ordering issue ("will be ready later"), but then the patch below
which simply fails the build does not match the description.
Jan
>
> Signed-off-by: Andreas Reichel <[email protected]>
> ---
> classes/efibootguard.bbclass | 4 +++-
> 1 file changed, 3 insertions(+), 1 deletion(-)
>
> diff --git a/classes/efibootguard.bbclass b/classes/efibootguard.bbclass
> index c979e23..553da57 100644
> --- a/classes/efibootguard.bbclass
> +++ b/classes/efibootguard.bbclass
> @@ -70,7 +70,9 @@ python build_efi_cfg() {
>
> make_isodir_cmd = ["mkdir", "-p", isodir]
> p = Popen(make_isodir_cmd)
> -
> + (out, err) = p.communicate()
> + if not p.returncode == 0:
> + bb.fatal("Could not create isodir: %s" % isodir)
> os.chdir(isodir)
> p = Popen([bg_setenv_cmd, "--file", "--kernel=vmlinuz",
> "--watchdog=30"], \
> stdout=PIPE, stderr=PIPE)
>
--
Siemens AG, Corporate Technology, CT RDA IOT SES-DE
Corporate Competence Center Embedded Linux
--
You received this message because you are subscribed to the Google Groups "EFI
Boot Guard" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to [email protected].
To post to this group, send email to [email protected].
To view this discussion on the web visit
https://groups.google.com/d/msgid/efibootguard-dev/5848f35e-f325-18c4-f19f-eae7b3e61d0d%40siemens.com.
For more options, visit https://groups.google.com/d/optout.
