From: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
To: buildroot@busybox.net
Subject: [Buildroot] wvstreams configure error
Date: Tue, 28 Dec 2010 11:33:23 +0100 [thread overview]
Message-ID: <20101228113323.6b7c982d@surf> (raw)
In-Reply-To: <1293529540.15318.34.camel@olyvine-desktop.logiways-sz.cn>
On Tue, 28 Dec 2010 17:45:40 +0800
"olyvine.chen at logiways.com.cn" <olyvine.chen@logiways.com.cn> wrote:
> Thanks for your reply, and I check the config.log, and find CXX compiler
> is missing, then how to pass the argument to configure to enable CXX ?
> ####################################################################
> configure:8427: result: no
> configure:8461: checking for openssl/ssl.h
> configure:8482: false -c -Os -pipe -Os -D_LARGEFILE_SOURCE
> -D_LARGEFILE64_SOURCE -D_FILE_OFFSET_BITS=64 --sysroot ????/staging/
> -Iyes/include conftest.cpp >&5
Presumably, you forgot to enable BR2_TOOLCHAIN_BUILDROOT_CXX, and so
you don't have a C++ cross-compiler. Your project should therefore
"depends on BR2_INSTALL_LIBSTDCPP" in its Config.in.
However, the "????" string for the sysroot argument is a bit strange.
It should be that way. Is it you that edited the log to not show the
full location of your staging directory ?
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 10:33 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
2010-12-28 9:45 ` olyvine.chen at logiways.com.cn
2010-12-28 10:33 ` Thomas Petazzoni [this message]
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=20101228113323.6b7c982d@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.