From: Patrick Palka <patrick@parcs.ath.cx>
To: Pedro Alves <palves@redhat.com>
Cc: "gdb-patches@sourceware.org" <gdb-patches@sourceware.org>,
Eli Zaretskii <eliz@gnu.org>,
Sergio Durigan Junior <sergiodj@redhat.com>
Subject: Re: [PATCH] Sync readline/ to version 7.0 alpha
Date: Sat, 25 Jul 2015 15:34:00 -0000 [thread overview]
Message-ID: <CA+C-WL8BAJ=LUg59Uu8J8_xDqe4wGsOja5-CYcT_pD9Egd_JPA@mail.gmail.com> (raw)
In-Reply-To: <55B1FB46.5000106@redhat.com>
On Fri, Jul 24, 2015 at 4:45 AM, Pedro Alves <palves@redhat.com> wrote:
> On 07/15/2015 03:35 AM, Patrick Palka wrote:
>> This patch syncs our upstream copy of readline from version 6.2 to the
>> latest version, 7.0 alpha (released July 10 2015).
>>
>> I essentially copied what was done the last time readline was synced,
>> when Jan updated to readline 6.2 in 2011:
>> http://sourceware.org/ml/gdb-patches/2011-05/msg00003.html
>
>
>> Getting this kind of change in at the start of the GDB 7.11 development
>> cycle will allow us to get a lot of passive testing from developers and
>> from bleeding-edge users.
>
> I agree; if this helps find readline issues that affect GDB before
> readline is released, it'll be a win, because distros tend to use the
> system readline instead of the one we bundle.
>
>> [And as new versions of readline 7.0 are
>> released, I will try to sync our local copy promptly.]
>>
>
> Thanks.
>
>> Since the patch is too big to send inline, I pushed it to
>> users/ppalka/readline-7.0-update. Hopefully that is more convenient that
>> sending it as a compressed attachment.
>
> Indeed it is. Thanks.
>
>>
>> readline/ChangeLog.gdb:
>>
>> Import readline 7.0 alpha
>> * configure: Regenerate.
>> * examples/rlfe/configure: Regenerate.
>>
>> gdb/ChangeLog:
>>
>> * completer.c (gdb_printable_part): Sync with readline function
>> it is based off of.
>>
>> gdb/testsuite/ChangeLog:
>>
>> * gdb.gdb/selftest.exp (test_with_self): Update test to now
>> expect the GDB inferior to no longer immediately stop after
>> being resumed with "signal SIGINT".
>
> Looks good to me.
Thanks for reviewing. I pushed this patch earlier today and not
surprisingly the buildbot caught some build failures. The ultimate
cause of these failures is that readline now builds shared libraries
by default alongside static libraries. I pushed a patch that disables
the building of readline's shared libraries by default.
>
> Thanks,
> Pedro Alves
>
next prev parent reply other threads:[~2015-07-25 15:34 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-07-15 2:35 Patrick Palka
2015-07-23 0:28 ` Patrick Palka
2015-07-24 8:46 ` Pedro Alves
2015-07-25 15:34 ` Patrick Palka [this message]
2015-07-25 19:15 ` Doug Evans
2015-07-25 19:29 ` Patrick Palka
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='CA+C-WL8BAJ=LUg59Uu8J8_xDqe4wGsOja5-CYcT_pD9Egd_JPA@mail.gmail.com' \
--to=patrick@parcs.ath.cx \
--cc=eliz@gnu.org \
--cc=gdb-patches@sourceware.org \
--cc=palves@redhat.com \
--cc=sergiodj@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