unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: Eli Zaretskii <eliz@gnu.org>
To: Glenn Morris <rgm@gnu.org>
Cc: 46837@debbugs.gnu.org
Subject: bug#46837: Makefile dependencies for info files
Date: Fri, 05 Mar 2021 09:31:44 +0200	[thread overview]
Message-ID: <834khqys2n.fsf@gnu.org> (raw)
In-Reply-To: <2eeeguus2h.fsf@fencepost.gnu.org> (message from Glenn Morris on Thu, 04 Mar 2021 23:45:26 -0500)

> From: Glenn Morris <rgm@gnu.org>
> Date: Thu, 04 Mar 2021 23:45:26 -0500
> 
> Glenn Morris wrote:
> 
> >> 1) Catering for systems without makeinfo - I would suggest dropping this.
> >
> > By which I meant, remove configure --without-makeinfo and special-casing
> > HAVE_MAKEINFO=no in the Makefile, thus removing the need for the
> > "info-real" target.
> >
> > configure not finding makeinfo would continue to be non-fatal if
> > info/emacs.info exists, to cater for release tarfiles where info files
> > are pre-built.

So the poor souls who don't have makeinfo could "touch info/emacs.info"
and have the build continue instead of failing?  If this works, I
think it's a fine solution.  It would be even better if the advice to
"touch info/emacs.info" would be included in the error message printed
when we find no makeinfo.

Thanks.





  reply	other threads:[~2021-03-05  7:31 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 [this message]
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
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=834khqys2n.fsf@gnu.org \
    --to=eliz@gnu.org \
    --cc=46837@debbugs.gnu.org \
    --cc=rgm@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).