unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: Robert Pluim <rpluim@gmail.com>
To: Lars Ingebrigtsen <larsi@gnus.org>
Cc: Mutiny <mutiny.mutiny@rediffmail.com>, 29731@debbugs.gnu.org
Subject: bug#29731: configure to distinguish makeinfo present-but-broken from missing-or-old
Date: Fri, 13 Aug 2021 15:31:10 +0200	[thread overview]
Message-ID: <871r6xqxnl.fsf@gmail.com> (raw)
In-Reply-To: <875yw9cxbt.fsf_-_@gnus.org> (Lars Ingebrigtsen's message of "Fri, 13 Aug 2021 15:01:58 +0200")

>>>>> On Fri, 13 Aug 2021 15:01:58 +0200, Lars Ingebrigtsen <larsi@gnus.org> said:

    Lars> "Mutiny " <mutiny.mutiny@rediffmail.com> writes:
    >> I did some deep testing and found out that following perl(sic) modules were
    >> missing:
    >> (excerpt from my setup perl modules script)
    >> 
    >> cpan install Locale::Messages # emacs build
    >> cpan install Text::Unidecode # emacs build
    >> cpan install Unicode::EastAsianWidth # emacs build
    >> 
    >> Thereafter ./configure and make&&make install working.

    Lars> Does the Emacs build use Perl?  I looked through configure and Makefile
    Lars> and didn't see any Perl mentions.

    Lars> Anybody know?

No. Some of the admin scripts do, but theyʼre not required to build
emacs. makeinfo requires perl last time I checked.

Robert
-- 





  reply	other threads:[~2021-08-13 13:31 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 [this message]
2021-08-13 13:40       ` Lars Ingebrigtsen
2021-08-13 14:09         ` Eli Zaretskii
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

  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=871r6xqxnl.fsf@gmail.com \
    --to=rpluim@gmail.com \
    --cc=29731@debbugs.gnu.org \
    --cc=larsi@gnus.org \
    --cc=mutiny.mutiny@rediffmail.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).