From: Christopher Larson <kergoth@gmail.com>
To: Patches and discussions about the oe-core layer
<openembedded-core@lists.openembedded.org>
Subject: Re: Toolchain rework, call for testing
Date: Fri, 17 Aug 2012 09:21:21 -0700 [thread overview]
Message-ID: <25305C5D6E5A4932BA15741803712080@gmail.com> (raw)
In-Reply-To: <CAMKF1srjqDsesRcWP7oGzouPj9aOt_Ln0aOWE9cEQwpUQ7Unuw@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 934 bytes --]
On Thursday, August 16, 2012 at 9:47 PM, Khem Raj wrote:
> Recently glibc build has been simplified upstream. It has dropped the
> dependency on libgcc_s and libgcc_eh for building glibc itself.
> This means that we can simplify our toolchain bootstrap a bit by
> dropping 1 of the 3 cross gcc build stages. We do not need
> gcc-cross-intermediate
> anymore. This should bring some build time reduction and simplify the
> bootstrap. I have a series of patches which I have tested
> by building core-image-minimal and meta-toolchain for all supported
> qemu architectures and also uclibc/eglibc both
> but it needs a lot more testing therefore I am calling out wider
> audience for help in testing it out.
>
> The branch is
>
> http://git.openembedded.org/openembedded-core-contrib/log/?h=kraj/toolchain-rework
Successfully built core-image-base for p2020rdb with meta-fsl-ppc, so far.
--
Christopher Larson
[-- Attachment #2: Type: text/html, Size: 7806 bytes --]
next prev parent reply other threads:[~2012-08-17 16:33 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-08-17 4:47 Toolchain rework, call for testing Khem Raj
2012-08-17 16:21 ` Christopher Larson [this message]
2012-08-21 3:35 ` Saul Wold
2012-08-21 4:35 ` Khem Raj
2012-08-21 11:55 ` Marcin Juszkiewicz
2012-08-21 12:00 ` Phil Blundell
2012-08-21 12:07 ` Martin Jansa
2012-08-21 12:23 ` Gary Thomas
2012-08-21 17:13 ` Khem Raj
2012-08-21 18:37 ` Khem Raj
2012-08-21 12:18 ` [yocto] " Martin Jansa
2012-08-21 17:15 ` Khem Raj
2012-08-21 18:28 ` Martin Jansa
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=25305C5D6E5A4932BA15741803712080@gmail.com \
--to=kergoth@gmail.com \
--cc=openembedded-core@lists.openembedded.org \
/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