From: Bryan Hundven <bryanhundven@gmail.com>
To: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
Cc: crossgcc@sourceware.org, "Yann E. MORIN" <yann.morin.1998@free.fr>
Subject: Re: [crosstool-ng] Pre-built toolchains for testing in Buildroot
Date: Mon, 15 Jun 2015 16:12:00 -0000 [thread overview]
Message-ID: <1434384756.9341.1.camel@gmail.com> (raw)
In-Reply-To: <20150615091815.5440bbbb@free-electrons.com>
[-- Attachment #1: Type: text/plain, Size: 966 bytes --]
Thomas, all,
On Mon, 2015-06-15 at 09:18 +0200, Thomas Petazzoni wrote:
> Hello,
>
> On Sun, 14 Jun 2015 20:50:16 -0700, Bryan Hundven wrote:
>
> > I'm about to release 1.22.0, which fixes some bugs that were found after
> > 1.21.0. The last step before 1.22.0 is testing/updating the samples.
>
> Ok.
>
> > After I verify they all build correctly, I'll release 1.22.0 and
> > update/build the toolchains you linked me to.
>
> Ok, maybe we should discuss a little bit which toolchains you are going
> to produce. Especially, discussing the uClibc one. We are moving to
> uClibc-ng as the default, and we now require largefile and IPv6 support
> in all toolchains. So make sure you generate uClibc toolchains with the
> appropriate configuration.
Thanks for reminding me, uClibc-ng was another thing I wanted to add to
1.22.0. Do you have specific configurations you want me to use?
> Thanks a lot!
>
> Thomas
Cheers,
-Bryan
[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 473 bytes --]
prev parent reply other threads:[~2015-06-15 16:12 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-05-15 18:40 Thomas Petazzoni
2015-05-15 18:43 ` Bryan Hundven
2015-05-15 18:53 ` Reinoud Koornstra
2015-05-15 19:00 ` Thomas Petazzoni
2015-05-15 19:02 ` Bryan Hundven
2015-06-13 14:01 ` Thomas Petazzoni
2015-06-15 3:50 ` Bryan Hundven
2015-06-15 7:18 ` Thomas Petazzoni
2015-06-15 16:12 ` Bryan Hundven [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=1434384756.9341.1.camel@gmail.com \
--to=bryanhundven@gmail.com \
--cc=crossgcc@sourceware.org \
--cc=thomas.petazzoni@free-electrons.com \
--cc=yann.morin.1998@free.fr \
/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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).