From: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
To: buildroot@busybox.net
Subject: [Buildroot] [pull request v2] Pull request for branch for-2011.11/ext-toolchain-updates
Date: Sun, 9 Oct 2011 19:44:23 +0200 [thread overview]
Message-ID: <cover.1318182187.git.thomas.petazzoni@free-electrons.com> (raw)
Hello,
Changes since the last posting:
* Add Acked-by and Reviewed-by tags as given by Yann E. Morin (thanks!)
* Include comments made by Yann and Arnout on patches 8/9 and 9/9.
Thomas
The following changes since commit ddb8c639c312fd9f65dbb123837c100281495d50:
libplayer: mark python bindings as broken (2011-10-08 22:39:29 +0200)
are available in the git repository at:
http://free-electrons.com/~thomas/buildroot.git for-2011.11/ext-toolchain-updates
Mike Frysinger (1):
toolchain: speed up sysroot lib copying
Thomas De Schampheleire (1):
toolchain-external: allow specifying extra external libraries
Thomas Petazzoni (7):
external toolchain: slightly optimize the copy of the toolchain sysroot
ext-toolchain: Add CodeSourcery SH uClinux 2011.03
ext-toolchain: Bump version of CodeSourcery MIPS 2011.03
ext-toolchain: Add CodeSourcery SH GNU/Linux 2011.03
ext-toolchain: Add CodeSoucery x86 GNU/Linux 2010.09
ext-toolchain: Take into account Mentor Graphics acquisition of CodeSoucery
external-toolchain: Slightly optimize toolchain extraction
toolchain/helpers.mk | 10 +-
toolchain/toolchain-external/Config.in | 157 ++++++++++++++++++++----------
toolchain/toolchain-external/ext-tool.mk | 17 +++-
3 files changed, 127 insertions(+), 57 deletions(-)
Thanks,
--
Thomas Petazzoni
next reply other threads:[~2011-10-09 17:44 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-10-09 17:44 Thomas Petazzoni [this message]
2011-10-09 17:44 ` [Buildroot] [PATCH 1/9] external toolchain: slightly optimize the copy of the toolchain sysroot Thomas Petazzoni
2011-10-09 22:00 ` Peter Korsgaard
2011-10-10 6:43 ` Thomas Petazzoni
2011-10-10 6:48 ` Thomas Petazzoni
2011-10-10 6:55 ` Peter Korsgaard
2011-10-09 17:44 ` [Buildroot] [PATCH 2/9] toolchain-external: allow specifying extra external libraries Thomas Petazzoni
2011-10-09 17:44 ` [Buildroot] [PATCH 3/9] ext-toolchain: Add CodeSourcery SH uClinux 2011.03 Thomas Petazzoni
2011-10-09 17:44 ` [Buildroot] [PATCH 4/9] ext-toolchain: Bump version of CodeSourcery MIPS 2011.03 Thomas Petazzoni
2011-10-09 17:44 ` [Buildroot] [PATCH 5/9] ext-toolchain: Add CodeSourcery SH GNU/Linux 2011.03 Thomas Petazzoni
2011-10-09 17:44 ` [Buildroot] [PATCH 6/9] ext-toolchain: Add CodeSoucery x86 GNU/Linux 2010.09 Thomas Petazzoni
2011-10-09 17:44 ` [Buildroot] [PATCH 7/9] ext-toolchain: Take into account Mentor Graphics acquisition of CodeSoucery Thomas Petazzoni
2011-10-09 17:44 ` [Buildroot] [PATCH 8/9] external-toolchain: Slightly optimize toolchain extraction Thomas Petazzoni
2011-10-09 21:42 ` Yann E. MORIN
2011-10-10 7:57 ` Peter Korsgaard
2011-10-09 17:44 ` [Buildroot] [PATCH 9/9] toolchain: speed up sysroot lib copying Thomas Petazzoni
2011-10-09 21:46 ` Yann E. MORIN
2011-10-10 2:25 ` Mike Frysinger
2011-10-10 6:44 ` Thomas Petazzoni
2011-10-10 15:12 ` Mike Frysinger
2011-10-10 15:19 ` Thomas Petazzoni
2011-10-10 15:22 ` Mike Frysinger
2011-10-10 15:29 ` Thomas Petazzoni
2011-10-10 15:46 ` Mike Frysinger
2011-10-10 7:57 ` 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=cover.1318182187.git.thomas.petazzoni@free-electrons.com \
--to=thomas.petazzoni@free-electrons.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