[Bug]: Build fails without a reason

[jeremybobbin]

Is there an existing issue for this?

• I have searched existing issues

Bug Type

• Firmware
• Tool
• Unit Test

What packages are impacted?

MdeModulePkg

Which targets are impacted by this bug?

DEBUG

Current Behavior

I run build -a X64 -p ./MdeModulePkg/MdeModulePkg.dsc and I see the following:

Build environment: Linux-6.19.9-arch1-1-x86_64-with-glibc2.43
SOURCE_DATE_EPOCH not set - using 1773794009
Build start time: 17:33:29, Mar.17 2026

WORKSPACE        = /home/jer/edk2
EDK_TOOLS_PATH   = /home/jer/edk2/BaseTools
CONF_PATH        = /home/jer/edk2/Conf
PYTHON_COMMAND   = python3


Processing meta-data .
Architecture(s)  = X64
Build target     = DEBUG
Toolchain        = VS2022

Active Platform          = /home/jer/edk2/MdeModulePkg/MdeModulePkg.dsc


- Failed -
Build end time: 17:33:30, Mar.17 2026
Build total time: 00:00:01

Expected Behavior

I believe I should see a line like:

build.py...
 : error XXXX: ...

Steps To Reproduce

I ran . edksetup.sh and then ran build -a X64 -p ./MdeModulePkg/MdeModulePkg.dsc

Build Environment

- OS(s): Arch
- Tool Chain(s): GCC

Version Information

Commit: 35c03c1c9

Urgency

Low

Are you going to fix this?

I will fix it

Do you need maintainer feedback?

No maintainer feedback needed

Anything else?

No response

[leiflindholm]

I agree that the lack of error message isn't great, but you appear to be trying to build on Linux using the Visual Studio 2022 toolchain profile. Try adding -t GCC or -t CLANGDWARF to your build command line.

[Damien-Chen]

Yes, @leiflindholm is right.edk2 use Conf/target.template to generate target.txt. By defauly the TOOL_CHAIN_TAG is set to VS2022. Eeither you modify it to use GCC or add build flag in command may resolve this problem

[jeremybobbin]

Thanks! Switching to GCC worked.