From: "Laszlo Ersek" <lersek@redhat.com>
To: devel@edk2.groups.io, jacklien@qti.qualcomm.com
Subject: Re: [edk2-devel] Fail to build boot with tools code failure
Date: Tue, 21 Nov 2023 17:27:31 +0100 [thread overview]
Message-ID: <b2e4a5fb-5110-49f5-5437-20dc20a89fee@redhat.com> (raw)
In-Reply-To: <SJ0PR02MB8718BC8FB435D95596145CC5FFB0A@SJ0PR02MB8718.namprd02.prod.outlook.com>
On 11/16/23 04:46, Jackie Lien (Temp) via groups.io wrote:
> Hi team,
>
> Please help with the build error in BOOT.MXF.1.1.1. The command and log
> are listed below.
>
>
>
> Sync & build command:
>
> 1. python sync_crm.py BOOT.MXF.1.1.1-00175-Olympic-1
> 2. copy manifest to my local sync (copy
> \\snowcone\builds906\PROD\BOOT.MXF.1.1.1-00175-Olympic-1\boot_images\boot_tools\manifest\build\manifest.xml <file://snowcone/builds906/PROD/BOOT.MXF.1.1.1-00175-Olympic-1/boot_images/boot_tools/manifest/build/manifest.xml> to \\jacklien-linux\workspace\BOOT.MXF.1.1.1-00175-Olympic-1\boot_images\boot_tools\manifest\build\manifest.xml <file://jacklien-linux/workspace/BOOT.MXF.1.1.1-00175-Olympic-1/boot_images/boot_tools/manifest/build/manifest.xml>)
> 3. python buildex.py -t Olympic -v LE -r DEBUG
>
>
>
>
>
> Build log:
> build.py...
>
> : error C0DE: Tools code failure
>
> Please send email to devel@edk2.groups.io
> <mailto:devel@edk2.groups.io> for help, attaching following call stack
> trace!
>
>
>
> Traceback (most recent call last):
>
> File
> "/local/mnt/workspace/BOOT.MXF.1.1.1-00175-Olympic-1/boot_images/edk2/BaseTools/Source/Python/GenFds/GenFds.py", line 371, in GenFdsApi
>
> GenFds.GenFd('', FdfParserObj, BuildWorkSpace, ArchList)
>
> File
> "/local/mnt/workspace/BOOT.MXF.1.1.1-00175-Olympic-1/boot_images/edk2/BaseTools/Source/Python/GenFds/GenFds.py", line 510, in GenFd
>
> FdObj.GenFd()
>
> File
> "/local/mnt/workspace/BOOT.MXF.1.1.1-00175-Olympic-1/boot_images/edk2/BaseTools/Source/Python/GenFds/Fd.py", line 131, in GenFd
>
> RegionObj.AddToBuffer (FdBuffer, self.BaseAddress,
> self.BlockSizeList, self.ErasePolarity,
> GenFdsGlobalVariable.ImageBinDict, self.DefineVarDict, Flag=Flag)
>
> File
> "/local/mnt/workspace/BOOT.MXF.1.1.1-00175-Olympic-1/boot_images/edk2/BaseTools/Source/Python/GenFds/Region.py", line 134, in AddToBuffer
>
> FvObj.AddToBuffer(FvBuffer, FvBaseAddress, BlockSize, BlockNum,
> ErasePolarity, Flag=Flag)
>
> File
> "/local/mnt/workspace/BOOT.MXF.1.1.1-00175-Olympic-1/boot_images/edk2/BaseTools/Source/Python/GenFds/Fv.py", line 127, in AddToBuffer
>
> FileName = FfsFile.GenFfs(MacroDict, FvParentAddr=BaseAddress,
> IsMakefile=Flag, FvName=self.UiFvName)
>
>
> ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
>
> File
> "/local/mnt/workspace/BOOT.MXF.1.1.1-00175-Olympic-1/boot_images/edk2/BaseTools/Source/Python/GenFds/FfsInfStatement.py", line 518, in GenFfs
>
> InputSectList, InputSectAlignments =
> self.__GenComplexFileSection__(Rule, FvChildAddr, FvParentAddr,
> IsMakefile=IsMakefile)
>
>
> ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
>
> File
> "/local/mnt/workspace/BOOT.MXF.1.1.1-00175-Olympic-1/boot_images/edk2/BaseTools/Source/Python/GenFds/FfsInfStatement.py", line 969, in __GenComplexFileSection__
>
> SectList, Align = Sect.GenSection(self.OutputPath, self.ModuleGuid,
> SecIndex, self.KeyStringList, self, IsMakefile = IsMakefile)
>
>
> ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
>
> File
> "/local/mnt/workspace/BOOT.MXF.1.1.1-00175-Olympic-1/boot_images/edk2/BaseTools/Source/Python/GenFds/EfiSection.py", line 263, in GenSection
>
> ImageObj = PeImageClass (File)
>
> ^^^^^^^^^^^^^^^^^^^
>
> File
> "/local/mnt/workspace/BOOT.MXF.1.1.1-00175-Olympic-1/boot_images/edk2/BaseTools/Source/Python/Common/Misc.py", line 1638, in __init__
>
> if ByteArray.tostring() != b'PE\0\0':
>
> ^^^^^^^^^^^^^^^^^^
>
> AttributeError: 'array.array' object has no attribute 'tostring'
>
>
>
>
>
>
>
> build.py...
>
> : error 7000: Failed to execute command
>
>
>
>
>
> - Failed -
>
> Build end time: 11:15:43, Nov.16 2023
>
> Build total time: 00:00:23
>
>
>
> ERROR: buildex::Run ['python',
> '/local/mnt/workspace/BOOT.MXF.1.1.1-00175-Olympic-1/boot_images/edk2/BaseTools/Source/Python/build/build.py', '-p', 'QcomPkg/SocPkg/Olympic/LE/Core.dsc', '-j', 'QcomPkg/SocPkg/Olympic/LE/build_Core.log', '-w', '-a', 'ARM', '-b', 'DEBUG', '-t', 'CLANG100LINUX', '-D', 'BUILDROOT=/local/mnt/workspace/BOOT.MXF.1.1.1-00175-Olympic-1/boot_images', '-D', 'BOOTROOT=/local/mnt/workspace/BOOT.MXF.1.1.1-00175-Olympic-1/boot_images/boot', '-D', 'REL=DEBUG', '-D', 'PRODMODE=DEBUGMODE', '-D', 'VAR=LE', '-D', 'COMPLIER=', '-D', 'FIRSTDLL=', '-D', 'SECONDDLL=', '-D', 'XBLSEC=', '-D', 'TARGETROOT=QcomPkg/SocPkg/Olympic', '-D', 'TARGETID=SocOlympic', '-D', 'TARGETPKG=SocPkg', '-D', 'QCOMDIR=', '-D', 'BOOTTOOLS=/local/mnt/workspace/BOOT.MXF.1.1.1-00175-Olympic-1/boot_images/boot_tools', '-D', 'EDK2ROOT=/local/mnt/workspace/BOOT.MXF.1.1.1-00175-Olympic-1/boot_images/edk2', '-D', 'SECTOOLS_DIR=/pkg/sectools/glue/latest', '-D', 'SECTOOLSROOT=/pkg/sectools/glue/latest', '-D', 'COMPILER=CLANG100LINUX', '-D', 'AARCH=ARM'] Build Subprocess failed with error...
>
> None
The platform DSC file seems to be "QcomPkg/SocPkg/Olympic/LE/Core.dsc".
Presumably that exists in a vendor tree that is not open source. Without
access to the platform, the issue may be hard to reproduce or to analyze
for the BaseTools maintainers.
Laszlo
-=-=-=-=-=-=-=-=-=-=-=-
Groups.io Links: You receive all messages sent to this group.
View/Reply Online (#111564): https://edk2.groups.io/g/devel/message/111564
Mute This Topic: https://groups.io/mt/102698983/7686176
Group Owner: devel+owner@edk2.groups.io
Unsubscribe: https://edk2.groups.io/g/devel/leave/12367111/7686176/1913456212/xyzzy [rebecca@openfw.io]
-=-=-=-=-=-=-=-=-=-=-=-
prev parent reply other threads:[~2023-11-21 16:27 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-11-16 3:46 [edk2-devel] Fail to build boot with tools code failure Jackie Lien (Temp) via groups.io
2023-11-21 16:27 ` Laszlo Ersek [this message]
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=b2e4a5fb-5110-49f5-5437-20dc20a89fee@redhat.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