From: "Laszlo Ersek" <lersek@redhat.com>
To: "Gao, Liming" <liming.gao@intel.com>,
"devel@edk2.groups.io" <devel@edk2.groups.io>,
"df7729@gmail.com" <df7729@gmail.com>
Subject: Re: [edk2-devel] BuildTools Broken
Date: Tue, 26 May 2020 16:23:55 +0200 [thread overview]
Message-ID: <1a5ce1b8-5905-fa3c-8269-215dba73526e@redhat.com> (raw)
In-Reply-To: <SN6PR11MB3197C8C4C5291160C0EE378780B00@SN6PR11MB3197.namprd11.prod.outlook.com>
On 05/26/20 15:05, Gao, Liming wrote:
> To update Conf, you can type edksetup.bat Reconfig command, and then try build again.
Ah indeed, thank you for the reminder!
Laszlo
>> -----Original Message-----
>> From: devel@edk2.groups.io <devel@edk2.groups.io> On Behalf Of Laszlo Ersek
>> Sent: Tuesday, May 26, 2020 8:43 PM
>> To: devel@edk2.groups.io; df7729@gmail.com
>> Subject: Re: [edk2-devel] BuildTools Broken
>>
>> On 05/25/20 18:55, David F. wrote:
>>> Last night through the forums I sent a problem with NMAKE U1073 trying
>>> to build. Some things built fine, but not others. I think my
>>> original message with all the details is still awaiting moderation.
>>> To follow up on that. I simply renamed BaseTools and restored the
>>> other one I had before updating back (which was older one where
>>> build.exe is Nov 29 2018), but now it starts building fine. Only
>>> breaks on some new items like longjump.nasm can't find nasm.inc which
>>> didn't exist back in the version I had.
>>
>> Your "Conf" directory was likely out-of-date, please delete it and let
>> edksetup.sh re-populate it from under BaseTools/Conf.
>>
>> An earlier report about the (apparently) same "Nasm.inc" symptom:
>>
>> https://bugzilla.tianocore.org/show_bug.cgi?id=2719
>>
>> Thanks
>> Laszlo
>>
>>> So I'll have to figure that
>>> out, but I guess I'll used the old BaseTools since the new one doesn't
>>> work either because I need to do something or it needs to be fixed.
>>> Building on Win10 but all that is in the other message. Using email
>>> now to see if it goes through faster.
>>>
>>>
>>>
>>
>>
>>
>
prev parent reply other threads:[~2020-05-26 14:24 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-05-25 16:55 BuildTools Broken df7729
2020-05-26 12:43 ` [edk2-devel] " Laszlo Ersek
2020-05-26 13:05 ` Liming Gao
2020-05-26 14:23 ` Laszlo Ersek [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=1a5ce1b8-5905-fa3c-8269-215dba73526e@redhat.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