From: MikeW <mw_phil@yahoo.co.uk>
To: buildroot@busybox.net
Subject: [Buildroot] problem generating c++ compiler for target arch
Date: Wed, 29 Nov 2006 17:45:52 +0000 (UTC) [thread overview]
Message-ID: <loom.20061129T184236-586@post.gmane.org> (raw)
In-Reply-To: 33518.80.176.236.13.1164226860.squirrel@mail.primefarm.co.uk
<lists@...> writes:
>
> OK,
>
> I managed to get buildroot to complete the build at last. Sadly, the c++
> compiler is b0rked.
>
> Looks like it's missing all sorts of libraries and things. Here is some
> sample output trying to compile a very simple program (C++ hello world):
>
> david <at> tulip:~/buildroot/build_arm/staging_dir/bin$ ./arm-linux-gcc foo.cpp
> /tmp/ccNH0d2c.o: In function `std::__verify_grouping(char const*, unsigned
> int, std::basic_string<char, std::char_traits<char>, std::allocator<char>
> > const&)':
> foo.cpp:(.text+0x20): undefined reference to `std::basic_string<char,
> std::char_traits<char>, std::allocator<char> >::size() const'
> foo.cpp:(.text+0x98): undefined reference to `std::basic_string<char,
> std::char_traits<char>, std::allocator<char> >::operator[](unsigned int)
> const'
...
>
> All sorts of things missing there - have I inadvertantly broken lots of
> buildroot?
>
> David
>
Did you specify libstdc++ in your menuconfig ?
MikeW
xxxgmane-paddingxxxxxxgmane-paddingxxxxxxgmane-paddingxxxxxxgmane-paddingxxx
xxxgmane-paddingxxxxxxgmane-paddingxxxxxxgmane-paddingxxxxxxgmane-paddingxxx
next prev parent reply other threads:[~2006-11-29 17:45 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-11-22 19:44 [Buildroot] problem generating c++ compiler for target arch lists at primefarm.co.uk
2006-11-22 20:02 ` Bernhard Fischer
2006-11-22 20:09 ` lists at primefarm.co.uk
2006-11-22 20:18 ` Bernhard Fischer
2006-11-22 20:21 ` lists at primefarm.co.uk
2006-11-29 17:45 ` MikeW [this message]
2006-11-29 17:52 ` David Prime
-- strict thread matches above, loose matches on Subject: below --
2006-11-22 18:06 lists at primefarm.co.uk
2006-11-22 18:52 ` Bernhard Fischer
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=loom.20061129T184236-586@post.gmane.org \
--to=mw_phil@yahoo.co.uk \
--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