From: Jan Kratochvil <jan.kratochvil@redhat.com>
To: gdb@sourceware.org
Cc: Kai Tietz <ktietz@redhat.com>, Eli Zaretskii <eliz@gnu.org>,
Christopher Faylor
<cgf-use-the-mailinglist-please@gnu.org>
Subject: readline rebase 5.1->6.2?
Date: Tue, 22 Mar 2011 15:43:00 -0000 [thread overview]
Message-ID: <20110322154327.GA8966@host1.jankratochvil.net> (raw)
Hi,
it is a bity pity the sourceware tree still bundles readline-5.1 while distros
build GDB with readline less than 5 years old.
This means in practice GDB already runs without the custom patches contained
in src/readline/ , just making GDB forked with individual downstream patch fix
ups of the compatibility.
Just the patches are of the kind of MS-related platforms compatibility:
+dnl BEGIN changes for CYGNUS cross-building for Cygwin
+#ifdef __MSDOS__
+#if defined (__GO32__)
+#ifndef __MINGW32__
!+#if defined (SIGWINCH)
? (+#if defined (HAVE_GETPWENT))
Other patches are for rl_prompt and signals where there were enough upstream
readline modifications I do not think these patches are meaningfully
applicable anymore.
Unfortunately there is AFAIK usually (in some cases there is) no testcase of
readline.
Before 7.3 cut off I ask about the opinion on these MS-related platforms
compatibility readline patches, Fedora GNU/Linux runs fine with
readline-6.1-2.fc14 with readline-6.2-2.fc15 soon to be GA and also no
reported problems.
Thanks,
Jan
next reply other threads:[~2011-03-22 15:43 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-03-22 15:43 Jan Kratochvil [this message]
2011-03-22 16:43 ` Joel Brobecker
2011-03-22 16:58 ` Tom Tromey
2011-03-22 17:19 ` Kai Tietz
2011-03-22 19:05 ` Eli Zaretskii
2011-03-22 19:48 ` Jan Kratochvil
2011-03-22 19:59 ` Eli Zaretskii
2011-04-01 9:30 ` Eli Zaretskii
2011-04-01 14:19 ` Tom Tromey
2011-04-02 10:29 ` Eli Zaretskii
2011-04-03 3:01 ` Eli Zaretskii
2011-04-25 16:05 ` Jan Kratochvil
2011-04-02 20:10 ` Jan Kratochvil
2011-03-22 20:04 ` Tom Tromey
2011-04-01 9:25 ` Eli Zaretskii
2011-03-22 20:36 ` Joel Brobecker
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=20110322154327.GA8966@host1.jankratochvil.net \
--to=jan.kratochvil@redhat.com \
--cc=cgf-use-the-mailinglist-please@gnu.org \
--cc=eliz@gnu.org \
--cc=gdb@sourceware.org \
--cc=ktietz@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