From: df7729@gmail.com
To: devel@edk2.groups.io
Subject: BuildTools Broken
Date: Mon, 25 May 2020 09:55:38 -0700 [thread overview]
Message-ID: <CAGRSmLtGjRrijC-Mm2BRcgxEvL5qbt-f2+YrDMMBzmEWDjgBzA@mail.gmail.com> (raw)
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. 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.
next reply other threads:[~2020-05-25 16:55 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-05-25 16:55 df7729 [this message]
2020-05-26 12:43 ` [edk2-devel] BuildTools Broken Laszlo Ersek
2020-05-26 13:05 ` Liming Gao
2020-05-26 14:23 ` Laszlo Ersek
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=CAGRSmLtGjRrijC-Mm2BRcgxEvL5qbt-f2+YrDMMBzmEWDjgBzA@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