From: Lars Ingebrigtsen <larsi@gnus.org>
To: Eli Zaretskii <eliz@gnu.org>
Cc: mutiny.mutiny@rediffmail.com, 29731@debbugs.gnu.org, rpluim@gmail.com
Subject: bug#29731: configure to distinguish makeinfo present-but-broken from missing-or-old
Date: Fri, 13 Aug 2021 16:41:05 +0200 [thread overview]
Message-ID: <87im099zlq.fsf@gnus.org> (raw)
In-Reply-To: <834kbtcu7y.fsf@gnu.org> (Eli Zaretskii's message of "Fri, 13 Aug 2021 17:09:05 +0300")
Eli Zaretskii <eliz@gnu.org> writes:
> It would be nice to have that, but basically it isn't our problem,
> IMO: building a tarball doesn't require makeinfo, while people who
> build from Git should IMO be expected to have a working Texinfo
> installation, which includes Perl modules necessary to run makeinfo.
Yes, you're right. If ./configure says that we can't find a (useable)
makeinfo, then it's up to the user to investigate the problem. In this
case, I'm guessing just typing "makeinfo" would have issued a bunch of
errors, which should point the user the right way -- and any changes we
make to configure here wouldn't really be that much more helpful.
So I'm closing this bug report.
--
(domestic pets only, the antidote for overdose, milk.)
bloggy blog: http://lars.ingebrigtsen.no
prev parent reply other threads:[~2021-08-13 14:41 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-12-16 7:38 bug#29731: emacs build broken (makeinfo) Mutiny
2017-12-16 8:59 ` Eli Zaretskii
2017-12-16 21:44 ` bug#29731: resolved&&advice Mutiny
2021-08-13 13:01 ` bug#29731: configure to distinguish makeinfo present-but-broken from missing-or-old Lars Ingebrigtsen
2021-08-13 13:31 ` Robert Pluim
2021-08-13 13:40 ` Lars Ingebrigtsen
2021-08-13 14:09 ` Eli Zaretskii
2021-08-13 14:41 ` Lars Ingebrigtsen [this message]
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=87im099zlq.fsf@gnus.org \
--to=larsi@gnus.org \
--cc=29731@debbugs.gnu.org \
--cc=eliz@gnu.org \
--cc=mutiny.mutiny@rediffmail.com \
--cc=rpluim@gmail.com \
/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).