From: Prem Kumar <perry.prem@gmail.com>
To: edk2-devel@lists.01.org
Subject: Build fail using latest UDK2018
Date: Thu, 6 Dec 2018 00:07:26 +0530 [thread overview]
Message-ID: <CAG+YCe0iBGn10wdkLkB0RSZBZgXiZ6hdr0O=ZCgTrs-v-zaxrw@mail.gmail.com> (raw)
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\\MdeModulePkg\\Core\\Pei\\PeiMain\\OUTPUT\\PeiCore.uni'
next reply other threads:[~2018-12-05 18:37 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-12-05 18:37 Prem Kumar [this message]
2018-12-05 23:59 ` Build fail using latest UDK2018 Gao, Liming
2018-12-06 14:42 ` Prem Kumar
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+YCe0iBGn10wdkLkB0RSZBZgXiZ6hdr0O=ZCgTrs-v-zaxrw@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