From: Elena Zannoni <ezannoni@redhat.com>
To: Stephane Carrez <stcarrez@nerim.fr>
Cc: Tom Tromey <tromey@redhat.com>,
Elena Zannoni <ezannoni@redhat.com>,
Daniel Jacobowitz <drow@mvista.com>,
Gdb List <gdb@sources.redhat.com>
Subject: Re: build failure in TUI
Date: Mon, 26 Aug 2002 15:04:00 -0000 [thread overview]
Message-ID: <15722.42338.319952.600556@localhost.redhat.com> (raw)
In-Reply-To: <3D6ABF11.1060109@nerim.fr>
Stephane Carrez writes:
> Hi!
>
> Elena Zannoni wrote:
>
> > [...]
> > > Debian has this:
> > > #define CTRL_CHAR(c) ((c) < control_character_threshold && (((c) & 0x80) == 0))
> > >
> > > I'm not sure offhand if this is fixed in stock readline 4.3, or if it
> > > is Debian local.
> > >
> >
> > It's in 4.3.
> >
> > Elena
> >
>
>
> We can temporarily override it in tuiIO.c to use 4.3 definition and until we have readline 4.3.
>
Yes.
>
> The TUI does not build with readline 4.3 (on the branch) because it uses readline internal
>
> variables that have disappeared. I filed a gdb PR for that. But this must not prevent
> a possible use of readline 4.3 for gdb 5.3.
>
Is there a workaround? Maybe the variables have disappeared from the
interface, but some accessor functions have been added to readline?
Elena
> Stephane
>
> -----------------------------------------------------------------------
> Home Office
> E-mail: stcarrez@nerim.fr Stephane.Carrez@solsoft.fr
> WWW: http://stephane.carrez.free.fr http://www.solsoft.com
> Free the Software! Visual Security Policy Management
>
next prev parent reply other threads:[~2002-08-26 22:04 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-08-26 14:18 Tom Tromey
2002-08-26 14:21 ` Daniel Jacobowitz
2002-08-26 14:31 ` Elena Zannoni
2002-08-26 14:51 ` Stephane Carrez
2002-08-26 15:04 ` Elena Zannoni [this message]
2002-08-26 15:31 ` Daniel Jacobowitz
2002-08-26 17:29 ` Elena Zannoni
2002-08-26 17:37 ` Elena Zannoni
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=15722.42338.319952.600556@localhost.redhat.com \
--to=ezannoni@redhat.com \
--cc=drow@mvista.com \
--cc=gdb@sources.redhat.com \
--cc=stcarrez@nerim.fr \
--cc=tromey@redhat.com \
/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