public inbox for
 help / color / mirror / Atom feed
From: Tom de Vries <>
Subject: [PATCH] Add --without-makeinfo
Date: Tue, 4 Oct 2022 17:21:33 +0200	[thread overview]
Message-ID: <20221004152132.GA1906@delia.home> (raw)


Currently, we cannot build gdb without makeinfo installed.

It would be convenient to work around this by using the configure flag
MAKEINFO=/usr/bin/true or some such, but that doesn't work because top-level
configure requires a makeinfo of at least version 4.7, and that version check
fails for /usr/bin/true, so we end up with MAKEINFO=missing instead.

What does work is this:
$ ./configure
$ make MAKEINFO=/usr/bin/true
but the drawback is that it'll have to be specified for each make invocation.

Fix this by adding support for --without-makeinfo in top-level configure.

Tested by building gdb on x86_64-linux, and verifying that no .info files
were generated.

OK for trunk?

- Tom

Add --without-makeinfo


2022-09-05  Tom de Vries  <>

	* Add --without-makeinfo.
	* configure: Regenerate.

 configure    | 4 ++++ | 4 ++++
 2 files changed, 8 insertions(+)

diff --git a/configure b/configure
index f14e0efd675..eb84add60cb 100755
--- a/configure
+++ b/configure
@@ -8399,6 +8399,9 @@ fi
 test -n "$MAKEINFO" || MAKEINFO="$MISSING makeinfo"
+if test $with_makeinfo = "no"; then
 case " $build_configdirs " in
   *" texinfo "*) MAKEINFO='$$r/$(BUILD_SUBDIR)/texinfo/makeinfo/makeinfo' ;;
@@ -8414,6 +8417,7 @@ case " $build_configdirs " in
 # FIXME: expect and dejagnu may become build tools?
diff --git a/ b/
index 0152c69292e..e4a2c076674 100644
--- a/
+++ b/
@@ -3441,6 +3441,9 @@ case " $build_configdirs " in
 AC_CHECK_PROGS([MAKEINFO], makeinfo, [$MISSING makeinfo])
+if test $with_makeinfo = "no"; then
 case " $build_configdirs " in
   *" texinfo "*) MAKEINFO='$$r/$(BUILD_SUBDIR)/texinfo/makeinfo/makeinfo' ;;
@@ -3456,6 +3459,7 @@ changequote(,)
 # FIXME: expect and dejagnu may become build tools?

             reply	other threads:[~2022-10-04 15:21 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-10-04 15:21 Tom de Vries [this message]
2022-10-09 17:02 ` Eric Gallager
2022-10-09 17:27 ` Andreas Schwab

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:

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

  git send-email \
    --in-reply-to=20221004152132.GA1906@delia.home \ \ \

* 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).