Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Gustavo Zacarias <gustavo@zacarias.com.ar>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH 2/3] ncurses: bump to 5.9
Date: Fri, 27 Jul 2012 08:40:41 -0300	[thread overview]
Message-ID: <50127E39.5070302@zacarias.com.ar> (raw)
In-Reply-To: <20120727133851.53f50f0e@skate>

On 07/27/12 08:38, Thomas Petazzoni wrote:

> Le Fri, 27 Jul 2012 13:23:45 +0200,
> Arnout Vandecappelle <arnout@mind.be> a ?crit :
> 
>>   Does the segfault issue also occur on arm or powerpc?  Neither PTXdist
>> nor OE is a big i386 user, so maybe they just didn't notice the problem.
> 
> Yesterday, I tried on ARM Cortex-A8 within the Qemu VExpress emulation
> (using Linaro toolchain), and it segfaulted. I haven't tried on real
> hardware though, so could always be a Qemu problem, or a toolchain
> problem.
> 
> Thomas

I've tried on real hardware (arm, powerpc) and it's the same issue.
I'll do some tests on a chroot (i586 or x86_64) to try track it down
since it fails too, at least for i586.
Regards.

  reply	other threads:[~2012-07-27 11:40 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-07-26 18:49 [Buildroot] [PATCH 1/3] ncurses: get the post staging installation hook called properly Thomas Petazzoni
2012-07-26 18:49 ` [Buildroot] [PATCH 2/3] ncurses: bump to 5.9 Thomas Petazzoni
2012-07-26 19:15   ` Gustavo Zacarias
2012-07-26 20:33     ` Thomas Petazzoni
2012-07-27  6:59     ` Thomas Petazzoni
2012-07-27 10:21       ` Gustavo Zacarias
2012-07-27 10:28         ` Thomas Petazzoni
2012-07-27 11:23           ` Arnout Vandecappelle
2012-07-27 11:27             ` Gustavo Zacarias
2012-07-27 11:38             ` Thomas Petazzoni
2012-07-27 11:40               ` Gustavo Zacarias [this message]
2012-07-26 18:49 ` [Buildroot] [PATCH 3/3] gpsd: remove patch to handle ncurses5-config custom location Thomas Petazzoni

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=50127E39.5070302@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