On Thu, 2017-02-23 at 18:48 +0100, Patrick Ohly wrote:
> The VfrCompile tool has a hard-coded maximum length for path names
> which turned out to be too small by around 20 characters in the
> Yocto autobuilder setup. Increasing the maximum by a factor of 4
> is relatively easy and makes the problem less likely.
>
> Signed-off-by: Patrick Ohly <patrick.o...@intel.com>
> ---
> meta/recipes-core/ovmf/ovmf_git.bb | 5 +++++
> 1 file changed, 5 insertions(+)
>
> diff --git a/meta/recipes-core/ovmf/ovmf_git.bb
> b/meta/recipes-core/ovmf/ovmf_git.bb
> index 6b3a597..76e836a 100644
> --- a/meta/recipes-core/ovmf/ovmf_git.bb
> +++ b/meta/recipes-core/ovmf/ovmf_git.bb
> @@ -50,6 +50,11 @@ COMPATIBLE_HOST='(i.86|x86_64).*'
> OVMF_SECURE_BOOT_EXTRA_FLAGS ??= ""
> OVMF_SECURE_BOOT_FLAGS = "-DSECURE_BOOT_ENABLE=TRUE
> ${OVMF_SECURE_BOOT_EXTRA_FLAGS}"
>
> +do_patch[postfuncs] += "fix_path_len"
> +fix_path_len () {
> + sed -i -e 's/^#define MAX_PATH.*255/#define MAX_PATH 1023/'
> ${S}/BaseTools/Source/C/VfrCompile/EfiVfr.h
> +}
I've used sed here because it was easy. I'll also send a version which
uses a proper patch. Just beware of the line encoding issues. The patch
really must have CR line ends, otherwise it won't apply to the source.
It might be safer to pull V2 of the ovmf patch from:
https://github.com/pohly/openembedded-core/commits/ovmf
--
Best Regards, Patrick Ohly
The content of this message is my personal opinion only and although
I am an employee of Intel, the statements I make here in no way
represent Intel's position on the issue, nor am I authorized to speak
on behalf of Intel on this matter.
--
_______________________________________________
Openembedded-core mailing list
Openembedded-core@lists.openembedded.org
http://lists.openembedded.org/mailman/listinfo/openembedded-core
