From: Laszlo Ersek <lersek@redhat.com>
To: "Chen, Farrah" <farrah.chen@intel.com>,
"'edk2-devel@lists.01.org'" <edk2-devel@lists.01.org>
Cc: "Hu, Robert" <robert.hu@intel.com>
Subject: Re: OVMF compile error
Date: Fri, 11 Aug 2017 13:21:59 +0200 [thread overview]
Message-ID: <cf6b8fa3-885b-27b9-54be-35e7f90fa983@redhat.com> (raw)
In-Reply-To: <1B925CC0CD9F3341B32D442251E7E1DC390AAB9D@shsmsx102.ccr.corp.intel.com>
On 08/11/17 04:46, Chen, Farrah wrote:
> Hi,
>
> When I build ovmf with commit: 76c6f69ccadc7835c9616b077d9ff1b8e46fe49e, the following error occurred:
>
> git clone https://github.com/tianocore/edk2.git
> cd edk2
> OvmfPkg/build.sh -a X64
> ........................................
> /home/fan/edk2/ShellPkg/Library/UefiShellDriver1CommandsLib/Drivers.c: In function 'GetImageNameFromHandle':
> /home/fan/edk2/ShellPkg/Library/UefiShellDriver1CommandsLib/Drivers.c:220:25: error: passing argument 3 of 'gBS->HandleProtocol' from incompatible pointer type [-Werror]
> );
> ^
> /home/fan/edk2/ShellPkg/Library/UefiShellDriver1CommandsLib/Drivers.c:220:25: note: expected 'void **' but argument is of type 'struct EFI_FIRMWARE_VOLUME2_PROTOCOL **'
> cc1: all warnings being treated as errors
> make: *** [/home/fan/edk2/Build/OvmfX64/DEBUG_GCC48/X64/ShellPkg/Library/UefiShellDriver1CommandsLib/UefiShellDriver1CommandsLib/OUTPUT/Drivers.obj] Error 1
Ray fixed it in f8daac8121e66c46d3374f63f80308a777c2a2e7.
Thanks
Laszlo
next prev parent reply other threads:[~2017-08-11 11:19 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-07-06 8:36 OVMF compile error Chen, Farrah
2017-07-06 8:47 ` Laszlo Ersek
2017-07-07 2:12 ` Chen, Farrah
2017-08-11 2:46 ` Chen, Farrah
2017-08-11 11:21 ` Laszlo Ersek [this message]
-- strict thread matches above, loose matches on Subject: below --
2018-11-07 4:39 Chen, Farrah
2018-11-07 5:37 ` yuchenlin
2018-11-07 10:00 ` Chen, Farrah
[not found] <1B925CC0CD9F3341B32D442251E7E1DC36D93C55@shsmsx102.ccr.corp.intel.com>
2016-09-14 7:21 ` Chen, Farrah
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=cf6b8fa3-885b-27b9-54be-35e7f90fa983@redhat.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