From: Bernhard Fischer <rep.dot.nop@gmail.com>
To: buildroot@busybox.net
Subject: [Buildroot] Building GCC/C++ compilers using Buildroot
Date: Tue, 10 Apr 2007 12:18:39 +0200 [thread overview]
Message-ID: <20070410101838.GA15274@aon.at> (raw)
In-Reply-To: <011e01c77b4f$50a67eb0$dcc4af0a@atmel.com>
On Tue, Apr 10, 2007 at 11:02:00AM +0200, Ulf Samuelsson wrote:
>> On Sun, Apr 08, 2007 at 10:01:56AM +0200, Ulf Samuelsson wrote:
>>>Tried to upgrade my ARM gcc-3.4.6 compiler in buildroot
>>>My host compiler is gcc-4.1.2 running on OpenSuse 10.2.
>>>
>>>First tried gcc-4.2 and latest supported binutils - Failed
>>
>> The snapshot-date is from sjhill and is outdated. I use the
>> gcc-4_2-branch, c, c++, fortran frontends work fine. If one of those
>> fails, i'm interrested in hearing about it (at least about c and
>> fortran; c++ lacks uClibc++ integration/support so isn't interresting
>> for me and i don't have spare-time to look into it).
>>
>
>The failure was when building the C++ compiler.
>
>Are you saying that you cannot build a g++ compiler using buildroot and uClibc?
I'm saying that the snapshot-date from gcc-4.2 is one sjhill used at one
point -- or still uses, i don't know= and that gcc-4.2 from the 4_2-branch
-- which i'm using -- can build a c, c++ and fortran frontend just fine.
Furthermore i'm observing that we do not (yet, patches welcome) use
uClibc++ (http://cxx.uclibc.org/ for your convenience) for gcc in
buildroot.
next prev parent reply other threads:[~2007-04-10 10:18 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-04-08 8:01 [Buildroot] Building GCC/C++ compilers using Buildroot Ulf Samuelsson
2007-04-10 7:59 ` Philippe Ney
2007-04-10 8:05 ` Bernhard Fischer
2007-04-10 9:02 ` Ulf Samuelsson
2007-04-10 10:18 ` Bernhard Fischer [this message]
[not found] ` <001d01c77b59$33037980$dcc4af0a@atmel.com>
[not found] ` <20070410102946.GB15274@aon.at>
[not found] ` <002301c77b60$51d44090$dcc4af0a@atmel.com>
[not found] ` <20070410120053.GA16257@aon.at>
2007-04-10 13:11 ` [Buildroot] eric, please comment [was: [buildroot] Re: BSP patch] Ulf Samuelsson
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=20070410101838.GA15274@aon.at \
--to=rep.dot.nop@gmail.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox