From: Emanuel Berg <embe8573@student.uu.se>
To: help-gnu-emacs@gnu.org
Subject: Re: Upgrading Emacs from Git
Date: Thu, 11 Feb 2016 02:55:37 +0100 [thread overview]
Message-ID: <87vb5wf1t2.fsf@debian.uxu> (raw)
In-Reply-To: 87mvr8t4y6.fsf@wanadoo.es
Óscar Fuentes <ofv@wanadoo.es> writes:
>> What do you do if that fails as well?
>
> In the directory that contains the git checkout
> execute:
>
> git clean -f -d -x
>
> That ensures that you are using a pristine source
> directory. Then
>
> make
>
> If that fails, then the build is broken due to some
> erroneous change made by the developers. Wait one day
> or two, "git pull" again, repeat the build process.
> If the build is still broken, on Emacs do
>
> M-x report-emacs-bug
>
> including details about your setup (compiler, library
> versions, etc) and the output of the build at the
> failure point.
>
> It is possible to check out a previous vesion (one day
> ago, for instance) instead of waiting for a fix
> upstream, but that requires and slightly more
> complicated git usage.
Case closed :)
--
underground experts united
http://user.it.uu.se/~embe8573
next prev parent reply other threads:[~2016-02-11 1:55 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-02-10 10:22 Upgrading Emacs from Git Marcin Borkowski
2016-02-10 16:51 ` Gregor Zattler
2016-02-11 14:07 ` Stefan Monnier
2016-02-10 17:27 ` Eli Zaretskii
2016-02-10 18:20 ` Óscar Fuentes
2016-02-11 0:52 ` Emanuel Berg
2016-02-11 1:24 ` Óscar Fuentes
2016-02-11 1:55 ` Emanuel Berg [this message]
[not found] ` <mailman.4359.1455152116.843.help-gnu-emacs@gnu.org>
2016-02-11 1:25 ` P. A. López-Valencia
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
List information: https://www.gnu.org/software/emacs/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87vb5wf1t2.fsf@debian.uxu \
--to=embe8573@student.uu.se \
--cc=help-gnu-emacs@gnu.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 read-only IMAP folder(s) and NNTP newsgroup(s).