From: Carsten Schoenert <c.schoenert@gmail.com>
To: buildroot@busybox.net
Subject: [Buildroot] no crosstool-ng 1.17.0 in 2012.11
Date: Mon, 03 Dec 2012 19:03:47 +0100 [thread overview]
Message-ID: <50BCE983.4060104@googlemail.com> (raw)
In-Reply-To: <201212031745.59827.yann.morin.1998@free.fr>
Hello Yann, Thomas,
Am 03.12.2012 17:45, schrieb Yann E. MORIN:
> crosstool-NG 1.17.0 was released too late for inclusion in buildroot 2012.11.
> I did not even try to update it.
o.k. that's the explanation. ;)
> If all goes well, I'll push the next ct-ng version in time for inclusion in
> the next BR release.
>
> Hopefully, all will go well, but there's FOSDEM at just about the time the
> next release of ct-ng is due. So, we'll see... :-/
Yes, FOSDEM in the cold city of Brussels. I'll be there.
> Alternatively, interested users ( eg. you! ;-) ) can post a patch! ;-)
I will do, right now a arm gcc 4.7.2 is builded. I will before checking
some things inside my branch. Until now everything work well, even the
compiler warnings are gone while cross compiler is building. ;)
Regards
Carsten
prev parent reply other threads:[~2012-12-03 18:03 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-12-03 16:36 [Buildroot] no crosstool-ng 1.17.0 in 2012.11 Carsten Schoenert
2012-12-03 16:43 ` Thomas Petazzoni
2012-12-03 16:45 ` Yann E. MORIN
2012-12-03 18:03 ` Carsten Schoenert [this message]
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=50BCE983.4060104@googlemail.com \
--to=c.schoenert@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