Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Philippe Ney <philippe.ney@pardes.ws>
To: buildroot@busybox.net
Subject: [Buildroot] C++ cross compiler
Date: Wed, 15 Nov 2006 17:33:37 +0100	[thread overview]
Message-ID: <20061115173337.96dab87f.philippe.ney@pardes.ws> (raw)
In-Reply-To: <23833.82.171.61.116.1163603087.squirrel@webmail.aerende.com>

> Hi Philippe,
>     Could you tell me how you were able to
> create a c++ cross compiler for ARM?   I.E.
> can you tell me which boxes you checked?
> 
>     The following is what I did which doesn't
> seem to work.
> 
> In make menuconfig in the "toolchain" menu I checked
> 
> [*] Build/install c++ compiler and libstdc++

OK

> and it ended up setting in .config :
> 
> BR2_INSTALL_LIBSTDCPP=y

OK

> but did not set:
> 
> BR2_PACKAGE_LIBCGICC or
> BR2_PACKAGE_QTE

That's packages. Nothing to do with the compiler

> After running make, arm-linux-g++ does not show up in the
> bin directory specified in the "Build options" menu section
> for "Toolchain and header file location".
> 
> 1. Is there another make menuconfig option that needs to
>    be set to build a C++ cross compiler?
> 
> 2. When I googled "buildroot c++ cross compiler" other people
>    were not able to create a c++ cross compiler w/buildroot and
>    I didn't see a clear resolution from the responses.

You ought to have something like :

buildroot/build_arm_nofpu/staging_dir/bin/arm-linux-uclibc-g++

(gcc-4.0.3 / binutils-2.17 / uClibc-0.9.28)

If the c++ support is not generated in your compiler, maybe you have to
check in the corresponding .mk file if the right parameters are used.


Philippe

  reply	other threads:[~2006-11-15 16:33 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-11-15  8:59 [Buildroot] C++ cross compiler nina.holly at aerende.com
2006-11-15 11:59 ` Philippe Ney
2006-11-15 15:04   ` nina.holly at aerende.com
2006-11-15 16:33     ` Philippe Ney [this message]
2006-11-15 14:47 ` MikeW
2006-11-15 15:20   ` nina.holly at aerende.com
2006-11-15 15:50     ` MikeW
2006-11-16 16:37       ` Bernhard Fischer
     [not found]         ` <16888.82.171.61.116.1163702830.squirrel@webmail.aerende.com>
2007-04-19 12:32           ` [Buildroot] web browser with buildroot/uClibc and Qtopia 4 nina.holly at aerende.com
  -- strict thread matches above, loose matches on Subject: below --
2006-11-26 22:46 [Buildroot] c++ cross compiler David Prime
     [not found] ` <39d7ed000611261547r44bf1d47j1fe03b69c6e44cc4@mail.gmail.com>
2006-11-27  9:55   ` David Prime
     [not found]     ` <39d7ed000611270157n68ce8222o7079898ca2185acc@mail.gmail.com>
2006-11-27 10:01       ` David Prime
     [not found]         ` <39d7ed000611270203k2d20b505t532c809f63088a1b@mail.gmail.com>
2006-11-27 10:36           ` David Prime
     [not found]             ` <39d7ed000611270240q19434dfj192de4494f52a996@mail.gmail.com>
2006-11-27 11:07               ` David Prime

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=20061115173337.96dab87f.philippe.ney@pardes.ws \
    --to=philippe.ney@pardes.ws \
    --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