From: Alan Mackenzie <acm@muc.de>
To: Eli Zaretskii <eliz@gnu.org>
Cc: emacs-devel@gnu.org
Subject: Re: Git help please - checking out old commit doesn't find lib/gnulib.mk.in.
Date: Sun, 12 Nov 2017 20:06:51 +0000 [thread overview]
Message-ID: <20171112200651.GC20916@ACM> (raw)
In-Reply-To: <83inefmjuh.fsf@gnu.org>
Hello, Eli.
On Sun, Nov 12, 2017 at 20:29:26 +0200, Eli Zaretskii wrote:
> > Date: Sun, 12 Nov 2017 18:09:59 +0000
> > From: Alan Mackenzie <acm@muc.de>
> > I'm attempting to check out a moderately old version of Emacs with:
> > $ git checkout 10c0e1c
> > . This appears to work. I then attempt to build it with:
> > $ time make -j17 bootstrap
> > . This fails with:
> > make: *** No rule to make target 'lib/gnulib.mk.in', needed by 'Makefile'. Stop.
> > . It would appear that the git checkout has failed to restore the state
> > of the given commit, in that it hasn't restored the indicated file. Is
> > this in fact the case?
> > What do I have to do to restore this version in a state I can build.
> I think you have some stale files that you need to clean up, basically
> anything that is not a versioned file.
I though that was what make bootstrap was for. In that working
directory, I tried ./autogen.sh all. This gave the error messages:
Running 'autoreconf -fi -I m4' ...
/usr/bin/m4:aclocal.m4:9: cannot open `m4/count-leading-zeros.m4': No such file or directory
+ 11 similar lines.
> For best results, I'd checkout into a separate directory, starting with
> "git worktree add".
Thanks. In the end, I just cloned another repository from my own
emacs-26 repo and checked out that version. This build without problems.
But it would be nice to be able to do what make bootstrap purports to do.
Maybe one of the other less used make targets will do this.
--
Alan Mackenzie (Nuremberg, Germany).
next prev parent reply other threads:[~2017-11-12 20:06 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-11-12 18:09 Git help please - checking out old commit doesn't find lib/gnulib.mk.in Alan Mackenzie
2017-11-12 18:22 ` Andreas Schwab
2017-11-12 18:24 ` Óscar Fuentes
2017-11-12 18:25 ` Lele Gaifax
2017-11-12 18:28 ` John Wiegley
2017-11-12 18:29 ` Eli Zaretskii
2017-11-12 20:06 ` Alan Mackenzie [this message]
2017-11-12 20:28 ` Eli Zaretskii
2017-11-12 20:40 ` Stefan Monnier
2017-11-12 21:23 ` Paul Eggert
2017-11-12 21:55 ` Alan Mackenzie
2017-11-12 23:51 ` Óscar Fuentes
2017-11-13 1:58 ` Stefan Monnier
2017-11-13 2:34 ` Óscar Fuentes
2017-11-13 3:17 ` Stefan Monnier
2017-11-13 1:42 ` Yasushi SHOJI
2017-11-13 8:21 ` Andreas Schwab
2017-11-13 3:30 ` Eli Zaretskii
2017-11-13 18:53 ` Alan Mackenzie
2017-11-13 19:13 ` Paul Eggert
2017-11-13 19:31 ` Alan Mackenzie
2017-11-13 19:17 ` Eli Zaretskii
2017-11-13 19:27 ` Alan Mackenzie
2017-11-13 19:35 ` Eli Zaretskii
2017-11-13 20:30 ` Alan Mackenzie
2017-11-13 20:42 ` Eli Zaretskii
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=20171112200651.GC20916@ACM \
--to=acm@muc.de \
--cc=eliz@gnu.org \
--cc=emacs-devel@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.
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).