All of 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 12:59:10 +0100	[thread overview]
Message-ID: <20061115125910.a375dcbd.philippe.ney@pardes.ws> (raw)
In-Reply-To: <22099.82.171.61.116.1163581168.squirrel@webmail.aerende.com>

> Hi,
>     Is it possible to generate a C++ (g++) cross compiler
> for ARM usng buildroot?  I have been able to generate
> a GCC cross compiler for ARM using buildroot.
> 
> Thanks for any pointers.

Sure.

$ make menuconfig

And check the right box.

Philippe

  reply	other threads:[~2006-11-15 11:59 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 [this message]
2006-11-15 15:04   ` nina.holly at aerende.com
2006-11-15 16:33     ` Philippe Ney
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=20061115125910.a375dcbd.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 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.