From: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
To: buildroot@busybox.net
Subject: [Buildroot] wvstreams configure error
Date: Tue, 28 Dec 2010 10:13:13 +0100 [thread overview]
Message-ID: <20101228101313.0e257c8b@surf> (raw)
In-Reply-To: <1293525765.15318.24.camel@olyvine-desktop.logiways-sz.cn>
On Tue, 28 Dec 2010 16:42:45 +0800
"olyvine.chen at logiways.com.cn" <olyvine.chen@logiways.com.cn> wrote:
> I now run into an error when configure wvstreams as following:
> ##################################################################################
> make[2]: Circular wvstreams-depends <- wvstreams dependency dropped.
Hum, this message is strange.
> configure: error: Required dependencies missing: OpenSSL>=0.9.7 zlib
It says OpenSSL and zlib are *required* dependencies, so:
> ifeq ($(BR2_PACKAGE_OPENSSL),y)
> WVSTREAMS_CONF_OPT+=--with-openssl
> WVSTREAMS_DEPENDENCIES+=openssl
> else
> WVSTREAMS_CONF_OPT+=--without-openssl
> endif
This should just be:
WVSTREAMS_CONF_OPT+=--with-openssl
WVSTREAMS_DEPENDENCIES+=openssl
and the package should "select BR2_PACKAGE_OPENSSL"
> ifeq ($(BR2_PACKAGE_ZLIB),y)
> WVSTREAMS_CONF_OPT+=--with-zlib=$(STAGING_DIR)
> WVSTREAMS_DEPENDENCIES+=zlib
> else
> WVSTREAMS_CONF_OPT+=--without-zlib
> endif
This should just be:
WVSTREAMS_CONF_OPT+=--with-zlib=$(STAGING_DIR)
WVSTREAMS_DEPENDENCIES+=zlib
and the package should "select BR2_PACKAGE_ZLIB"
Then, if zlib and openssl are still not found while being compiled
before wvstreams, then you'll have to look at wvstreams config.log file
to see why it cannot find them.
Regards,
Thomas
--
Thomas Petazzoni, Free Electrons
Kernel, drivers, real-time and embedded Linux
development, consulting, training and support.
http://free-electrons.com
next prev parent reply other threads:[~2010-12-28 9:13 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-12-28 8:42 [Buildroot] wvstreams configure error olyvine.chen at logiways.com.cn
2010-12-28 9:13 ` Thomas Petazzoni [this message]
2010-12-28 9:45 ` olyvine.chen at logiways.com.cn
2010-12-28 10:33 ` Thomas Petazzoni
2010-12-28 10:31 ` olyvine.chen at logiways.com.cn
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=20101228101313.0e257c8b@surf \
--to=thomas.petazzoni@free-electrons.com \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.