Hello Liming, That makes sense, though more experimentation shows the problem is not so simple.
d:\uefi\x\edk2: FspApiEntry.obj : fatal error LNK1143: invalid or corrupt file: no symbol for COMDAT section 0x1D d:\uefi\xx\edk2: LIB : fatal error LNK1000: Internal error during BuildLibrary d:\uefi\xxx\edk2: LIB : fatal error LNK1000: Internal error during BuildLibrary d:\uefi\xxxx\edk2: LIB : fatal error LNK1000: Internal error during BuildLibrary d:\uefi\xxxxx\edk2: LIB : fatal error LNK1000: Internal error during BuildLibrary d:\uefi\xxxxxx\edk2: FspApiEntry.obj : fatal error LNK1143: invalid or corrupt file: no symbol for COMDAT section 0x1C d:\uefi\xxxxxxx\edk2: FspApiEntry.obj : fatal error LNK1143: invalid or corrupt file: no symbol for COMDAT section 0x1C d:\uefi\xxxxxxxx\edk2: successful build d:\uefi\xxxxxxxxx\edk2: FspApiEntry.obj : fatal error LNK1143: invalid or corrupt file: no symbol for COMDAT section 0x50 d:\uefi\xxxxxxxxxx\edk2: FspApiEntry.obj : fatal error LNK1143: invalid or corrupt file: no symbol for COMDAT section 0x50 d:\uefi\xxxxxxxxxxx\edk2: successful build The build passes or fails depending on path length. Maybe this old tool chain has a problem relating to long file names. The command line used for this experiment look like: build.exe -p D:\uefi\ xxxxxxxx\edk2\IntelFspPkg\IntelFspPkg.dsc -b DEBUG -t DDK3790 -a IA32 -n 16 Thanks, Scott -----Original Message----- From: Gao, Liming [mailto:[email protected]] Sent: Monday, September 15, 2014 09:25 AM To: [email protected] Subject: Re: [edk2] [patch 1/5] IntelFspPkg: fix build failure when DDK3790 tool chain is used Scott: MdePkg BaseLib Assemelby code has no such issue. This issue may be the code issue. I suggest we fix the assemble code instead of modify assembler option. Thanks Liming -----Original Message----- From: Scott Duplichan [mailto:[email protected]] Sent: Monday, September 15, 2014 12:03 PM To: [email protected] Subject: [edk2] [patch 1/5] IntelFspPkg: fix build failure when DDK3790 tool chain is used IntelFspPkg: fix build failure when DDK3790 tool chain is used. The build fails due to link error LNK1143, "invalid or corrupt file". Avoid this error by removing /Zd /Zi from IntelFspPkg DDK3790 ML command line. This change allows building IntelFspPkg with DDK3790 tool chain, but without source level debugging information for asm files. If source level debugging for Intel FSP asm files is needed, use a different Microsoft tool chain. Contributed-under: TianoCore Contribution Agreement 1.0 Signed-off-by: Scott Duplichan <[email protected]> -- ------------------------------------------------------------------------------ Want excitement? Manually upgrade your production database. When you want reliability, choose Perforce Perforce version control. Predictably reliable. http://pubads.g.doubleclick.net/gampad/clk?id=157508191&iu=/4140/ostg.clktrk _______________________________________________ edk2-devel mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/edk2-devel ------------------------------------------------------------------------------ Want excitement? Manually upgrade your production database. When you want reliability, choose Perforce. Perforce version control. Predictably reliable. http://pubads.g.doubleclick.net/gampad/clk?id=157508191&iu=/4140/ostg.clktrk _______________________________________________ edk2-devel mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/edk2-devel
