Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Jeremy Rosen <jeremy.rosen@openwide.fr>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH] toolchain/crostool-NG: mark as deprecated
Date: Tue, 7 May 2013 10:20:36 +0200 (CEST)	[thread overview]
Message-ID: <2101586089.2239357.1367914836004.JavaMail.root@openwide.fr> (raw)
In-Reply-To: <20130507100237.3888a716@skate>

> 
> I don't have real comments about the proposal to deprecate the
> Crosstool-NG support, but I'd like to take this opportunity to unveil
> my plans about the internal toolchain support (I hate unveiling plans
> before the code is ready, but it seems like a good idea in this
> particular case) :
> 
>  (1) I am currently converting the existing internal toolchain logic
>  to
>      use the package infrastructure. I've already done it for
>      'gdb' (merged for 2013.05), I have patches that seem to work for
>      elf2flt and linux-headers, and I've started working on
>      converting
>      gcc (which is the most complicated piece of the puzzle).
> 
>  (2) Once this conversion is done, I intend to work on adding
>  (e)glibc
>      support to the internal toolchain backend, so that regardless of
>      what happens with the Crosstool-NG backend, Buildroot will
>      continue to have the possibility to build a (e)glibc toolchain.
> 
> (1) and (2) represent a significant amount of work, so don't expect
> those things to be ready overnight.
> 

ok, thanks for the news, I was a bit worried that we had would have no 
support for self-compiled glibc toolchain at some point (that was the 
main reason I was using ct-ng)

  reply	other threads:[~2013-05-07  8:20 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-05-06 22:47 [Buildroot] [PATCH] toolchain/crostool-NG: mark as deprecated Yann E. MORIN
2013-05-07  8:02 ` Thomas Petazzoni
2013-05-07  8:20   ` Jeremy Rosen [this message]
2013-05-07 21:02 ` Peter Korsgaard
  -- strict thread matches above, loose matches on Subject: below --
2013-06-14 20:24 soochon radee
2013-06-14 22:55 ` Yann E. MORIN
2013-06-15  8:23   ` 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=2101586089.2239357.1367914836004.JavaMail.root@openwide.fr \
    --to=jeremy.rosen@openwide.fr \
    --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