public inbox for gdb-prs@sourceware.org help / color / mirror / Atom feed
From: "wpoely86 at gmail dot com" <sourceware-bugzilla@sourceware.org> To: gdb-prs@sourceware.org Subject: [Bug compile/18113] New: GDB 7.9 fails to build when makeinfo is not installed Date: Wed, 11 Mar 2015 13:21:00 -0000 [thread overview] Message-ID: <bug-18113-4717@http.sourceware.org/bugzilla/> (raw) https://sourceware.org/bugzilla/show_bug.cgi?id=18113 Bug ID: 18113 Summary: GDB 7.9 fails to build when makeinfo is not installed Product: gdb Version: 7.9 Status: NEW Severity: normal Priority: P2 Component: compile Assignee: unassigned at sourceware dot org Reporter: wpoely86 at gmail dot com This bug is more or less the same as https://sourceware.org/bugzilla/show_bug.cgi?id=14678 , only this one is for GDB 7.9. If you don't have makeinfo installed, the make will fail: make[5]: Entering directory `/home/ward/tmp/eb_sandbox_20150311_13-46-46_buOYR/GDB/7.9/GCC-4.9.2/gdb-7.9/gdb/doc' (test "ln -s" = "ln -s" && \ ln -s ./all-cfg.texi gdb-cfg.texi) || \ ln ./all-cfg.texi gdb-cfg.texi || \ cp ./all-cfg.texi gdb-cfg.texi date=`sed -n -e 's/^.* BFD_VERSION_DATE \(.*\)$/\1/p' ./../../bfd/version.h`; \ sed -e "s/DATE/$date/" < ./../version.in > version.subst echo "@set GDBVN `sed q version.subst`" > ./GDBvn.new if [ -n "(GDB) " ]; then \ echo "@set VERSION_PACKAGE (GDB) " >> ./GDBvn.new; \ fi echo "@set BUGURL @uref{http://www.gnu.org/software/gdb/bugs/}" >> ./GDBvn.new if [ "@uref{http://www.gnu.org/software/gdb/bugs/}" = "@uref{http://www.gnu.org/software/gdb/bugs/}" ]; then \ echo "@set BUGURL_DEFAULT" >> ./GDBvn.new; \ fi if test -z "-I ./../../readline/doc"; then \ echo "@set SYSTEM_READLINE" >> ./GDBvn.new; \ fi if [ -n "" ]; then \ echo "@set SYSTEM_GDBINIT " >> ./GDBvn.new; \ fi mv GDBvn.new GDBvn.texi /home/ward/tmp/eb_sandbox_20150311_13-46-46_buOYR/GDB/7.9/GCC-4.9.2/gdb-7.9/missing makeinfo --split-size=5000000 --split-size=5000000 -I ./../../readline/doc -I ./../mi -I . \ -o gdb.info ./gdb.texinfo /home/ward/tmp/eb_sandbox_20150311_13-46-46_buOYR/GDB/7.9/GCC-4.9.2/gdb-7.9/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[5]: *** [gdb.info] Error 127 make[5]: Leaving directory `/home/ward/tmp/eb_sandbox_20150311_13-46-46_buOYR/GDB/7.9/GCC-4.9.2/gdb-7.9/gdb/doc' make[4]: *** [subdir_do] Error 1 make[4]: Leaving directory `/home/ward/tmp/eb_sandbox_20150311_13-46-46_buOYR/GDB/7.9/GCC-4.9.2/gdb-7.9/gdb' make[3]: *** [install-only] Error 2 make[3]: Leaving directory `/home/ward/tmp/eb_sandbox_20150311_13-46-46_buOYR/GDB/7.9/GCC-4.9.2/gdb-7.9/gdb' make[2]: *** [install] Error 2 make[2]: Leaving directory `/home/ward/tmp/eb_sandbox_20150311_13-46-46_buOYR/GDB/7.9/GCC-4.9.2/gdb-7.9/gdb' make[1]: *** [install-gdb] Error 2 make[1]: Leaving directory `/home/ward/tmp/eb_sandbox_20150311_13-46-46_buOYR/GDB/7.9/GCC-4.9.2/gdb-7.9' make: *** [install] Error 2 This is because the missing script passes the return code (127) from the failed call to makeinfo to make. Setting MAKEINFO=true (or false) will not help because the configure script does a version check on makeinfo. -- You are receiving this mail because: You are on the CC list for the bug.
next reply other threads:[~2015-03-11 13:21 UTC|newest] Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top 2015-03-11 13:21 wpoely86 at gmail dot com [this message] 2015-03-12 11:11 ` [Bug compile/18113] " wpoely86 at gmail dot com 2015-07-01 5:30 ` david.abdurachmanov at gmail dot com 2015-09-03 14:11 ` david.abdurachmanov at gmail dot com 2022-02-22 15:19 ` [Bug build/18113] " tromey at sourceware dot org 2023-08-25 17:48 ` bugmenot at mailinator dot com
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-18113-4717@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: linkBe 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).