public inbox for devel@edk2.groups.io
 help / color / mirror / Atom feed
From: "Rebecca Cran" <rebecca@bsdio.com>
To: devel@edk2.groups.io, Guo Dong <guo.dong@intel.com>,
	Ray Ni <ray.ni@intel.com>, Sean Rhodes <sean@starlabs.systems>,
	James Lu <james.lu@intel.com>, Gua Guo <gua.guo@intel.com>
Subject: UefiPayloadPkg IA32 RELEASE/DEBUG builds fail (BdsDxe not in .dsc file)
Date: Wed, 28 Dec 2022 13:55:22 -0700	[thread overview]
Message-ID: <e3d54737-6b1d-6347-1643-de4a9ed67069@bsdio.com> (raw)

[-- Attachment #1: Type: text/plain, Size: 614 bytes --]

I noticed the IA32 builds for UefiPayloadPkg fail because BdsDxe is listed in the FDF for all architectures, but is only for X64 in the DSC.

SECTION - Building UefiPayloadPkg Package

|
PROGRESS - --Running UefiPayloadPkg: Compiler Plugin DEBUG --|
|
PROGRESS - Start time: 2022-12-28 20:39:37.793661|
|
PROGRESS - Setting up the Environment|
|
PROGRESS - Running Pre Build|
|
PROGRESS - Running Build DEBUG|
|ERROR - EDK2 #001 from : Module 
/home/gitlab-runner/builds/5XJxMJJE/0/tianocore/edk2/MdeModulePkg/Universal/BdsDxe/BdsDxe.inf 
NOT found in DSC file; Is it really a binary module? -- Rebecca Cran |

||

[-- Attachment #2: Type: text/html, Size: 1902 bytes --]

                 reply	other threads:[~2022-12-28 20:55 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=e3d54737-6b1d-6347-1643-de4a9ed67069@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