public inbox for devel@edk2.groups.io
 help / color / mirror / Atom feed
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: Thu, 6 Jul 2017 10:47:04 +0200	[thread overview]
Message-ID: <104d890c-1a2c-684f-7277-7ea4fa8e5c94@redhat.com> (raw)
In-Reply-To: <1B925CC0CD9F3341B32D442251E7E1DC39097EE3@shsmsx102.ccr.corp.intel.com>

On 07/06/17 10:36, Chen, Farrah wrote:
> Hi,
> 
> When I build ovmf with commit: 19b2cb5c11cf3a4512e9183125ba4a69facb0489, the following error occurred:
> 
> git clone https://github.com/tianocore/edk2.git
> OvmfPkg/build.sh -a X64
> ........................................
> make: *** [/workspace/ia32e/nightly/kvm-next-20170706-137232-2185c9-31745/kvm/edk2/Build/OvmfX64/DEBUG_GCC48/X64/OvmfPkg/Sec/SecMain/DEBUG/SecMain.efi] Segmentation fault (core dumped)

Thanks for the report; the issue is already fixed in commit 60e85a39fe49
("BaseTools/GenFw: disregard payload in PE debug directory entry size",
2017-07-05).

Please do:

$ git checkout master
$ git pull
$ source edksetup.sh
$ make -C "$EDK_TOOLS_PATH"

and then build OVMF like always.

Thanks
Laszlo


  reply	other threads:[~2017-07-06  8:45 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 [this message]
2017-07-07  2:12   ` Chen, Farrah
2017-08-11  2:46 ` Chen, Farrah
2017-08-11 11:21   ` Laszlo Ersek
  -- 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=104d890c-1a2c-684f-7277-7ea4fa8e5c94@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