From: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH 2/3] ncurses: bump to 5.9
Date: Thu, 26 Jul 2012 22:33:02 +0200 [thread overview]
Message-ID: <20120726223302.4f773e96@skate> (raw)
In-Reply-To: <50119743.3090505@zacarias.com.ar>
Le Thu, 26 Jul 2012 16:15:15 -0300,
Gustavo Zacarias <gustavo@zacarias.com.ar> a ?crit :
> > After this bump, I build tested a large number of the ncurses reverse
> > dependencies we have in Buildroot, and they all built fine.
> >
> > Signed-off-by: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
>
> Nack.
> The version bump to 5.8 and 5.9 had issues in the past and still has.
> It may compile just fine but it segfaults miserably in a target, chroot
> or qemu image.
> Simple test, i586 target with external toolchain, build less and see.
> Regards.
Yes, I just did some runtime testing, and also faced segfaults. Now
that you say it, I also remember what you said.
Thanks!
Thomas
--
Thomas Petazzoni, Free Electrons
Kernel, drivers, real-time and embedded Linux
development, consulting, training and support.
http://free-electrons.com
next prev parent reply other threads:[~2012-07-26 20:33 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 [this message]
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
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=20120726223302.4f773e96@skate \
--to=thomas.petazzoni@free-electrons.com \
--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