On Wed, Nov 22, 2017 at 02:11:34PM +0100, Matthias Schoepfer wrote:
> Hi Andreas,
>
> >> /home/mschoepf/foo/yocto/build/tmp/work/mic_7700-idp-linux/core-image-fts/1.0-r0/deploy-core-image-fts-image-complete/core-image-fts-mic-7700-20171122105906/tmp.wic.ve8_m7nf/hdd/efi.1/EFI/BOOT
> >>
> >> returned '1' instead of 0
> >> | output: cp: cannot stat
> >> '/home/mschoepf/foo/yocto/build/tmp/work/mic_7700-idp-linux/core-image-fts/1.0-r0/recipe-sysroot/usr/share/EFI/BOOT/*':
> >>
> >> No such file or directory
> > It seems the directory is empty and the '*' is not globbed but taken as
> > filename. Reasen is that either the deployment had not taken place
> > before or the deployment location has changed (again). You could do a
> > find for the files which are tried to be copied by the python plugin
> > files and adapt the paths to have a quick fix.
> Ok, .../recipe-sysroot/usr/share/EFI/BOOT, EFI/BOOT does not exist. Not
> there, not anywhere in the build directory tree. Even doing bitbake -c
> deploy efibootguard did not help. Where shall these files normally be
> coming from?!
>
A quick grep inside `meta-efibootguard` lists
scripts/lib/wic/plugins/source/efibootguard-efi.py:
install_cmd = "install -d %s/EFI/BOOT" % hdddir
This python file creates the directory within the location specified by
the variable hdddir. Your log suggests, that `hdddir % "/EFI/BOOT"` is
/home/mschoepf/foo/yocto/build/tmp/work/mic_7700-idp-linux/core-image-fts/1.0-r0/deploy-core-image-fts-image-complete/core-image-fts-mic-7700-20171122105906/tmp.wic.ve8_m7nf/hdd/efi.1/EFI/BOOT
This would be the first step to verify if this directory exists. Then
the files are copied from `bootimg_dir % "/EFI/BOOT"` to `hdddir` %
"/EFI/BOOT" where the script obviously fails. I.e., the
`efibootguard.bb` recipe installs the files to ${DEPLOYDIR} which is
probably different in this yocto version. Maybe you can alter the
`efibootguard.bb` so that files are deployed into a fixed temporary
directory and alter the python plugin to use the same directory. Or you
could use `bitbake -E` to grep for important directories and
corresponding variables. It is sometimes not obvious which variables to
use to put together a valid path.
Kind regards
Andreas
> Thanks and Regards,
>
> Matthias
--
Andreas Reichel
Dipl.-Phys. (Univ.)
Software Consultant
[email protected], +49-174-3180074
TNG Technology Consulting GmbH, Betastr. 13a, 85774 Unterfoehring
Geschaeftsfuehrer: Henrik Klagges, Dr. Robert Dahlke, Gerhard Mueller
Sitz: Unterfoehring * Amtsgericht Muenchen * HRB 135082
--
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/20171122133559.GA2802%40iiotirae.
For more options, visit https://groups.google.com/d/optout.
