Openembedded Devel Discussions
 help / color / mirror / Atom feed
From: Mike Westerhof <mike@mwester.net>
To: openembedded-devel <openembedded-devel@lists.openembedded.org>
Subject: ncurses 5.7 doesn't build libtermcap anymore?
Date: Sat, 28 Aug 2010 21:36:52 -0500	[thread overview]
Message-ID: <4C79C7C4.1050304@mwester.net> (raw)

I've been working on some recent problems that popped up in the SlugOS
feeds; one that appeared recently is that asterisk no longer builds;
configure complains about -ltermcap, and investigation shows that
indeed, libtermcap is missing.  It seems that the new ncurses recipe
(5.7) no longer builds it for some reason.  I think the same problem is
the root cause for the failure of js to build as well.

So I guess the first question is if this is intentional or not?  If it
is, then I guess I'll modify the asterisk recipe to remove the
dependency and submit that patch.  Otherwise, well, I guess I could
attempt to debug and fix the ncurses recipe, but it looks a bit, um,
"non-trivial" so any advice would be appreciated.

Or should I just pin ncurses to the old 5.4 version that worked?

Thanks,
-Mike



             reply	other threads:[~2010-08-29  2:44 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-08-29  2:36 Mike Westerhof [this message]
2010-08-29  8:36 ` ncurses 5.7 doesn't build libtermcap anymore? Khem Raj
2010-08-29 10:02 ` Eric Bénard
2010-08-29 10:39   ` [PATCH] sdk.bbclass: allow virtclass-sdk override Eric Bénard
2010-08-29 10:45   ` [PATCH] ncurses-5.7 : fix sdk build + add libtermcap link Eric Bénard
2010-08-29 11:22     ` [PATCH v2] " Eric Bénard
2010-08-29 13:33       ` Enrico Scholz
2010-08-29 14:30         ` Eric Bénard
2010-08-29 20:08           ` Enrico Scholz
2010-08-29 20:40             ` Eric Bénard
2010-08-29 20:10   ` ncurses 5.7 doesn't build libtermcap anymore? Enrico Scholz
2010-08-29 10:31 ` Enrico Scholz

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=4C79C7C4.1050304@mwester.net \
    --to=mike@mwester.net \
    --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