From: Sergio Monteiro Basto <sergio@sergiomb.no-ip.org>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH] ncurses: version bump to 5.8
Date: Thu, 21 Apr 2011 20:22:23 +0100 [thread overview]
Message-ID: <1303413743.6641.12.camel@segulix> (raw)
In-Reply-To: <878vv423zn.fsf@macbook.be.48ers.dk>
On Wed, 2011-04-20 at 20:05 +0200, Peter Korsgaard wrote:
> >>>>> "Sergio" == Sergio Monteiro Basto <sergio@sergiomb.no-ip.org> writes:
>
> Hi,
>
> Sergio> After you fix the build error, I wrote that we should built
> Sergio> ncurses with configure option --with-termlib=tinfo , which
> Sergio> Fedora use by default . And you wrote to make a "patch adding
> Sergio> optional tinfo build" , I done one draft of the patch.
>
> Sergio> Since this bug in runtime, seems to be with terminfo, build with option
> Sergio> --with-termlib=tinfo , doesn't solve the problem ?
>
> I haven't tried, but doesn't that just shuffle part of the ncurses
> functions into libtinfo? I don't right away see why that would fix
> anything, but I'll start a build now.
so, it fix anything ?
> Besides this hypothetical fix, is there any other reason why
> --with-termlib=tinfo would be preferable?
Well, What I know is.
Is a default of Fedora and seems to me that ncurses becomes better.
In fact builds libtinfo.so which will be use (when exist) in some others
packages, one of them is dialog.
I can't say nothing more for sure , but packages use libtinfo.so if they
exist by default, so probably will work better if lib exist.
Best regards,
--
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/20110421/16a29976/attachment.bin>
next prev parent reply other threads:[~2011-04-21 19:22 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
2011-04-20 18:05 ` Peter Korsgaard
2011-04-21 19:22 ` Sergio Monteiro Basto [this message]
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=1303413743.6641.12.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