From: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH] package/crosstool-ng: update to 1.17.0
Date: Tue, 4 Dec 2012 10:12:28 +0100 [thread overview]
Message-ID: <20121204101228.2e78f9a1@skate> (raw)
In-Reply-To: <1354564065-24388-2-git-send-email-c.schoenert@t-online.de>
Dear Carsten Schoenert,
On Mon, 3 Dec 2012 20:47:45 +0100, Carsten Schoenert wrote:
> From: Carsten Schoenert <c.schoenert@t-online.de>
>
> Updating current crosstool-ng config files to 1.17.0
> crosstool-ng.config-eglibc
> crosstool-ng.config-glibc
> crosstool-ng.config-uClibc
>
> Signed-off-by: Carsten Schoenert <c.schoenert@t-online.de>
> ---
> package/crosstool-ng/crosstool-ng.mk | 2 +-
> .../crosstool-ng.config-eglibc | 73 ++++++++++++++-----
> .../crosstool-ng.config-glibc | 74 +++++++++++++++-----
> .../crosstool-ng.config-uClibc | 71 ++++++++++++++-----
> 4 files changed, 165 insertions(+), 55 deletions(-)
Thanks for doing this work. I think ct-ng now supports minimal
defconfig files. Would it make sense to use that instead of
full .config files in order to reduce the amount of churn when updating
between ct-ng versions? Yann?
Thomas
--
Thomas Petazzoni, Free Electrons
Kernel, drivers, real-time and embedded Linux
development, consulting, training and support.
http://free-electrons.com
next prev parent reply other threads:[~2012-12-04 9:12 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-12-03 19:47 [Buildroot] [PATCH 0/1] Update Crosstool-NG to 1.17.0 Carsten Schoenert
2012-12-03 19:47 ` [Buildroot] [PATCH] package/crosstool-ng: update " Carsten Schoenert
2012-12-04 9:12 ` Thomas Petazzoni [this message]
2012-12-04 18:09 ` Yann E. MORIN
2012-12-04 19:35 ` Thomas Petazzoni
2012-12-05 15:30 ` Peter Korsgaard
2012-12-09 20:02 ` Peter Korsgaard
2012-12-09 20:37 ` Yann E. MORIN
2012-12-09 21:18 ` Carsten Schoenert
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=20121204101228.2e78f9a1@skate \
--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