unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: Glenn Morris <rgm@gnu.org>
To: Eli Zaretskii <eliz@gnu.org>
Cc: 46837@debbugs.gnu.org
Subject: bug#46837: Makefile dependencies for info files
Date: Sat, 06 Mar 2021 12:38:38 -0500	[thread overview]
Message-ID: <5nczwcqj1d.fsf@fencepost.gnu.org> (raw)
In-Reply-To: <838s71xsve.fsf@gnu.org> (Eli Zaretskii's message of "Fri, 05 Mar 2021 22:12:05 +0200")

Eli Zaretskii wrote:

> So it will fail even if all the Info files are already in the tree,
> when makeinfo is not available?  Or are you saying that in order for
> "make" not to fail one must touch not just info/emacs.info, but also
> all the rest of the *.info files?

?

If all the info file are already there, make will see that they are newer
than their dependencies, so it won't try to rebuild them.
There's no need to "touch" anything, and I would/did not recommend
doing so.

> No argument there, I was talking about fire escape.  After all, we are
> removing a "feature" that existed in previous releases.  

--without-makeinfo was always irrelevant in _releases_, where the info
files are pre-built.

> It would be good to tell people how to get back the old behavior, I
> think.

They can always do "make lisp" (I think) instead of "make [all]".

Or you can add a target "all-noinfo" which is just "all" without "info",
but I don't know who the users of such a target would be.





  reply	other threads:[~2021-03-06 17:38 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-02-28 23:39 bug#46837: Makefile dependencies for info files Glenn Morris
2021-03-01 16:47 ` Eli Zaretskii
2021-03-04 18:53   ` Glenn Morris
2021-03-04 19:22     ` Eli Zaretskii
2021-03-04 19:00 ` Glenn Morris
2021-03-05  4:45   ` Glenn Morris
2021-03-05  7:31     ` Eli Zaretskii
2021-03-05 19:23       ` Glenn Morris
2021-03-05 19:34         ` Stefan Kangas
2021-03-07 10:52           ` Michael Albinus
2021-03-07 17:14             ` Glenn Morris
2021-03-07 17:22               ` Michael Albinus
2021-03-07 17:33                 ` Glenn Morris
2021-03-07 17:49                   ` Michael Albinus
2021-03-07 17:38                 ` Glenn Morris
2021-03-08 17:51                   ` Glenn Morris
2021-03-08 17:58                     ` Michael Albinus
2021-03-05 20:12         ` Eli Zaretskii
2021-03-06 17:38           ` Glenn Morris [this message]
2021-03-06 18:12             ` 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=5nczwcqj1d.fsf@fencepost.gnu.org \
    --to=rgm@gnu.org \
    --cc=46837@debbugs.gnu.org \
    --cc=eliz@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).