public inbox for devel@edk2.groups.io
 help / color / mirror / Atom feed
From: "David F." <df7729@gmail.com>
To: edk2 developers list <edk2-devel@lists.01.org>
Subject: Re: Latest SVN Update Breaks Link
Date: Sat, 1 Dec 2018 22:49:31 -0800	[thread overview]
Message-ID: <CAGRSmLvsgaW+XtrCnwA8Ek+2u4fFGUBwL2h0UfbPp744_NH3gw@mail.gmail.com> (raw)
In-Reply-To: <CAGRSmLsh=hC8kNqaPFLCNiGvaSZOaxYeb9e1s_xNQtehmD8-5w@mail.gmail.com>

So digging in I saw there were in the .S files, and didn't look like
building.  So, stumbling around, I finally looked at the Conf templates and
saw new entries for nasm and such.  I went through the process of updating
all my tool defs, setting up the PYTHON_HOME and NASM_PREFIX directories,
and seems to build now except my own batch file didn't do what it normally
does and give me a SUCCESS or FAILURE message so I know if all the nonsense
on the screen should be looked at or not.   So looking a bit more "where
build" I see it's not using a batch file which will break everyone's batch
files since a "call" is now needed.  I think the errorlevel is returned
from the call so it's sample to add call.

In short, you'll need to update build Conf if updating from older version
and adjust your batch files to use "call" for build.

On Sat, Dec 1, 2018 at 7:37 PM David F. <df7729@gmail.com> wrote:

> Hi,
>
> My last SVN update was from July 2018.   I just did one Yesterday now my
> build breaks linking with:
>
> LibC.lib(Main.obj) : error LNK2001: unresolved external symbol SetJump
> BaseLib.lib(LongJump.obj) : error LNK2001: unresolved external symbol
> InternalLongJump
>
> The build is using VS2008 and the target is for X64.
>
> Any ideas?
>
>
>
>
>


  reply	other threads:[~2018-12-02  6:49 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-12-02  3:37 Latest SVN Update Breaks Link David F.
2018-12-02  6:49 ` David F. [this message]
2018-12-03  0:25   ` 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=CAGRSmLvsgaW+XtrCnwA8Ek+2u4fFGUBwL2h0UfbPp744_NH3gw@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