Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Gustavo Zacarias <gustavo@zacarias.com.ar>
To: buildroot@busybox.net
Subject: [Buildroot] [Bug-readline] IPython/readline segfaults
Date: Wed, 25 Mar 2015 11:07:29 -0300	[thread overview]
Message-ID: <5512C121.7040707@zacarias.com.ar> (raw)
In-Reply-To: <5512BF40.5000702@vu.nl>

On 03/25/2015 10:59 AM, ir. Tjeerd Pinkert wrote:

> On 25-03-15 14:21, Gustavo Zacarias wrote:
>> On 03/25/2015 07:55 AM, ir. Tjeerd Pinkert wrote:
>>
>>> Thanks, indeed, buildroot 2015.02 has 6.3 with no patches, although it
>>> downloads the latest tar file. I'm trying to see if patching helps.
>>
>> I've sent a patch to bump it to patchlevel 8 after the 2015.02 release
>> for another bug in commit b817e8c58117402561a61c0d749337f415c9c985
>> (bash-related).
>> So it'll be part of the 2015.05 release, or if you're in a rush just
>> apply that patch to your tree.
> 
> I have tested it, and the patch works, no more segfaults so far.
> 
> I attach the patch file for buildroot, Gustavo, can you tell me if I did
> it in a correct way? Did you already include this one in buildroot too?
> I could not get the original patch working with the buildroot system so
> I generated my own diff which works for buildroot (that is
> readline-0001-63-002.patch). I saw there are more patches for readline
> 6.3 available.

Hi.
No need to CC Mike or the readline list, as far as they're concerned
this was already fixed with the patches upstream.
Well, it's easy, fetch the patch:

$ wget
"http://git.buildroot.net/buildroot/patch/?id=b817e8c58117402561a61c0d749337f415c9c985"
-O readline.patch

Apply the patch:

buildroot-2015.02 $ patch -p1 <readline.patch

And yes, the patches need a little tweak to apply cleanly (the patch
prefixing is done in a somewhat odd way), but i've handled that in the
patch i've sent for buildroot inclusion.
Regards.

      reply	other threads:[~2015-03-25 14:07 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <55116D12.1000106@vu.nl>
     [not found] ` <5511B114.60704@case.edu>
     [not found]   ` <20150325003203.GL10761@vapier>
2015-03-25 10:55     ` [Buildroot] [Bug-readline] IPython/readline segfaults ir. Tjeerd Pinkert
2015-03-25 13:21       ` Gustavo Zacarias
2015-03-25 13:59         ` ir. Tjeerd Pinkert
2015-03-25 14:07           ` Gustavo Zacarias [this message]

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=5512C121.7040707@zacarias.com.ar \
    --to=gustavo@zacarias.com.ar \
    --cc=buildroot@busybox.net \
    /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