From: Eli Zaretskii <eliz@gnu.org>
To: Lars Ingebrigtsen <larsi@gnus.org>
Cc: emacs-devel@gnu.org
Subject: Re: A target that's even more bootstrap?
Date: Wed, 19 Jun 2019 18:48:34 +0300 [thread overview]
Message-ID: <83v9x1r2y5.fsf@gnu.org> (raw)
In-Reply-To: <m3pnn94m36.fsf@gnus.org> (message from Lars Ingebrigtsen on Wed, 19 Jun 2019 17:43:41 +0200)
> From: Lars Ingebrigtsen <larsi@gnus.org>
> Cc: emacs-devel@gnu.org
> Date: Wed, 19 Jun 2019 17:43:41 +0200
>
> > Can you tell what it fails to do that requires to run autogen.sh?
>
> OK, there were more failure modes here than I was aware of...
>
> make extraclean bootstrap
>
> just plain fails, ending with
>
> rm -f config-tmp-*
> rm -f ./*~ \#*
> make -C src bootstrap-clean
> make[1]: Entering directory '/home/larsi/src/emacs/trunk/src'
> make[1]: *** No rule to make target 'bootstrap-clean'. Stop.
> make[1]: Leaving directory '/home/larsi/src/emacs/trunk/src'
> Makefile:891: recipe for target 'src_bootstrap-clean' failed
> make: *** [src_bootstrap-clean] Error 2
>
> make extraclean; make bootstrap
>
> does not fail, but extraclean does not remove the .elc files, and
> whatever it does also stops "make bootstrap" from removing the .elc
> files, which is rather surprising.
>
> Running the autogen.sh; ./configure in between these two makes enables
> bootstrap to delete the .elc files.
We should need to do only this:
make extraclean
make
There should be no need to say "make bootstrap", precisely as it isn't
needed in a freshly cloned repository.
So I understand one thing extraclean doesn't do is remove the *.elc
files; let's add that. What else?
next prev parent reply other threads:[~2019-06-19 15:48 UTC|newest]
Thread overview: 59+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-06-18 11:22 A target that's even more bootstrap? Lars Ingebrigtsen
2019-06-18 12:16 ` Andreas Schwab
2019-06-18 12:27 ` Lars Ingebrigtsen
2019-06-18 12:53 ` Phillip Lord
2019-06-18 13:20 ` Stefan Monnier
2019-06-18 13:28 ` Lars Ingebrigtsen
2019-06-18 16:03 ` Eli Zaretskii
2019-06-19 9:29 ` Phillip Lord
2019-06-19 15:21 ` Eli Zaretskii
2019-06-19 13:15 ` Lars Ingebrigtsen
2019-06-19 14:00 ` Andreas Schwab
2019-06-19 15:28 ` Eli Zaretskii
2019-06-19 15:32 ` Lars Ingebrigtsen
2019-06-18 15:53 ` Eli Zaretskii
2019-06-18 15:58 ` Lars Ingebrigtsen
2019-06-18 16:54 ` Eli Zaretskii
2019-06-18 17:47 ` Andy Moreton
2019-06-18 19:22 ` Óscar Fuentes
2019-06-19 4:32 ` Elias Mårtenson
2019-06-19 5:29 ` Teemu Likonen
2019-06-19 15:12 ` Eli Zaretskii
2019-06-19 20:06 ` Juanma Barranquero
2019-06-19 20:19 ` Lars Ingebrigtsen
2019-06-19 20:26 ` Óscar Fuentes
2019-06-20 2:30 ` Eli Zaretskii
2019-06-19 11:53 ` Lars Ingebrigtsen
2019-06-19 12:33 ` Andy Moreton
2019-06-19 12:45 ` Óscar Fuentes
2019-06-19 13:35 ` Juanma Barranquero
2019-06-19 13:46 ` Lars Ingebrigtsen
2019-06-19 15:34 ` Eli Zaretskii
2019-06-19 15:43 ` Lars Ingebrigtsen
2019-06-19 15:48 ` Eli Zaretskii [this message]
2019-06-19 16:12 ` Lars Ingebrigtsen
2019-06-19 17:03 ` Eli Zaretskii
2019-06-19 17:29 ` Lars Ingebrigtsen
2019-06-19 18:18 ` Eli Zaretskii
2019-06-20 11:32 ` Lars Ingebrigtsen
2019-06-20 13:06 ` Eli Zaretskii
2019-06-20 14:23 ` Lars Ingebrigtsen
2019-06-20 15:10 ` Lars Ingebrigtsen
2019-06-20 16:29 ` Eli Zaretskii
2019-06-21 10:51 ` Lars Ingebrigtsen
2019-06-21 22:03 ` Paul Eggert
2019-06-23 2:48 ` Richard Stallman
2019-06-20 16:23 ` Eli Zaretskii
2019-06-20 16:27 ` Lars Ingebrigtsen
2019-06-20 16:46 ` Eli Zaretskii
2019-06-20 16:47 ` Lars Ingebrigtsen
2019-06-20 18:24 ` Paul Eggert
2019-06-19 15:29 ` Phillip Lord
2019-06-19 15:59 ` Óscar Fuentes
2019-06-19 16:18 ` Stefan Monnier
2019-06-19 16:35 ` Óscar Fuentes
2019-06-19 17:03 ` Out of tree builds [was Re: A target that's even more bootstrap?] Glenn Morris
2019-06-19 17:30 ` Óscar Fuentes
2019-06-19 17:13 ` A target that's even more bootstrap? Stefan Monnier
2019-06-19 17:43 ` Óscar Fuentes
2019-06-20 13:49 ` Phillip Lord
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=83v9x1r2y5.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=emacs-devel@gnu.org \
--cc=larsi@gnus.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 external index
https://git.savannah.gnu.org/cgit/emacs.git
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.