public inbox for gdb-prs@sourceware.org
help / color / mirror / Atom feed
From: "vries at gcc dot gnu.org" <sourceware-bugzilla@sourceware.org>
To: gdb-prs@sourceware.org
Subject: [Bug build/10723] Dependency on readline internal variable
Date: Mon, 01 May 2023 07:34:14 +0000 [thread overview]
Message-ID: <bug-10723-4717-cJhNCXJz0p@http.sourceware.org/bugzilla/> (raw)
In-Reply-To: <bug-10723-4717@http.sourceware.org/bugzilla/>
https://sourceware.org/bugzilla/show_bug.cgi?id=10723
Tom de Vries <vries at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |tromey at sourceware dot org
--- Comment #5 from Tom de Vries <vries at gcc dot gnu.org> ---
(In reply to Tom de Vries from comment #4)
> Changing component to build, problem is not unique (anymore) to TUI.
More specifically:
...
$ find gdb* -type f | egrep -v ChangeLog | xargs egrep -i
"extern.*[^a-zA-Z]_rl_"
gdb/tui/tui-io.c: extern int _rl_echoing_p;
gdb/completer.c: extern int _rl_complete_mark_directories;
gdb/completer.c:extern int _rl_completion_prefix_display_length;
gdb/completer.c:extern int _rl_print_completions_horizontally;
gdb/completer.c:EXTERN_C int _rl_qsort_string_compare (const void *, const void
*);
gdb/cli-out.c:EXTERN_C void _rl_erase_entire_line (void);
...
--
You are receiving this mail because:
You are on the CC list for the bug.
next prev parent reply other threads:[~2023-05-01 7:34 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <bug-10723-4717@http.sourceware.org/bugzilla/>
2012-07-19 12:18 ` [Bug tui/10723] " rguenther at suse dot de
2012-07-19 12:23 ` jan.kratochvil at redhat dot com
2012-07-19 12:43 ` rguenther at suse dot de
2012-11-10 13:35 ` Stephane.Carrez at gmail dot com
2023-05-01 5:24 ` [Bug build/10723] " vries at gcc dot gnu.org
2023-05-01 7:34 ` vries at gcc dot gnu.org [this message]
2023-12-16 9:38 ` cvs-commit at gcc dot gnu.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-10723-4717-cJhNCXJz0p@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).