public inbox for gdb-prs@sourceware.org
help / color / mirror / Atom feed
From: "Nick.Fall at outlook dot jp" <sourceware-bugzilla@sourceware.org>
To: gdb-prs@sourceware.org
Subject: [Bug build/14678] GDB 7.5 fails to build unless makeinfo is installed
Date: Wed, 19 Oct 2022 01:43:32 +0000 [thread overview]
Message-ID: <bug-14678-4717-NcTWh0R3jl@http.sourceware.org/bugzilla/> (raw)
In-Reply-To: <bug-14678-4717@http.sourceware.org/bugzilla/>
https://sourceware.org/bugzilla/show_bug.cgi?id=14678
nfall <Nick.Fall at outlook dot jp> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |Nick.Fall at outlook dot jp
--- Comment #15 from nfall <Nick.Fall at outlook dot jp> ---
This bug appears to still be occuring in gdb 12.1.
$ mkdir gdbtest
$ cd gdbtest
$ ../tmp/gdb-12.1/configure
...
checking for makeinfo... no
/home/me/tmp/gdb-12.1/missing: line 81: makeinfo: command not found
...
$ make
...
MAKEINFO doc/bfd.info
/home/me/tmp/gdb-12.1/missing: line 81: makeinfo: command not found
WARNING: 'makeinfo' is missing on your system.
You should only need it if you modified a '.texi' file, or
any other file indirectly affecting the aspect of the manual.
You might want to install the Texinfo package:
<http://www.gnu.org/software/texinfo/>
The spurious makeinfo call might also be the consequence of
using a buggy 'make' (AIX, DU, IRIX), in which case you might
want to install GNU make:
<http://www.gnu.org/software/make/>
make[3]: *** [doc/bfd.info] Error 127
make[3]: Leaving directory `/home/me/gdbtest/bfd'
make[2]: *** [info-recursive] Error 1
make[2]: Leaving directory `/home/me/gdbtest/bfd'
make[1]: *** [all-bfd] Error 2
make[1]: Leaving directory `/home/me/gdbtest'
make: *** [all] Error 2
--
You are receiving this mail because:
You are on the CC list for the bug.
next prev parent reply other threads:[~2022-10-19 1:44 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-10-06 19:17 [Bug gdb/14678] New: " psmith at gnu dot org
2013-01-02 18:57 ` [Bug gdb/14678] " palves at redhat dot com
2013-06-28 18:12 ` aaro.koskinen at iki dot fi
2020-03-07 19:18 ` psmith at gnu dot org
2020-03-07 19:22 ` psmith at gnu dot org
2020-11-21 20:48 ` miguel.ojeda.sandonis at gmail dot com
2022-02-22 15:18 ` tromey at sourceware dot org
2022-02-22 15:19 ` tromey at sourceware dot org
2022-02-22 15:19 ` tromey at sourceware dot org
2022-02-22 15:20 ` tromey at sourceware dot org
2022-02-23 15:12 ` [Bug build/14678] " tromey at sourceware dot org
2022-10-04 15:48 ` vries at gcc dot gnu.org
2022-10-19 1:43 ` Nick.Fall at outlook dot jp [this message]
2022-10-19 4:02 ` vries at gcc dot gnu.org
2023-08-28 7:55 ` bugmenot at mailinator dot com
2023-08-28 13:48 ` tromey at sourceware dot org
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=bug-14678-4717-NcTWh0R3jl@http.sourceware.org/bugzilla/ \
--to=sourceware-bugzilla@sourceware.org \
--cc=gdb-prs@sourceware.org \
/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).