Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Sergio Monteiro Basto <sergio@sergiomb.no-ip.org>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH] ncurses: version bump to 5.8
Date: Wed, 20 Apr 2011 18:55:02 +0100	[thread overview]
Message-ID: <1303322103.8512.4.camel@segulix> (raw)
In-Reply-To: <87pqogj49u.fsf@macbook.be.48ers.dk>

On Wed, 2011-04-20 at 18:06 +0200, Peter Korsgaard wrote: 
> >>>>> "Sergio" == Sergio Monteiro Basto <sergio@sergiomb.no-ip.org> writes:
> 
>  Sergio> On Mon, 2011-04-04 at 12:31 +0200, Peter Korsgaard wrote:
>  >> The problem is a null pointer access in tgetent. It seems to load the
>  >> terminfo file ok, but something goes wrong.
> 
>  Sergio> https://bugs.busybox.net/show_bug.cgi?id=2845
> 
>  Sergio> we shoun't build curses with --with-termlib=tinfo 
> 
> Does that have anything to do with the crash? Your bug report (which I
> cannot reproduce) seems to be related to a build error rather than a
> runtime one.

https://bugs.busybox.net/show_bug.cgi?id=2845#c7

After you fix the build error, I wrote that we should built ncurses with
configure option  --with-termlib=tinfo , which Fedora use by default .
And you wrote to make a "patch adding optional tinfo build" , I done one
draft of the patch.

Since this bug in runtime, seems to be with terminfo, build with option
--with-termlib=tinfo , doesn't solve the problem ? 

> I've now just tested with a glibc toolchain (E.G
> qemu_arm_versatile_defconfig and select external codesourcery 2010.09
> toolchain) and stuff using ncurses (I tried htop) also crashes here, so
> it doesn't seem to be something specific to uclibc.
> 
> I've also tested ncurses 5.9 with the same results. with 2011.05 getting
> quite near, perhaps the best approach is to revert to ncurses 5.7?
> 

-- 
S?rgio M. B.
-------------- next part --------------
A non-text attachment was scrubbed...
Name: smime.p7s
Type: application/x-pkcs7-signature
Size: 3309 bytes
Desc: not available
URL: <http://lists.busybox.net/pipermail/buildroot/attachments/20110420/301f26a2/attachment.bin>

  reply	other threads:[~2011-04-20 17:55 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-03-23 23:42 [Buildroot] [PATCH] ncurses: version bump to 5.8 Mike Frysinger
2011-03-27 20:55 ` Peter Korsgaard
2011-04-04 10:31 ` Peter Korsgaard
2011-04-04 15:51   ` Mike Frysinger
2011-04-04 19:08     ` Peter Korsgaard
2011-04-04 19:17       ` Mike Frysinger
2011-04-04 19:28         ` Peter Korsgaard
2011-04-04 21:22   ` Sergio Monteiro Basto
2011-04-20 16:06     ` Peter Korsgaard
2011-04-20 17:55       ` Sergio Monteiro Basto [this message]
2011-04-20 18:05         ` Peter Korsgaard
2011-04-21 19:22           ` Sergio Monteiro Basto
2011-04-21 21:04             ` Peter Korsgaard
2011-04-21 22:29               ` Mike Frysinger
2011-04-22  2:11                 ` Sergio Monteiro Basto
2011-04-22 21:27                   ` Mike Frysinger
2011-04-22  5:27                 ` Peter Korsgaard
2011-04-22 15:25                   ` Heiko Zuerker
2011-04-22 19:39                     ` Peter Korsgaard
2011-04-22 20:23                       ` Heiko Zuerker

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=1303322103.8512.4.camel@segulix \
    --to=sergio@sergiomb.no-ip.org \
    --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