public inbox for devel@edk2.groups.io
 help / color / mirror / Atom feed
From: "Gao, Liming" <liming.gao@intel.com>
To: Bhupesh Sharma <bhupesh.sharma@nxp.com>,
	"edk2-devel@lists.01.org" <edk2-devel@lists.01.org>
Subject: Re: EDK2 master build failure
Date: Fri, 18 Nov 2016 05:14:48 +0000	[thread overview]
Message-ID: <4A89E2EF3DFEDB4C8BFDE51014F606A14B4B6C0C@shsmsx102.ccr.corp.intel.com> (raw)
In-Reply-To: <AM4PR0401MB2289538842CBAE08EB7D550C88B10@AM4PR0401MB2289.eurprd04.prod.outlook.com>

In Misc.py, it import string class. But, in the same directory, there is source file String.py. Seemly, python interpreter wrongly imports String.py and cause this issue. This issue may happen on the case insensitive file system. 

We meet with such issue before. We set up virtual machine on windows OS to run Linux build, edk2 source code is downloaded in windows OS and shared to virtual linux machine, then do linux build will cause such issue. To avoid it, we download edk2 source code in Linux machine and build them pass. 

Thanks
Liming
> -----Original Message-----
> From: edk2-devel [mailto:edk2-devel-bounces@lists.01.org] On Behalf Of
> Bhupesh Sharma
> Sent: Friday, November 18, 2016 4:12 AM
> To: edk2-devel@lists.01.org
> Subject: [edk2] EDK2 master build failure
> 
> Hi EDK2 experts,
> 
> I have just rebased my code on the latest EDK2 master branch and now when
> I am trying to compile the same
> I am getting the following errors (for my ARMv8 build):
> 
> # ./build.sh RELEASE clean; ./build.sh RELEASE
> ..........................................
> Welcome to LS1043A UEFI Build environment
> ..........................................
> Cleaning up the build directory '../../../../Build/LS1043aRdb/'..
> ..........................................
> Welcome to LS1043A UEFI Build environment
> ..........................................
> Initializing workspace
> Loading previous configuration from /media/sf_VBox-
> Share/LS1043A/edk2/Conf/BuildEnv.sh
> WORKSPACE: /media/sf_VBox-Share/LS1043A/edk2
> EDK_TOOLS_PATH: /media/sf_VBox-Share/LS1043A/edk2/BaseTools
> CONF_PATH: /media/sf_VBox-Share/LS1043A/edk2/Conf
> Copying $EDK_TOOLS_PATH/Conf/tools_def.template
>      to /media/sf_VBox-Share/LS1043A/edk2/Conf/tools_def.txt
> Build environment: Linux-4.2.0-27-generic-x86_64-with-Ubuntu-14.04-trusty
> Build start time: 01:19:30, Nov.18 2016
> 
> WORKSPACE        = /media/sf_VBox-Share/LS1043A/edk2
> ECP_SOURCE       = /media/sf_VBox-
> Share/LS1043A/edk2/EdkCompatibilityPkg
> EDK_SOURCE       = /media/sf_VBox-
> Share/LS1043A/edk2/EdkCompatibilityPkg
> EFI_SOURCE       = /media/sf_VBox-
> Share/LS1043A/edk2/EdkCompatibilityPkg
> EDK_TOOLS_PATH   = /media/sf_VBox-Share/LS1043A/edk2/BaseTools
> CONF_PATH        = /media/sf_VBox-Share/LS1043A/edk2/Conf
> 
> 
> Architecture(s)  = AARCH64
> Build target     = RELEASE
> Toolchain        = GCC49
> 
> Active Platform          = /media/sf_VBox-
> Share/LS1043A/edk2/OpenPlatformPkg/Platforms/Nxp/LS1043aRdb/LS1043a
> RdbPkg.dsc
> Flash Image Definition   = /media/sf_VBox-
> Share/LS1043A/edk2/OpenPlatformPkg/Platforms/Nxp/LS1043aRdb/LS1043a
> RdbPkg.fdf
> 
> Processing meta-data .......
> 
> 
> build.py...
>  : error C0DE: Unknown fatal error when processing [/media/sf_VBox-
> Share/LS1043A/edk2/MdePkg/MdePkg.dec]
> 
> (Please send email to edk2-devel@lists.01.org for help, attaching following
> call stack trace!)
> 
> (Python 2.7.6 on linux2) Traceback (most recent call last):
>   File "/media/sf_VBox-
> Share/LS1043A/edk2/BaseTools/BinWrappers/PosixLike/../../Source/Python
> /build/build.py", line 2276, in Main
>     MyBuild.Launch()
>   File "/media/sf_VBox-
> Share/LS1043A/edk2/BaseTools/BinWrappers/PosixLike/../../Source/Python
> /build/build.py", line 2028, in Launch
>     self._MultiThreadBuildPlatform()
>   File "/media/sf_VBox-
> Share/LS1043A/edk2/BaseTools/BinWrappers/PosixLike/../../Source/Python
> /build/build.py", line 1823, in _MultiThreadBuildPlatform
>     self.Progress
>   File "/media/sf_VBox-
> Share/LS1043A/edk2/BaseTools/Source/Python/AutoGen/AutoGen.py", line
> 176, in __new__
>     if not AutoGenObject._Init(Workspace, MetaFile, Target, Toolchain, Arch,
> *args, **kwargs):
>   File "/media/sf_VBox-
> Share/LS1043A/edk2/BaseTools/Source/Python/AutoGen/AutoGen.py", line
> 464, in _Init
>     for key in BuildData.Pcds:
>   File "/media/sf_VBox-
> Share/LS1043A/edk2/BaseTools/Source/Python/Workspace/WorkspaceData
> base.py", line 2469, in _GetPcds
>     self._Pcds.update(self._GetPcd(MODEL_PCD_FEATURE_FLAG))
>   File "/media/sf_VBox-
> Share/LS1043A/edk2/BaseTools/Source/Python/Workspace/WorkspaceData
> base.py", line 2583, in _GetPcd
>     if TokenSpaceGuid not in self.Guids:
>   File "/media/sf_VBox-
> Share/LS1043A/edk2/BaseTools/Source/Python/Workspace/WorkspaceData
> base.py", line 2368, in _GetGuids
>     Value = GuidValue(CName, self.Packages, self.MetaFile.Path)
>   File "/media/sf_VBox-
> Share/LS1043A/edk2/BaseTools/Source/Python/Common/Misc.py", line 804,
> in GuidValue
>     GuidKeys = P.Guids.keys()
>   File "/media/sf_VBox-
> Share/LS1043A/edk2/BaseTools/Source/Python/Workspace/WorkspaceData
> base.py", line 1482, in _GetGuid
>     RecordList = self._RawData[MODEL_EFI_GUID, self._Arch]
>   File "/media/sf_VBox-
> Share/LS1043A/edk2/BaseTools/Source/Python/Workspace/MetaFileParser.
> py", line 239, in __getitem__
>     self.Start()
>   File "/media/sf_VBox-
> Share/LS1043A/edk2/BaseTools/Source/Python/Workspace/MetaFileParser.
> py", line 1671, in Start
>     self._SectionParser[self._SectionType[0]](self)
>   File "/media/sf_VBox-
> Share/LS1043A/edk2/BaseTools/Source/Python/Workspace/MetaFileParser.
> py", line 43, in MacroParser
>     Parser(self)
>   File "/media/sf_VBox-
> Share/LS1043A/edk2/BaseTools/Source/Python/Workspace/MetaFileParser.
> py", line 1896, in _PcdParser
>     IsValid, Cause = CheckPcdDatum(ValueList[1], ValueList[0])
>   File "/media/sf_VBox-
> Share/LS1043A/edk2/BaseTools/Source/Python/Common/Misc.py", line
> 1639, in CheckPcdDatum
>     Printset = set(string.printable)
> AttributeError: 'module' object has no attribute 'printable'
> 
> 
> - Failed -
> Build end time: 01:19:43,
> 
> Is this a known issue?
> 
> Regards,
> Bhupesh
> _______________________________________________
> edk2-devel mailing list
> edk2-devel@lists.01.org
> https://lists.01.org/mailman/listinfo/edk2-devel


  reply	other threads:[~2016-11-18  5:14 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-11-17 20:11 EDK2 master build failure Bhupesh Sharma
2016-11-18  5:14 ` Gao, Liming [this message]
2016-11-18  9:51   ` Bhupesh Sharma

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=4A89E2EF3DFEDB4C8BFDE51014F606A14B4B6C0C@shsmsx102.ccr.corp.intel.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