From: Programmingkid <programmingkidx@gmail.com>
To: Peter Maydell <peter.maydell@linaro.org>
Cc: Dan Streetman <ddstreet@canonical.com>,
QEMU Developers <qemu-devel@nongnu.org>
Subject: Re: Makefile has local changes that will be overwritten
Date: Mon, 1 Feb 2021 10:30:25 -0500 [thread overview]
Message-ID: <E9865C2F-68A9-404F-896C-09C2A78C51A3@gmail.com> (raw)
In-Reply-To: <CAFEAcA_m3vbjh42_tox4h_9wS_BSEad=nJrc=v_it01FxVV=EQ@mail.gmail.com>
> On Feb 1, 2021, at 9:52 AM, Peter Maydell <peter.maydell@linaro.org> wrote:
>
> On Mon, 1 Feb 2021 at 14:49, Dan Streetman <ddstreet@canonical.com> wrote:
>>
>> On Mon, Feb 1, 2021 at 9:23 AM Programmingkid <programmingkidx@gmail.com> wrote:
>>>
>>> When trying to build QEMU I see this error:
>>>
>>> error: Your local changes to the following files would be overwritten by checkout:
>>> Makefile
>>> Please commit your changes or stash them before you switch branches.
>>> Aborting
>>>
>>> What I do to see this error:
>>> ./configure --target-list=i386-softmmu
>>
>> Sorry, I don't see that error, what commit are you building from?
>
> ...and what does git think the local changes to Makefile are ?
This is the output of 'git status':
On branch master
Your branch is up to date with 'origin/master'.
Changes not staged for commit:
(use "git add <file>..." to update what will be committed)
(use "git restore <file>..." to discard changes in working directory)
(commit or discard the untracked or modified content in submodules)
modified: dtc (new commits, modified content)
Untracked files:
(use "git add <file>..." to include in what will be committed)
pixman/
no changes added to commit (use "git add" and/or "git commit -a")
This is the output of 'git diff master':
diff --git a/dtc b/dtc
index 85e5d83984..88f18909db 160000
--- a/dtc
+++ b/dtc
@@ -1 +1 @@
-Subproject commit 85e5d839847af54efab170f2b1331b2a6421e647
+Subproject commit 88f18909db731a627456f26d779445f84e449536-dirty
I have tried 'git clean -d -f', 'git reset --hard' and 'git pull'. I am now at 74208cd252c5da9d867270a178799abd802b9338 and still seeing the error with MakeFile.
next prev parent reply other threads:[~2021-02-01 15:32 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-02-01 14:23 Makefile has local changes that will be overwritten Programmingkid
2021-02-01 14:48 ` Dan Streetman
2021-02-01 14:52 ` Peter Maydell
2021-02-01 15:30 ` Programmingkid [this message]
2021-02-02 9:26 ` Greg Kurz
2021-02-02 12:47 ` Warner Losh
2021-02-01 15:07 ` Programmingkid
2021-02-01 15:21 ` Dan Streetman
2021-02-01 14:58 ` Stefan Weil
2021-02-01 15:03 ` Peter Maydell
2021-02-01 15:36 ` Programmingkid
2021-02-01 16:04 ` Stefan Weil
2021-02-01 16:08 ` Programmingkid
2021-02-01 15:46 ` Daniel P. Berrangé
2021-02-01 16:06 ` Programmingkid
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-all 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=E9865C2F-68A9-404F-896C-09C2A78C51A3@gmail.com \
--to=programmingkidx@gmail.com \
--cc=ddstreet@canonical.com \
--cc=peter.maydell@linaro.org \
--cc=qemu-devel@nongnu.org \
/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;
as well as URLs for NNTP newsgroup(s).