public inbox for devel@edk2.groups.io
 help / color / mirror / Atom feed
From: "Rebecca Cran" <rebecca@bsdio.com>
To: devel@edk2.groups.io, Laszlo Ersek <lersek@redhat.com>,
	Ard Biesheuvel <ardb+tianocore@kernel.org>,
	Jordan Justen <jordan.l.justen@intel.com>
Subject: OvmfPkgIa32X64.dsc is broken: OvmfPkg/Sec/SecMain.inf NOT found in DSC file; Is it really a binary module?
Date: Wed, 16 Jun 2021 22:15:38 -0600	[thread overview]
Message-ID: <f98e2c77-8068-378f-214a-7e9f6a74f614@bsdio.com> (raw)

Is OvmfPkg/OvmfPkgIa32X64.dsc still supposed to work after the recent 
changes in OvmfPkg? I realized it's currently broken.


bcran@photon:~/src/uefi/edk2> build -p OvmfPkg/OvmfPkgIa32X64.dsc -a X64 
-t GCC5 -b RELEASE
Build environment: Linux-5.12.9-1-default-x86_64-with-glibc2.2.5
Build start time: 22:11:28, Jun.16 2021

WORKSPACE        = /home/bcran/src/uefi/edk2
EDK_TOOLS_PATH   = /home/bcran/src/uefi/edk2/BaseTools
CONF_PATH        = /home/bcran/src/uefi/edk2/Conf
PYTHON_COMMAND   = /usr/bin/python3.8


Processing meta-data
.Architecture(s)  = X64
Build target     = RELEASE
Toolchain        = GCC5

Active Platform          = 
/home/bcran/src/uefi/edk2/OvmfPkg/OvmfPkgIa32X64.dsc


build.py...
  : error F001: Module /home/bcran/src/uefi/edk2/OvmfPkg/Sec/SecMain.inf 
NOT found in DSC file; Is it really a binary module?



- Failed -
Build end time: 22:11:29, Jun.16 2021
Build total time: 00:00:01


-- 
Rebecca Cran



             reply	other threads:[~2021-06-17  4:15 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-06-17  4:15 Rebecca Cran [this message]
2021-06-20 13:51 ` [edk2-devel] OvmfPkgIa32X64.dsc is broken: OvmfPkg/Sec/SecMain.inf NOT found in DSC file; Is it really a binary module? Lendacky, Thomas

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=f98e2c77-8068-378f-214a-7e9f6a74f614@bsdio.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