From: "PierreGondois" <pierre.gondois@arm.com>
To: "maurice.ma@intel.com" <maurice.ma@intel.com>,
"guo.dong@intel.com" <guo.dong@intel.com>,
"benjamin.you@intel.com" <benjamin.you@intel.com>,
"devel@edk2.groups.io" <devel@edk2.groups.io>, nd <nd@arm.com>
Subject: Build error for UefiPayloadPkgIa32.dsc
Date: Thu, 18 Jun 2020 14:55:25 +0000 [thread overview]
Message-ID: <DB7PR08MB3113072BA5642A517012C07A8B9B0@DB7PR08MB3113.eurprd08.prod.outlook.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 981 bytes --]
Hello,
I am not actively using this platform, but I wanted to report an error when building one of the DSC files in the UefiPayloadPkg with the following configuration:
build -b NOOPT -a IA32 -t VS2017 -p edk2 edk2\UefiPayloadPkg\UefiPayloadPkgIa32.dsc
The following error occurs:
Generating PEIFV FV
#### ['GenFv', '-a', 'Build\\UefiPayloadPkgIA32\\NOOPT_VS2017\\FV\\Ffs\\PEIFV.inf', '-o', 'Build\\UefiPayloadPkgIA32\\NOOPT_VS2017\\FV\\PEIFV.Fv', '-i', Build\\UefiPayloadPkgIA32\\NOOPT_VS2017\\FV\\PEIFV.inf']
Return Value = 2
GenFv: ERROR 3000: Invalid
the required fv image size 0x406c8 exceeds the set fv image size 0x30000
Regards,
Pierre
IMPORTANT NOTICE: The contents of this email and any attachments are confidential and may also be privileged. If you are not the intended recipient, please notify the sender immediately and do not disclose the contents to any other person, use it for any purpose, or store or copy the information in any medium. Thank you.
[-- Attachment #2: Type: text/html, Size: 3013 bytes --]
next reply other threads:[~2020-06-18 14:55 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-06-18 14:55 PierreGondois [this message]
2020-06-18 22:16 ` Build error for UefiPayloadPkgIa32.dsc Guo Dong
2020-06-19 9:55 ` [edk2-devel] " PierreGondois
2020-06-21 2:14 ` Guo Dong
2020-07-08 15:24 ` PierreGondois
2020-07-08 17:55 ` Guo Dong
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-list 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=DB7PR08MB3113072BA5642A517012C07A8B9B0@DB7PR08MB3113.eurprd08.prod.outlook.com \
--to=devel@edk2.groups.io \
/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