From: Noam Postavsky <npostavs@users.sourceforge.net>
To: Jean-Christophe Helary <jean.christophe.helary@gmail.com>
Cc: emacs-devel <emacs-devel@gnu.org>
Subject: Re: error building emacs from clean clone
Date: Tue, 10 Oct 2017 05:17:13 -0400 [thread overview]
Message-ID: <CAM-tV-_xMBRYZ3sBLkCyW-hTE53gTwL7a8yxC7GXbzULFJD6pw@mail.gmail.com> (raw)
In-Reply-To: <CA9C9F74-606A-4FDA-9366-A0B0EF5F00D5@gmail.com>
On Tue, Oct 10, 2017 at 4:51 AM, Jean-Christophe Helary
<jean.christophe.helary@gmail.com> wrote:
> I don't know what "now" is for you, but I've tried that a number of times in the past 24 hours and it still does not work.
Ah, okay. It was reported that updating fixed an error which seems the
same as what you posted:
https://debbugs.gnu.org/cgi/bugreport.cgi?users=emacs;bug=28760#11
Perhaps you have something else though?
> I think it's Stephan who suggested a while back that when a build failed for no obvious reasons, just starting from scratch was the best way to fix the issue. So I just erased my emacs directory and did the git clone dance, but this time without success.
Cloning from scratch is overkill, 'git clean -fx' will delete
everything not directly from git. That way you don't have to download
everything from the beginning.
Andreas' suggestion of 'make bootstrap' is *usually* enough, but not
in every case (see INSTALL.REPO for a couple of counter-examples).
> Last attempt was 10mn ago.
Which revision are you at? 'git log -1'
next prev parent reply other threads:[~2017-10-10 9:17 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-10-09 14:25 error building emacs from clean clone Jean-Christophe Helary
2017-10-09 15:58 ` Noam Postavsky
2017-10-09 22:32 ` Jean-Christophe Helary
2017-10-09 22:35 ` Noam Postavsky
2017-10-10 0:45 ` Stefan Monnier
2017-10-10 2:03 ` Jean-Christophe Helary
2017-10-10 8:35 ` Noam Postavsky
2017-10-10 8:51 ` Jean-Christophe Helary
2017-10-10 9:17 ` Noam Postavsky [this message]
2017-10-10 9:32 ` Phillip Lord
2017-10-10 9:45 ` Noam Postavsky
2017-10-10 8:47 ` Andreas Schwab
2017-10-10 8:52 ` Jean-Christophe Helary
2017-10-10 8:57 ` Andreas Schwab
2017-10-10 9:09 ` Jean-Christophe Helary
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=CAM-tV-_xMBRYZ3sBLkCyW-hTE53gTwL7a8yxC7GXbzULFJD6pw@mail.gmail.com \
--to=npostavs@users.sourceforge.net \
--cc=emacs-devel@gnu.org \
--cc=jean.christophe.helary@gmail.com \
/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.
Code repositories for project(s) associated with this public inbox
https://git.savannah.gnu.org/cgit/emacs.git
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).