From: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH 1/2] package/gdb (7.9): fix doc build when makeinfo is missing
Date: Sat, 5 Sep 2015 20:09:30 +0200 [thread overview]
Message-ID: <20150905200930.7e018f2a@free-electrons.com> (raw)
In-Reply-To: <1441463443-9335-1-git-send-email-romain.naour@openwide.fr>
Romain,
On Sat, 5 Sep 2015 16:30:42 +0200, Romain Naour wrote:
> + gdb/index.html: ${GDB_DOC_FILES}
> +- $(MAKEHTML) $(MAKEHTMLFLAGS) $(READLINE_TEXI_INCFLAG) -I ${GDBMI_DIR} -I $(srcdir) $(srcdir)/gdb.texinfo
> ++ $(MAKEHTML) $(MAKEHTMLFLAGS) $(READLINE_TEXI_INCFLAG) -I ${GDBMI_DIR} -I $(srcdir) $(srcdir)/gdb.texinfo | true
Can you try instead to just prepend a - at the beginning of the line?
-$(MAKEHTML) ....
Or better yet, for a properly upstreamable solution, a --enable-doc
option to explicitly enable or disable the doc. Or something that
detects if makeinfo is available, and if it isn't, that doesn't try to
generate the documentation.
Thanks,
Thomas
--
Thomas Petazzoni, CTO, Free Electrons
Embedded Linux, Kernel and Android engineering
http://free-electrons.com
next prev parent reply other threads:[~2015-09-05 18:09 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-09-05 14:30 [Buildroot] [PATCH 1/2] package/gdb (7.9): fix doc build when makeinfo is missing Romain Naour
2015-09-05 14:30 ` [Buildroot] [PATCH 2/2] package/gdb (7.10): fix doc build when make info " Romain Naour
2015-09-05 18:09 ` Thomas Petazzoni [this message]
2015-09-05 21:50 ` [Buildroot] [PATCH 1/2] package/gdb (7.9): fix doc build when makeinfo " Romain Naour
2015-09-06 8:31 ` Thomas Petazzoni
2015-09-06 9:18 ` Romain Naour
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=20150905200930.7e018f2a@free-electrons.com \
--to=thomas.petazzoni@free-electrons.com \
--cc=buildroot@busybox.net \
/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