From: Bernhard Fischer <rep.nop@aon.at>
To: buildroot@busybox.net
Subject: [Buildroot] C++ cross compiler
Date: Thu, 16 Nov 2006 17:37:58 +0100 [thread overview]
Message-ID: <20061116163758.GA26680@aon.at> (raw)
In-Reply-To: <loom.20061115T164509-569@post.gmane.org>
On Wed, Nov 15, 2006 at 03:50:52PM +0000, MikeW wrote:
> <nina.holly@...> writes:
>
>>
>> Hi Mike,
>> The build completes without an error, just no
>> arm-linux-g++ compiler gets built. So I'm not sure
>> if the patch would fix the problem.
>>
>> Nina
>>
>Must be something more fundamental wrong - you'll have to try (e.g.)
For a native compiler on the target, make sure to set
BR2_PACKAGE_GCC_TARGET=y
next prev parent reply other threads:[~2006-11-16 16:37 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
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 [this message]
[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=20061116163758.GA26680@aon.at \
--to=rep.nop@aon.at \
--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