From: Gary Thomas <gary@mlbassoc.com>
To: openembedded-core@lists.openembedded.org
Subject: Re: Toolchain rework, call for testing
Date: Tue, 21 Aug 2012 06:23:46 -0600 [thread overview]
Message-ID: <50337DD2.3040704@mlbassoc.com> (raw)
In-Reply-To: <1345550404.2673.23.camel@phil-desktop>
On 2012-08-21 06:00, Phil Blundell wrote:
> On Tue, 2012-08-21 at 13:55 +0200, Marcin Juszkiewicz wrote:
>> W dniu 17.08.2012 06:47, Khem Raj pisze:
>>> Hi All
>>>
>>> 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.
>>
>> Please adapt also toolchain-layer in meta-oe for those stuck with gcc 4.6.
>
> Why is it that gcc-4.7 doesn't work for those people?
I have troubles with older versions of the Linux kernel on ARM. Anything
older than 3.2 either doesn't boot or is unstable. Kernel only, user code
built with 4.7+ seems to be fine. Since I need to use those older kernels
and I don't have the time/budget to figure out why they don't work with 4.7+,
I'm sticking with 4.6+ for now.
--
------------------------------------------------------------
Gary Thomas | Consulting for the
MLB Associates | Embedded world
------------------------------------------------------------
next prev parent reply other threads:[~2012-08-21 12:35 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
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 [this message]
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=50337DD2.3040704@mlbassoc.com \
--to=gary@mlbassoc.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