From: oreddy <oreddy@rfnetech.com>
To: buildroot@busybox.net
Subject: [Buildroot] error toolchain build for mips-linux-uclibc with BR2_INSTALL_LIBSTDCPP
Date: Thu, 26 Apr 2012 20:18:45 +0800 [thread overview]
Message-ID: <4F993D25.8070906@rfnetech.com> (raw)
In-Reply-To: <20120426140413.3f394243@skate>
On 26/4/2012 8:04 PM, Thomas Petazzoni wrote:
> Le Thu, 26 Apr 2012 18:12:36 +0800,
> oreddy<oreddy@rfnetech.com> a ?crit :
>
>> Build root version 2009.08 and i have attached the config file.
> Can you try with a more recent Buildroot version? It's very unlikely
> that the community will be interested in fixing problems on such an old
> version, especially since we have done a lot of changes and
> improvements in Buildroot over the last few years, so 2009.08 is quite
> radically different from 2012.02 that we would recommend to use.
>
> Best regards,
>
> Thomas
Thomas,
Yeah absolutely correct, but I think it needs more time to test the
whole build and applications running on it again.
Anyhow when I was goggling, found a patch
http://git.buildroot.net/buildroot/commit/?id=6b578c8d73b6403e3be8bddf611fb1059d7c2f4b
which is more related to this issue. Will try this and come back.
Last option is to try a new build root.
Regards,
Reddy.
next prev parent reply other threads:[~2012-04-26 12:18 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 [this message]
2012-04-26 12:25 ` Thomas Petazzoni
2012-04-27 21:48 ` Arnout Vandecappelle
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=4F993D25.8070906@rfnetech.com \
--to=oreddy@rfnetech.com \
--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.