unofficial mirror of bug-guile@gnu.org 
 help / color / mirror / Atom feed
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: Sun, 08 Mar 2020 12:09:59 +0100	[thread overview]
Message-ID: <8736ajdrw8.fsf@gnu.org> (raw)
In-Reply-To: <CAPi7W809bzq5NCM33iTAwudrox31KVhdg5xnmoDJVqtMDUnPrw@mail.gmail.com> (Fabrice Fontaine's message of "Sat, 7 Mar 2020 23:07:18 +0100")

Hello,

Fabrice Fontaine <fontaine.fabrice@gmail.com> skribis:

> Le sam. 7 mars 2020 à 21:40, Ludovic Courtès <ludo@gnu.org> a écrit :

[...]

>> > Yes, this build failure is raised by one of our buidlroot autobuilders.
>> > We're running autoreconf as we have a patch that updates configure.ac:
>>
>> OK.  From Guile’s perspective, it’s not a bug that ‘makeinfo’ is needed
>> in this case.
> OK, then instead of this patch, do you think that adding a
> --disable-doc option could be acceptable?

No because again, when building from a tarball, ‘makeinfo’ is not needed
(the Info files are included in the tarball).  I hope that makes sense!

Thanks,
Ludo’.





      reply	other threads:[~2020-03-08 11:09 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
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 [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/guile/

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=8736ajdrw8.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).