From: Arnout Vandecappelle <arnout@mind.be>
To: buildroot@busybox.net
Subject: [Buildroot] error toolchain build for mips-linux-uclibc with BR2_INSTALL_LIBSTDCPP
Date: Fri, 27 Apr 2012 23:48:58 +0200 [thread overview]
Message-ID: <201204272348.59110.arnout@mind.be> (raw)
In-Reply-To: <4F991F94.50608@rfnetech.com>
On Thursday 26 April 2012 12:12:36 oreddy wrote:
> I have enabled BR2_INSTALL_LIBSTDCPP option in .config file and tried to build the toolchain I have received the following error:
>
>
> cp: cannot stat `/Reddy/11n_Build/Test/dev_main/build/gcc-4.3.3/build_mips/staging_dir/usr/mips-linux-uclibc/lib*/libstdc++.so*': No such file or directory
Did you do a clean rebuild?
Buildroot doesn't detect when you have changed the toolchain options,
so it may "forget" to perform some build steps (e.g. compiling the C++
library).
Regards,
Arnout
--
Arnout Vandecappelle arnout at mind be
Senior Embedded Software Architect +32-16-286540
Essensium/Mind http://www.mind.be
G.Geenslaan 9, 3001 Leuven, Belgium BE 872 984 063 RPR Leuven
LinkedIn profile: http://www.linkedin.com/in/arnoutvandecappelle
GPG fingerprint: 7CB5 E4CC 6C2E EFD4 6E3D A754 F963 ECAB 2450 2F1F
next prev parent reply other threads:[~2012-04-27 21:48 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <CAAawjsQQ0nc9HYYAegCTs6sRM+rwXhimyV83hB+jwR6bo1B=SA@mail.gmail.com>
2012-04-26 10:12 ` [Buildroot] error toolchain build for mips-linux-uclibc with BR2_INSTALL_LIBSTDCPP oreddy
2012-04-26 12:04 ` Thomas Petazzoni
2012-04-26 12:18 ` oreddy
2012-04-26 12:25 ` Thomas Petazzoni
2012-04-27 21:48 ` Arnout Vandecappelle [this message]
2012-04-26 8:58 chinna obireddy
2012-04-26 9:01 ` Thomas Petazzoni
[not found] ` <CAAawjsRW17mtajZ+3ttCWq7rv5qBn8QXyeA-OqjUuFmE_VhiAA@mail.gmail.com>
2012-04-26 9:41 ` chinna obireddy
2012-04-26 9:58 ` Thomas Petazzoni
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=201204272348.59110.arnout@mind.be \
--to=arnout@mind.be \
--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