From: "Peter Hüwe" <PeterHuewe@gmx.de>
To: buildroot@busybox.net
Subject: [Buildroot] configure looks in /usr for ncurses headers?
Date: Wed, 28 Jul 2010 19:02:42 +0200 [thread overview]
Message-ID: <201007281902.43312.PeterHuewe@gmx.de> (raw)
Hi,
today I tried to bump the pidgin/finch multimessenger to version 2.7.2 which
was released several days ago.
But before I tried to bump the version, I tried to build the 2.7.1 version
I've submitted about a month ago - but (as almost expected) the build failed
with the following message:
checking for initscr in -lncursesw... (cached) yes
checking for update_panels in -lpanelw... (cached) yes
checking /usr/include/ncursesw/ncurses.h usability... no
checking /usr/include/ncursesw/ncurses.h presence... no
checking for /usr/include/ncursesw/ncurses.h... no
checking /usr/include/ncurses.h usability... yes
checking /usr/include/ncurses.h presence... yes
checking for /usr/include/ncurses.h... yes
checking if /usr/include/ncurses.h supports wide characters... no
configure: error:
Finch will not be built. You need to install ncursesw (or ncurses) and its
development headers.
Why does configure (now) look in /usr/include and not
.../buildroot/output/staging/usr/include ?
Or is /usr/include correct? - if yes why could I build the package back then
and not now? (same source version of pidgin, no changes in config)
Thanks,
Peter
reply other threads:[~2010-07-28 17:02 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=201007281902.43312.PeterHuewe@gmx.de \
--to=peterhuewe@gmx.de \
--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