public inbox for gdb-prs@sourceware.org
help / color / mirror / Atom feed
From: "psmith at gnu dot org" <sourceware-bugzilla@sourceware.org>
To: gdb-prs@sourceware.org
Subject: [Bug gdb/14678] New: GDB 7.5 fails to build unless makeinfo is installed
Date: Sat, 06 Oct 2012 19:17:00 -0000	[thread overview]
Message-ID: <bug-14678-4717@http.sourceware.org/bugzilla/> (raw)


http://sourceware.org/bugzilla/show_bug.cgi?id=14678

             Bug #: 14678
           Summary: GDB 7.5 fails to build unless makeinfo is installed
           Product: gdb
           Version: 7.5
            Status: NEW
          Severity: normal
          Priority: P2
         Component: gdb
        AssignedTo: unassigned@sourceware.org
        ReportedBy: psmith@gnu.org
    Classification: Unclassified


I've seen various bugs against earlier releases of GDB stating that they would
not build on systems where makeinfo is not installed, but they were supposed to
be fixed in the current GDB releases.  So there is a new build failure with GDB
7.5, which will not build properly on systems without makeinfo installed.

It appears that gdb.info is depending on the generated file GDBvn.texi, but
that file is not provided in the GDB 7.5 distribution.  As a result make
rebuilds it, and as a result of THAT it wants to rebuild gdb.info but this of
course fails if makeinfo is not available:

make[7]: Entering directory `/usr/src/cc/obj/f/gdb.i686/gdb/doc'
(test "ln -s" = "ln -s" && \
  ln -s /usr/src/cc/gdb-7.5/gdb/doc/all-cfg.texi gdb-cfg.texi) || \
ln /usr/src/cc/gdb-7.5/gdb/doc/all-cfg.texi gdb-cfg.texi || \
cp /usr/src/cc/gdb-7.5/gdb/doc/all-cfg.texi gdb-cfg.texi
echo "@set GDBVN `sed q /usr/src/cc/gdb-7.5/gdb/doc/../version.in`" >
./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 /usr/src/cc/gdb-7.5/gdb/doc/../../readline/doc"; then \
  echo "@set SYSTEM_READLINE" >> ./GDBvn.new; \
fi
mv GDBvn.new GDBvn.texi
/usr/src/cc/gdb-7.5/missing makeinfo --split-size=5000000 --split-size=5000000 
 -I /usr/src/cc/gdb-7.5/gdb/doc/../../readline/doc -I
/usr/src/cc/gdb-7.5/gdb/doc/../mi -I /usr/src/cc/gdb-7.5/gdb/doc \
    -o gdb.info /usr/src/cc/gdb-7.5/gdb/doc/gdb.texinfo
WARNING: `makeinfo' is missing on your system.  You should only need it if
         you modified a `.texi' or `.texinfo' file, or any other file
         indirectly affecting the aspect of the manual.  The spurious
         call might also be the consequence of using a buggy `make' (AIX,
         DU, IRIX).  You might want to install the `Texinfo' package or
         the `GNU make' package.  Grab either from any GNU archive site.
make[7]: *** [gdb.info] Error 1

-- 
Configure bugmail: http://sourceware.org/bugzilla/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are on the CC list for the bug.


             reply	other threads:[~2012-10-06 19:17 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-10-06 19:17 psmith at gnu dot org [this message]
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
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@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).