From: Ulf Samuelsson <ulf@atmel.com>
To: buildroot@busybox.net
Subject: [Buildroot] Building GCC/C++ compilers using Buildroot
Date: Sun, 8 Apr 2007 10:01:56 +0200 [thread overview]
Message-ID: <01d901c779b6$221ca5a0$dcc4af0a@atmel.com> (raw)
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
Then tried gcc-4.2 and binutils-2.17 failed.
Looked into the error messages and found that the problem
seems to occur when building the C++ compilers.
Now trying gcc-4.1.2 and binutils-2.17 without C++ compilers.
Whats is a recommended combination of gcc and binutils
if you want to have a c++ cross compiler?
Best Regards
Ulf Samuelsson ulf at atmel.com
Atmel Nordic AB
Mail: Box 2033, 174 02 Sundbyberg, Sweden
Visit: Kavalleriv?gen 24, 174 58 Sundbyberg, Sweden
Phone +46 (8) 441 54 22 Fax +46 (8) 441 54 29
GSM +46 (706) 22 44 57
Technical support when I am not available:
AT90 AVR Applications Group: mailto:avr at atmel.com
AT91 ARM Applications Group: mailto:at91support at atmel.com
AVR32 Applications Group mailto:avr32 at atmel.com
http://www.avrfreaks.net/; http://avr32linux.org/
http://www.at91.com/ ; ftp://at91dist:distrib at 81.80.104.162/
next reply other threads:[~2007-04-08 8:01 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-04-08 8:01 Ulf Samuelsson [this message]
2007-04-10 7:59 ` [Buildroot] Building GCC/C++ compilers using Buildroot Philippe Ney
2007-04-10 8:05 ` Bernhard Fischer
2007-04-10 9:02 ` Ulf Samuelsson
2007-04-10 10:18 ` Bernhard Fischer
[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='01d901c779b6$221ca5a0$dcc4af0a@atmel.com' \
--to=ulf@atmel.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