From: Gustavo Zacarias <gustavo@zacarias.com.ar>
To: buildroot@busybox.net
Subject: [Buildroot] ncurses: build freezes without error with v5.7
Date: Wed, 14 Jul 2010 16:29:49 -0300 [thread overview]
Message-ID: <4C3E102D.50105@zacarias.com.ar> (raw)
In-Reply-To: <1279123755.7058.242.camel@cabbage.rehill.info>
On 07/14/2010 01:09 PM, Quotient Remainder wrote:
> The following appears when I try to build with ncurses enabled. No
> error is displayed but the tic command never returns. "top" shows that
> tic is using 100% of CPU time. I've let it run for 20 minutes or more
> and it doesn't progress any further.
> BR is current: c0e307b848d8de23e6f10a179c4f240c023c8b82.
> Toolchain is external, CodeSourcery ARM GNU/Linux 2009q3-67.
Try this patch from gentoo:
http://sources.gentoo.org/cgi-bin/viewvc.cgi/gentoo-x86/sys-libs/ncurses/files/ncurses-5.7-tic-cross-detection.patch?revision=1.1
Sounds a lot like your problem.
Regards.
next prev parent reply other threads:[~2010-07-14 19:29 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-07-14 16:09 [Buildroot] ncurses: build freezes without error with v5.7 Quotient Remainder
2010-07-14 19:29 ` Gustavo Zacarias [this message]
2010-07-15 11:09 ` Quotient Remainder
2010-07-15 12:06 ` Mitch Davis
2010-07-15 14:06 ` Quotient Remainder
2010-07-15 14:30 ` Mitch Davis
2010-07-15 14:44 ` Quotient Remainder
2010-07-15 16:33 ` Mitch Davis
2010-07-15 16:52 ` Quotient Remainder
2010-07-16 1:28 ` Mitch Davis
2010-07-16 9:25 ` Quotient Remainder
[not found] ` <AANLkTim6BMXBWILqIwNMe02j3PDl9TAWhT1n_pkUdBBI@mail.gmail.com>
[not found] ` <1279288154.15465.18.camel@dubciaranr1.verifone.com>
2010-07-19 10:31 ` Quotient Remainder
2010-07-19 11:39 ` Mitch Davis
2010-07-19 13:58 ` Quotient Remainder
2010-07-19 14:05 ` Thomas Petazzoni
2010-07-19 14:19 ` Quotient Remainder
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=4C3E102D.50105@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