From: "Hans-Bernhard Bröker" <HBBroeker@t-online.de>
To: cygwin@cygwin.com
Subject: Re: configure script fails during install (Setup Ver 2.897 (64 bit))
Date: Mon, 04 Nov 2019 17:18:00 -0000 [thread overview]
Message-ID: <506003de-7a2a-267b-e32b-ed67f55f9ff1@t-online.de> (raw)
In-Reply-To: <BY5PR12MB39405F3DF67CB86A9EB80E37B57F0@BY5PR12MB3940.namprd12.prod.outlook.com>
Am 04.11.2019 um 02:06 schrieb Lawrence Clooney:
> Error Message:
> checking whether to use NLS... no
> checking for initscr in -lncurses... yes
> checking ncurses.h usability... yes
> checking ncurses.h presence... yes
> checking for ncurses.h... yes
> checking for Berkeley DB db.h version >= 4.1 ... no (version numbers not found)
> configure: error: Berkeley DB db.h is missing or has incompatible version
No, that does not mean that the configure script failed. It means the
configure script determined that your build machine lacks some
capabilities this program needs, and thus refused to continue. As
that's exactly what the script is supposed to do, it cannot be qualified
as a failure.
You will have to install the required packages to satisfy that
dependency. In the case at hand, that would be libdb-devel (current
version 5.3.28-2).
What did fail here is either the sequence of instructions you followed
(because they really should have told you to install that package), or
your following of same (if they did tell you, but you didn't).
--
Problem reports: http://cygwin.com/problems.html
FAQ: http://cygwin.com/faq/
Documentation: http://cygwin.com/docs.html
Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple
prev parent reply other threads:[~2019-11-04 17:18 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-11-04 1:06 Lawrence Clooney
2019-11-04 7:19 ` Brian Inglis
2019-11-04 17:18 ` Hans-Bernhard Bröker [this message]
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=506003de-7a2a-267b-e32b-ed67f55f9ff1@t-online.de \
--to=hbbroeker@t-online.de \
--cc=cygwin@cygwin.com \
/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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).