From: Eli Zaretskii <eliz@gnu.org>
To: Lars Ingebrigtsen <larsi@gnus.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 17:09:05 +0300 [thread overview]
Message-ID: <834kbtcu7y.fsf@gnu.org> (raw)
In-Reply-To: <87a6llbgz4.fsf@gnus.org> (message from Lars Ingebrigtsen on Fri, 13 Aug 2021 15:40:31 +0200)
> From: Lars Ingebrigtsen <larsi@gnus.org>
> Date: Fri, 13 Aug 2021 15:40:31 +0200
> Cc: Mutiny <mutiny.mutiny@rediffmail.com>, 29731@debbugs.gnu.org
>
> Robert Pluim <rpluim@gmail.com> writes:
>
> > No. Some of the admin scripts do, but theyʼre not required to build
> > emacs. makeinfo requires perl last time I checked.
>
> Aha. Hm. Oh, Glenn had renamed this to:
>
> retitle 29731 configure to distinguish makeinfo present-but-broken from missing-or-old
>
> Which is, I guess, the correct description here. So makeinfo didn't
> work for the user because Perl was b0rked, but ./configure says that the
> user didn't have makeinfo.
>
> I guess that should be possible to distinguish...
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.
next prev parent reply other threads:[~2021-08-13 14:09 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 [this message]
2021-08-13 14:41 ` Lars Ingebrigtsen
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=834kbtcu7y.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=29731@debbugs.gnu.org \
--cc=larsi@gnus.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 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.