From: "Ludovic Courtès" <ludo@gnu.org>
To: Fabrice Fontaine <fontaine.fabrice@gmail.com>
Cc: 39974@debbugs.gnu.org
Subject: bug#39974: Guile fails to build without makeinfo
Date: Sat, 07 Mar 2020 17:04:51 +0100 [thread overview]
Message-ID: <878skci21o.fsf@gnu.org> (raw)
In-Reply-To: <CAPi7W80OJJUan4bjQxbZ3cyxsmGe6-fc1AydPVni2i5aSYbyHA@mail.gmail.com> (Fabrice Fontaine's message of "Sat, 7 Mar 2020 10:53:33 +0100")
Hello,
Fabrice Fontaine <fontaine.fabrice@gmail.com> skribis:
> guile fails to build without makeinfo:
>
> make[4]: Entering directory
> '/nvmedata/autobuild/instance-7/output-1/build/host-guile-2.0.14/doc/ref'
> MAKEINFO guile.info
> /nvmedata/autobuild/instance-7/output-1/build/host-guile-2.0.14/build-aux/missing:
> line 81: makeinfo: command not found
AFAIK, ‘makeinfo’ is needed if and only if one modifies the .texi files,
or perhaps the ‘configure’ file.
Could it be what happened here?
BTW, 2.0 is an old series that is no longer maintained (the current
stable series is 3.0, and the previous one is 2.2).
Thanks,
Ludo’.
next prev parent reply other threads:[~2020-03-07 16:04 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-03-07 9:53 bug#39974: Guile fails to build without makeinfo Fabrice Fontaine
2020-03-07 16:04 ` Ludovic Courtès [this message]
2020-03-07 16:35 ` Fabrice Fontaine
2020-03-07 20:40 ` Ludovic Courtès
2020-03-07 22:07 ` Fabrice Fontaine
2020-03-08 11:09 ` Ludovic Courtès
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/guile/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=878skci21o.fsf@gnu.org \
--to=ludo@gnu.org \
--cc=39974@debbugs.gnu.org \
--cc=fontaine.fabrice@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.
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).