Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
To: buildroot@busybox.net
Subject: [Buildroot] buildroot not support c++ compliing
Date: Fri, 8 Oct 2010 09:18:44 +0200	[thread overview]
Message-ID: <20101008091844.1afdb502@surf> (raw)
In-Reply-To: <1286511827.3703.11.camel@olyvine-desktop.logiways-sz.cn>

Hello,

On Fri, 08 Oct 2010 12:23:47 +0800
"olyvine.chen at logiways.com.cn" <olyvine.chen@logiways.com.cn> wrote:

>   I now try to add package libmusicbrainz to buildroot, but many
> errors happen, such as the following:
> 
> *************************************************************************
> 
> buildroot/output/build/libmusicbrainz-3.0.2/src/artist.cpp:23:18:
> error: string: No such file or directory
> 
> *************************************************************************
>   it seems indicate that no c++ library available, then how to enable
> c ++ compiling for buildroot? 
>         
>   I enabled glibc via:
>   Toolchain => Toolchain type (External toolchain) => External
> toolchain C library (glibc)

Which external toolchain are you using ?

Thomas
-- 
Thomas Petazzoni, Free Electrons
Kernel, drivers, real-time and embedded Linux
development, consulting, training and support.
http://free-electrons.com

  reply	other threads:[~2010-10-08  7:18 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-10-08  4:23 [Buildroot] buildroot not support c++ compliing olyvine.chen at logiways.com.cn
2010-10-08  7:18 ` Thomas Petazzoni [this message]
2010-10-08  8:17   ` olyvine.chen at logiways.com.cn
2010-10-08  8:28     ` Phil Edworthy
2010-10-08  8:44     ` Thomas Petazzoni
2010-10-08  8:52       ` Lionel Landwerlin
2010-10-09  9:50         ` 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=20101008091844.1afdb502@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox