public inbox for gdb-prs@sourceware.org
help / color / mirror / Atom feed
From: "doko at debian dot org" <sourceware-bugzilla@sourceware.org>
To: gdb-prs@sourceware.org
Subject: [Bug build/30108] New: gdb info docs fail to build when configured --with-system-readlne
Date: Fri, 10 Feb 2023 03:56:13 +0000 [thread overview]
Message-ID: <bug-30108-4717@http.sourceware.org/bugzilla/> (raw)
https://sourceware.org/bugzilla/show_bug.cgi?id=30108
Bug ID: 30108
Summary: gdb info docs fail to build when configured
--with-system-readlne
Product: gdb
Version: 13.1
Status: NEW
Severity: normal
Priority: P2
Component: build
Assignee: unassigned at sourceware dot org
Reporter: doko at debian dot org
Target Milestone: ---
this seems to be different than #27808. with --with-system-readline configured,
the build fails because it cannot find the readline includes. These are always
taken from the source tree, this should not be dependent on this configuration
option.
seen on both the 13 branch and trunk. proposed patch:
--- a/gdb/configure.ac
+++ b/gdb/configure.ac
@@ -590,7 +590,7 @@ if test "$with_system_readline" = yes; t
READLINE=-lreadline
READLINE_DEPS=
READLINE_CFLAGS=
- READLINE_TEXI_INCFLAG=
+ READLINE_TEXI_INCFLAG='-I $(READLINE_DIR)'
else
READLINE='$(READLINE_DIR)/libreadline.a'
READLINE_DEPS='$(READLINE)'
--
You are receiving this mail because:
You are on the CC list for the bug.
next reply other threads:[~2023-02-10 3:56 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-02-10 3:56 doko at debian dot org [this message]
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
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@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).