public inbox for devel@edk2.groups.io
 help / color / mirror / Atom feed
From: Prem Kumar <perry.prem@gmail.com>
To: liming.gao@intel.com
Cc: edk2-devel@lists.01.org
Subject: Re: Build fail using latest UDK2018
Date: Thu, 6 Dec 2018 20:12:03 +0530	[thread overview]
Message-ID: <CAG+YCe3gz5RQMqUcMaRN9Ha1kDCnaNfsE8DhN_0+jjLNMU=t4A@mail.gmail.com> (raw)
In-Reply-To: <4A89E2EF3DFEDB4C8BFDE51014F606A14E3845DB@SHSMSX104.ccr.corp.intel.com>

Recreating this issue is simple..

   1. Fresh build either NT32Pkg for x64 bit
   2. Launch NT32 simulator
   3. Close Nt32 simulator
   4. And try build again for x64 bit
   5. It will throw this build error.

I've even tried to delete folder PeiMain from Build folder.. then it gives
error for another. But it build success when I delete entire build folder.

Configuration used:

   1. Visual Studio 2016
   2. Nt32Pkg
   3. UDK2018


On Thu, Dec 6, 2018 at 5:29 AM Gao, Liming <liming.gao@intel.com> wrote:

> How reproduce this issue? Could you list your step?
>
> >-----Original Message-----
> >From: edk2-devel [mailto:edk2-devel-bounces@lists.01.org] On Behalf Of
> >Prem Kumar
> >Sent: Thursday, December 06, 2018 2:37 AM
> >To: edk2-devel@lists.01.org
> >Subject: [edk2] Build fail using latest UDK2018
> >
> >Hi All,
> > When I try to build UDK2018 package I'm facing below build error.
> >
> >*Note:*
> >  When I delete the build folder the same build error is not happening.
> >  The same build error is not happening when build is happening for first
> >time.
> >
> >Any pointers is appreciated.
> >
> >
> >build.py...
> > : error C0DE: Unknown fatal error when processing
> >[c:\myworkspace\MdeModulePkg\Core\Pei\PeiMain.inf]
> >
> >(Please send email to edk2-devel@lists.01.org for help, attaching
> following
> >call stack trace!)
> >
> >(Python 2.7.14 on win32) Traceback (most recent call last):
> >  File "C:\myworkspace\BaseTools\Source\Python\build\build.py", line 2494,
> >in Main
> >    MyBuild.Launch()
> >  File "C:\myworkspace\BaseTools\Source\Python\build\build.py", line 2227,
> >in Launch
> >    self._MultiThreadBuildPlatform()
> >  File "C:\myworkspace\BaseTools\Source\Python\build\build.py", line 2100,
> >in _MultiThreadBuildPlatform
> >    self.CreateAsBuiltInf()
> >  File "C:\myworkspace\BaseTools\Source\Python\build\build.py", line 2239,
> >in CreateAsBuiltInf
> >    Module.CreateAsBuiltInf()
> >  File "C:\myworkspace\BaseTools\Source\Python\AutoGen\AutoGen.py",
> >line
> >3617, in CreateAsBuiltInf
> >    shutil.copy2(UNIFile, self.OutputDir)
> >  File "C:\Python27\lib\shutil.py", line 144, in copy2
> >    copyfile(src, dst)
> >  File "C:\Python27\lib\shutil.py", line 97, in copyfile
> >    with open(dst, 'wb') as fdst:
> >IOError: [Errno 13] Permission denied:
> >'c:\\myworkspaceBuild\\NT32X64\\DEBUG_VS2015x86\\X64\\MdeModulePk
> >g\\Core\\Pei\\PeiMain\\OUTPUT\\PeiCore.uni'
> >_______________________________________________
> >edk2-devel mailing list
> >edk2-devel@lists.01.org
> >https://lists.01.org/mailman/listinfo/edk2-devel
>


  reply	other threads:[~2018-12-06 14:42 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-12-05 18:37 Build fail using latest UDK2018 Prem Kumar
2018-12-05 23:59 ` Gao, Liming
2018-12-06 14:42   ` Prem Kumar [this message]
2018-12-06 14:53     ` Gao, Liming
2018-12-06 14:56       ` Prem Kumar
2018-12-06 15:02         ` Gao, Liming

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='CAG+YCe3gz5RQMqUcMaRN9Ha1kDCnaNfsE8DhN_0+jjLNMU=t4A@mail.gmail.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