From: Enrico Scholz <enrico.scholz@sigma-chemnitz.de>
To: openembedded-devel@lists.openembedded.org
Cc: martin.jansa@gmail.com
Subject: Re: We need newer ncurses Was: Host Environment affect on target builds
Date: Sat, 05 Jun 2010 15:36:59 +0200 [thread overview]
Message-ID: <lypr058utg.fsf@ensc-virt.intern.sigma-chemnitz.de> (raw)
In-Reply-To: <20100605055722.GR16035@jama> (Martin Jansa's message of "Sat, 5 Jun 2010 07:57:22 +0200")
Martin Jansa <martin.jansa@gmail.com> writes:
> BTW: 5.4 is >6years old, 5.7 ~2years old (latest)
>
> Is someone already working on newer ncurses recipes?
https://www.cvg.de/people/ensc/ncurses_5.7.bb
Problem with ncurses is, that it needs a patched autoconf 2.13 to do
the full autoconf step. Recipe above uses shipped ./configure. Newer
ncurses need some termcap/tinfo related changes in multiple packages
too and I did not had time to clean them all up for submission.
Enrico
next prev parent reply other threads:[~2010-06-05 13:41 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-06-05 1:19 Host Environment affect on target builds Ambrose, Martin
2010-06-05 5:57 ` We need newer ncurses Was: " Martin Jansa
2010-06-05 13:36 ` Enrico Scholz [this message]
2010-06-19 18:52 ` Klaus 'mrmoku' Kurzmann
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=lypr058utg.fsf@ensc-virt.intern.sigma-chemnitz.de \
--to=enrico.scholz@sigma-chemnitz.de \
--cc=martin.jansa@gmail.com \
--cc=openembedded-devel@lists.openembedded.org \
/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