unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: Stefan Kangas <stefan@marxist.se>
To: Glenn Morris <rgm@gnu.org>
Cc: 46837@debbugs.gnu.org
Subject: bug#46837: Makefile dependencies for info files
Date: Fri, 5 Mar 2021 13:34:15 -0600	[thread overview]
Message-ID: <CADwFkm=0tacRfVSkRAFkRtmWPNuvTmXZ_XR3o-vOCg8Yyw9Qkw@mail.gmail.com> (raw)
In-Reply-To: <d1zgzhwgk1.fsf@fencepost.gnu.org> (Glenn Morris's message of "Fri, 05 Mar 2021 14:23:26 -0500")

Glenn Morris <rgm@gnu.org> writes:

> I would not recommend that, which in any case would only get past the
> configure step, leaving make to fail. Instead I would recommend
> installing makeinfo, which is widely available and where even an
> ancient version will do.

Sounds reasonable.  I don't see why you should need to build Emacs from
the git repository on systems where you can't install makeinfo.

Building from git should mostly be for development and brave souls
wanting to try the bleeding edge.





  reply	other threads:[~2021-03-05 19:34 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 [this message]
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='CADwFkm=0tacRfVSkRAFkRtmWPNuvTmXZ_XR3o-vOCg8Yyw9Qkw@mail.gmail.com' \
    --to=stefan@marxist.se \
    --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).