From: "Chen, Farrah" <farrah.chen@intel.com>
To: "devel@edk2.groups.io" <devel@edk2.groups.io>
Cc: "Hao, Xudong" <xudong.hao@intel.com>
Subject: ovmf build fail with gcc 4.8.5
Date: Tue, 13 Aug 2019 01:13:13 +0000 [thread overview]
Message-ID: <1B925CC0CD9F3341B32D442251E7E1DC3E3115C3@SHSMSX104.ccr.corp.intel.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 2671 bytes --]
Hi,
When build ovmf with the latest two commits of master branch, we meet error on Red Hat 7.6 with gcc version 4.8.5, but succeed on Red Hat 8.0 with gcc version 8.2.1.
Steps:
git clone https://github.com/tianocore/edk2.git
cd edk2
git submodule init
git submodule update -recursive
OvmfPkg/build.sh -a X64 -n 64
Error log:
.......
/home/build/kvm_build/nightly/kvm_qemu/kvm-next-20190813010558-a738b5e7-5e7bcdcf/edk2/MdeModulePkg/Core/DxeIplPeim/X64/VirtualMemory.c:641:50: error: 'PageMapLevel5Entry' may be used uninitialized in this function [-Werror=maybe-uninitialized]
PAGE_MAP_AND_DIRECTORY_POINTER *PageMapLevel5Entry;
^
cc1: all warnings being treated as errors
"objcopy" /home/build/kvm_build/nightly/kvm_qemu/kvm-next-20190813010558-a738b5e7-5e7bcdcf/edk2/Build/OvmfX64/DEBUG_GCC48/X64/MdeModulePkg/Bus/Pci/PciHostBridgeDxe/PciHostBridgeDxe/DEBUG/PciHostBridgeDxe.dll
"GenFw" -e UEFI_DRIVER -o /home/build/kvm_build/nightly/kvm_qemu/kvm-next-20190813010558-a738b5e7-5e7bcdcf/edk2/Build/OvmfX64/DEBUG_GCC48/X64/OvmfPkg/XenBusDxe/XenBusDxe/OUTPUT/XenBusDxe.efi /home/build/kvm_build/nightly/kvm_qemu/kvm-next-20190813010558-a738b5e7-5e7bcdcf/edk2/Build/OvmfX64/DEBUG_GCC48/X64/OvmfPkg/XenBusDxe/XenBusDxe/DEBUG/XenBusDxe.dll
make: *** [/home/build/kvm_build/nightly/kvm_qemu/kvm-next-20190813010558-a738b5e7-5e7bcdcf/edk2/Build/OvmfX64/DEBUG_GCC48/X64/MdeModulePkg/Core/DxeIplPeim/DxeIpl/OUTPUT/X64/VirtualMemory.obj] Error 1
cp -f /home/build/kvm_build/nightly/kvm_qemu/kvm-next-20190813010558-a738b5e7-5e7bcdcf/edk2/Build/OvmfX64/DEBUG_GCC48/X64/OvmfPkg/XenBusDxe/XenBusDxe/OUTPUT/XenBusDxe.efi /home/build/kvm_build/nightly/kvm_qemu/kvm-next-20190813010558-a738b5e7-5e7bcdcf/edk2/Build/OvmfX64/DEBUG_GCC48/X64/OvmfPkg/XenBusDxe/XenBusDxe/DEBUG
build.py...
: error 7000: Failed to execute command
make tbuild [/home/build/kvm_build/nightly/kvm_qemu/kvm-next-20190813010558-a738b5e7-5e7bcdcf/edk2/Build/OvmfX64/DEBUG_GCC48/X64/MdeModulePkg/Core/DxeIplPeim/DxeIpl]
build.py...
: error F002: Failed to build module
/home/build/kvm_build/nightly/kvm_qemu/kvm-next-20190813010558-a738b5e7-5e7bcdcf/edk2/MdeModulePkg/Core/DxeIplPeim/DxeIpl.inf [X64, GCC48, DEBUG]
- Failed -
Build end time: 08:46:33, Aug.13 2019
Build total time: 00:01:15
GCC:
gcc --version
gcc (GCC) 4.8.5 20150623 (Red Hat 4.8.5-36)
Copyright (C) 2015 Free Software Foundation, Inc.
This is free software; see the source for copying conditions. There is NO
warranty; not even for MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE.
Thanks,
Fan
[-- Attachment #2: Type: text/html, Size: 6925 bytes --]
next reply other threads:[~2019-08-13 1:13 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-08-13 1:13 Chen, Farrah [this message]
2019-08-13 12:23 ` [edk2-devel] ovmf build fail with gcc 4.8.5 Laszlo Ersek
2019-08-16 1:57 ` 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=1B925CC0CD9F3341B32D442251E7E1DC3E3115C3@SHSMSX104.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