public inbox for gdb-prs@sourceware.org
help / color / mirror / Atom feed
From: "cvs-commit at gcc dot gnu.org" <sourceware-bugzilla@sourceware.org>
To: gdb-prs@sourceware.org
Subject: [Bug build/30108] gdb info docs fail to build when configured --with-system-readlne
Date: Mon, 13 Feb 2023 14:59:48 +0000	[thread overview]
Message-ID: <bug-30108-4717-7DdGaJ5WlW@http.sourceware.org/bugzilla/> (raw)
In-Reply-To: <bug-30108-4717@http.sourceware.org/bugzilla/>

https://sourceware.org/bugzilla/show_bug.cgi?id=30108

--- Comment #5 from cvs-commit at gcc dot gnu.org <cvs-commit at gcc dot gnu.org> ---
The gdb-13-branch branch has been updated by Keith Seitz
<kseitz@sourceware.org>:

https://sourceware.org/git/gitweb.cgi?p=binutils-gdb.git;h=c594b6f7d5dd50bc0ae3b0f15b556bfe592893bb

commit c594b6f7d5dd50bc0ae3b0f15b556bfe592893bb
Author: Keith Seitz <keiths@redhat.com>
Date:   Mon Feb 13 06:14:40 2023 -0800

    Fix doc build dependencies for --with-system-readline

    PR build/30108 concerns building gdb documentation with
    --with-sytem-readline.  If the in-tree readline directory is
    missing, though, the docs will fail to build:

    make[4]: Entering directory
'/home/keiths/work/readline-doc-issue/linux/gdb/doc'
    make[4]: *** No rule to make target
'../../../src/gdb/doc/../../readline/readline/doc/rluser.texi', needed by
'gdb.info'.  Stop.

    The listed file (and hsuser.texi) are conditionally included by
gdb.texinfo.
    When system readline is used, gdb/configure.ac will leave
    READLINE_TEXI_INCFLAGS empty, causing doc/Makefile.in to output a line to
    $BUILD/doc/GDBvn.texi with "@set SYSTEM_READLINE".  This surpresses the
    inclusion of the missing files. They are not needed or used in this
    scenario.

    However, GDB_DOC_SOURCE_INCLUDES always lists these two files as
dependencies,
    thus provoking the build error whenever readline/ is missing.

    This patch fixes this by creating (essentially) a conditional setting of
the
    dependencies to be included from readline.

-- 
You are receiving this mail because:
You are on the CC list for the bug.

  parent reply	other threads:[~2023-02-13 14:59 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-02-10  3:56 [Bug build/30108] New: " doko at debian dot org
2023-02-10  3:56 ` [Bug build/30108] " doko at debian dot org
2023-02-10 20:31 ` keiths at redhat dot com
2023-02-10 21:43 ` keiths at redhat dot com
2023-02-12 11:41 ` brobecker at gnat dot com
2023-02-13 14:16 ` cvs-commit at gcc dot gnu.org
2023-02-13 14:59 ` cvs-commit at gcc dot gnu.org [this message]
2023-02-13 15:07 ` keiths at redhat 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-30108-4717-7DdGaJ5WlW@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).