From: Martin Jansa <martin.jansa@gmail.com>
To: openembedded-devel@lists.openembedded.org
Subject: Re: meta-oe breakage since oe-core removed gcc-4.6
Date: Thu, 28 Jun 2012 19:40:41 +0200 [thread overview]
Message-ID: <20120628174041.GB24537@localhost.jama.net> (raw)
In-Reply-To: <CADZ6=avV5=3g9CkMMDc9cKLUpw_-Bk_q7fb5MceJmtR0gH6YvQ@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 1169 bytes --]
On Thu, Jun 28, 2012 at 03:06:29PM +0200, Thilo Fromm wrote:
> Hi meta-openembedded maintainers,
>
> meta-openembedded buid is currently broken since oe-core removed
> recipes for gcc-4.6, and meta-oe has .bbappends for several gcc 4.6
> recipes now unavailable in oe-core.
>
> No matter what's meta-oe's plan to handle this (i.e. move gcc-4.6 into
> meta-oe/toolchain-layer completely vs. remove gcc 4.6 .bbappends
> altogether), the current state - having the .bbappends in meta-oe and
> no original recipes anymore in oe-core - breaks the build. Is this
> going to change anytime soon? In either way?
khem's patches which removed it from oe-core said:
gcc-4.6: Retire into toochain-layer
so I guess he has some patches adding whole recipes to toolchain-layer
(I had a feeling that I've even seen them somewhere, but cannot find
them later).
So for now I've removed all .bbappends as I'm using gcc-4.7.1 anyway.
you can cherry-pick this one for now:
http://git.openembedded.org/meta-openembedded-contrib/commit/?h=shr&id=a31c882c8e336b9ffaa00c074fc24da50deb83a7
Cheers,
--
Martin 'JaMa' Jansa jabber: Martin.Jansa@gmail.com
[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 205 bytes --]
next prev parent reply other threads:[~2012-06-28 17:51 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-06-28 13:06 meta-oe breakage since oe-core removed gcc-4.6 Thilo Fromm
2012-06-28 17:40 ` Martin Jansa [this message]
2012-06-29 0:24 ` Khem Raj
2012-06-29 7:14 ` Thilo Fromm
2012-07-09 16:04 ` Marcin Juszkiewicz
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=20120628174041.GB24537@localhost.jama.net \
--to=martin.jansa@gmail.com \
--cc=openembedded-devel@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