From: Martin Banky <martin.banky@gmail.com>
To: buildroot@busybox.net
Subject: [Buildroot] [Review] Add gcc 4.5.1
Date: Mon, 20 Sep 2010 15:03:14 -0700 [thread overview]
Message-ID: <1285020197-30269-1-git-send-email-Martin.Banky@gmail.com> (raw)
This is the first pass at adding gcc 4.5.1 to buildroot. It builds fine for the
host and the target. The question I have, is the implementation the correct
way to change the toolchain? I couldn't find a lot of documentation regarding
the toolchain (as far as changing or updating it). Also, can the toolchain mk
files be updated to the new format or are their builds too complex?
[PATCH 1/3] dbus: bump to 1.4.0
[PATCH 2/3] m4: bump to 1.4.15
[PATCH 3/3] Added gcc 4.5.1 to buildroot
next reply other threads:[~2010-09-20 22:03 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-09-20 22:03 Martin Banky [this message]
2010-09-20 22:03 ` [Buildroot] [PATCH 1/3] dbus: bump to 1.4.0 Martin Banky
2010-09-20 22:03 ` [Buildroot] [PATCH 2/3] m4: bump to 1.4.15 Martin Banky
2010-09-20 22:03 ` [Buildroot] [PATCH 3/3] Added gcc 4.5.1 to buildroot Martin Banky
2010-11-03 19:23 ` [Buildroot] [Review] Add gcc 4.5.1 Gustavo Zacarias
2010-11-03 22:52 ` Yann E. MORIN
2010-11-04 1:25 ` Gustavo Zacarias
2010-11-04 23:05 ` Peter Korsgaard
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=1285020197-30269-1-git-send-email-Martin.Banky@gmail.com \
--to=martin.banky@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