From: "Chen, Farrah" <farrah.chen@intel.com>
To: "edk2-devel@lists.01.org" <edk2-devel@lists.01.org>
Cc: "Hu, Robert" <robert.hu@intel.com>
Subject: OVMF compile error
Date: Thu, 6 Jul 2017 08:36:33 +0000 [thread overview]
Message-ID: <1B925CC0CD9F3341B32D442251E7E1DC39097EE3@shsmsx102.ccr.corp.intel.com> (raw)
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)
build.py...
: error 7000: Failed to execute command
make tbuild [/workspace/ia32e/nightly/kvm-next-20170706-137232-2185c9-31745/kvm/edk2/Build/OvmfX64/DEBUG_GCC48/X64/OvmfPkg/Sec/SecMain]
build.py...
: error 7000: Failed to execute command
make tbuild [/workspace/ia32e/nightly/kvm-next-20170706-137232-2185c9-31745/kvm/edk2/Build/OvmfX64/DEBUG_GCC48/X64/MdeModulePkg/Core/Pei/PeiMain]
build.py...
: error F002: Failed to build module
/workspace/ia32e/nightly/kvm-next-20170706-137232-2185c9-31745/kvm/edk2/OvmfPkg/Sec/SecMain.inf [X64, GCC48, DEBUG]
- Failed -
Build end time: 16:19:11, Jul.06 2017
Build total time: 00:00:23
Best Regards,
Fan Chen
next reply other threads:[~2017-07-06 8:36 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-07-06 8:36 Chen, Farrah [this message]
2017-07-06 8:47 ` OVMF compile error Laszlo Ersek
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=1B925CC0CD9F3341B32D442251E7E1DC39097EE3@shsmsx102.ccr.corp.intel.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