From: "Gao, Liming" <liming.gao@intel.com>
To: "Foster, Matthew I" <matthew.i.foster@intel.com>,
wang xiaofeng <winggundum82@163.com>,
"edk2-devel@lists.01.org" <edk2-devel@lists.01.org>
Subject: Re: UnicodeError: UTF-16 stream does not start with BOM error when update from UDK2015 to latest Github trunk
Date: Thu, 1 Sep 2016 01:07:00 +0000 [thread overview]
Message-ID: <4A89E2EF3DFEDB4C8BFDE51014F606A14B3E0F16@shsmsx102.ccr.corp.intel.com> (raw)
In-Reply-To: <3E72E29DAAE6E94BB0236F004CFB699B7884E150@fmsmsx107.amr.corp.intel.com>
Matthew:
The temp way is to convert all uni files to UTF16 format. You can use edk2 trunk BaseTools\Scripts\ConvertUni.py to convert uni file format.
Thanks
Liming
> -----Original Message-----
> From: Foster, Matthew I
> Sent: Thursday, September 01, 2016 3:04 AM
> To: Gao, Liming <liming.gao@intel.com>; wang xiaofeng
> <winggundum82@163.com>; edk2-devel@lists.01.org
> Subject: RE: [edk2] UnicodeError: UTF-16 stream does not start with BOM
> error when update from UDK2015 to latest Github trunk
>
> Is there a way to work-around this error without having to upgrade to the
> newest BaseTools?
>
> -----Original Message-----
> From: edk2-devel [mailto:edk2-devel-bounces@lists.01.org] On Behalf Of
> Gao, Liming
> Sent: Monday, February 29, 2016 11:08 PM
> To: wang xiaofeng <winggundum82@163.com>; edk2-devel@lists.01.org
> Subject: Re: [edk2] UnicodeError: UTF-16 stream does not start with BOM
> error when update from UDK2015 to latest Github trunk
>
> Do you get the latest BaseTools binary win32?
>
> > -----Original Message-----
> > From: edk2-devel [mailto:edk2-devel-bounces@lists.01.org] On Behalf Of
> > wang xiaofeng
> > Sent: Tuesday, March 01, 2016 2:04 PM
> > To: edk2-devel@lists.01.org
> > Subject: [edk2] UnicodeError: UTF-16 stream does not start with BOM
> > error when update from UDK2015 to latest Github trunk
> >
> > Hi All Edk2 developer,
> > I meet a build error when update code from UDK2015 to latest
> > Github trunk. Do anyone meet similar issue before? I sync NetworkPkg
> > seperately to latest code but find the following error:
> >
> >
> > build...
> > : error C0DE: Unknown fatal error when processing
> > [e:\code\cl174\NetworkPkg\Ip6Dxe\Ip6Dxe.inf]
> > (Please send email to edk2-devel@lists.sourceforge.net for help,
> > attaching following call stack trace!)
> >
> >
> > (Python 2.7.3 on win32) Traceback (most recent call last):
> > File "build.py", line 2032, in Main
> > File "build.py", line 1788, in Launch
> > File "build.py", line 1618, in _MultiThreadBuildPlatform
> > File
> >
> "c:\Users\Public\Documents\BuildPool\BaseTools\build\Source\Python\Aut
> > oGen\AutoGen.py", line 3446, in CreateCodeFile
> > File
> >
> "c:\Users\Public\Documents\BuildPool\BaseTools\build\Source\Python\Aut
> > oGen\AutoGen.py", line 2854, in _GetAutoGenFileList
> > File
> >
> "c:\Users\Public\Documents\BuildPool\BaseTools\build\Source\Python\Aut
> > oGen\GenC.py", line 1552, in CreateCode
> > File
> >
> "c:\Users\Public\Documents\BuildPool\BaseTools\build\Source\Python\Aut
> > oGen\GenC.py", line 1456, in CreateUnicodeStringCode
> > File
> >
> "c:\Users\Public\Documents\BuildPool\BaseTools\build\Source\Python\Aut
> > oGen\StrGather.py", line 600, in GetStringFiles
> > File
> >
> "c:\Users\Public\Documents\BuildPool\BaseTools\build\Source\Python\Aut
> > oGen\UniClassObject.py", line 203, in __init__
> > File
> >
> "c:\Users\Public\Documents\BuildPool\BaseTools\build\Source\Python\Aut
> > oGen\UniClassObject.py", line 463, in LoadUniFiles
> > File
> >
> "c:\Users\Public\Documents\BuildPool\BaseTools\build\Source\Python\Aut
> > oGen\UniClassObject.py", line 377, in LoadUniFile
> > File
> >
> "c:\Users\Public\Documents\BuildPool\BaseTools\build\Source\Python\Aut
> > oGen\UniClassObject.py", line 318, in PreProcess
> > File "C:\Python\32-bit\2.7\lib\codecs.py", line 684, in next
> > File "C:\Python\32-bit\2.7\lib\codecs.py", line 615, in next
> > File "C:\Python\32-bit\2.7\lib\codecs.py", line 530, in readline
> > File "C:\Python\32-bit\2.7\lib\codecs.py", line 477, in read
> > File "C:\Python\32-bit\2.7\lib\encodings\utf_16.py", line 112, in
> > decode
> > UnicodeError: UTF-16 stream does not start with BOM
> > _______________________________________________
> > edk2-devel mailing list
> > edk2-devel@lists.01.org
> > https://lists.01.org/mailman/listinfo/edk2-devel
> _______________________________________________
> edk2-devel mailing list
> edk2-devel@lists.01.org
> https://lists.01.org/mailman/listinfo/edk2-devel
prev parent reply other threads:[~2016-09-01 1:07 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <516d6a57.6ba8.15330c71162.Coremail.winggundum82@163.com>
[not found] ` <4A89E2EF3DFEDB4C8BFDE51014F606A114BC1060@SHSMSX101.ccr.corp.intel.com>
2016-08-31 19:04 ` UnicodeError: UTF-16 stream does not start with BOM error when update from UDK2015 to latest Github trunk Foster, Matthew I
2016-09-01 1:07 ` Gao, Liming [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=4A89E2EF3DFEDB4C8BFDE51014F606A14B3E0F16@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