From: Marcin Juszkiewicz <marcin.juszkiewicz@linaro.org>
To: Khem Raj <raj.khem@gmail.com>
Cc: "openembedded-core@lists.openembedded.org layer"
<openembedded-core@lists.openembedded.org>,
Discussion of the angstrom distribution development
<angstrom-distro-devel@linuxtogo.org>
Subject: Re: gcc-cross-initial Failure (is a meta-aarch64 screw up)
Date: Wed, 08 May 2013 08:43:16 +0200 [thread overview]
Message-ID: <5189F404.8090300@linaro.org> (raw)
In-Reply-To: <6488B785-095B-4077-96A6-0E2004900C68@gmail.com>
W dniu 08.05.2013 04:23, Khem Raj pisze:
> This seems totally wrong to me to since it overrides recipes in
> subtle ways and does not document it anywhere
>
> firstly, README is not there and as it seems its a BSP layer but it
> has much more than a BSP metadata in it. even then if it needed a new
> toolchain then it should have used different names for includes like
> meta-linaro-toolchain does.
>
> if it needed to enhance existing recipes from OE-Core or reuse them
> then it should have included them as it is and tweaked with bbappend
> or created new recipes itself for aarch64 compiler tools.
>
> I will leave this to meta-linaro devs to sort out and let it play
> better with rest of layers meanwhile I will propose to disable
> meta-aarch64 in angstrom.
I will sort it out today.
next prev parent reply other threads:[~2013-05-08 7:02 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-04-05 14:03 gcc-cross-initial Failure Jack Mitchell
2013-04-05 16:15 ` Khem Raj
2013-04-05 16:36 ` Jack Mitchell
2013-04-05 17:03 ` Khem Raj
2013-04-08 8:52 ` Jack Mitchell
2013-04-08 9:06 ` Jack Mitchell
2013-05-08 2:23 ` gcc-cross-initial Failure (is a meta-aarch64 screw up) Khem Raj
2013-05-08 5:13 ` [Angstrom-devel] " Koen Kooi
2013-05-08 6:43 ` Marcin Juszkiewicz [this message]
2013-05-08 8:22 ` Marcin Juszkiewicz
2013-05-14 21:43 ` Khem Raj
2013-05-15 2:39 ` Marcin Juszkiewicz
2013-05-08 9:55 ` Jack Mitchell
2013-04-09 14:23 ` gcc-cross-initial Failure Khem Raj
2013-04-05 19:07 ` Elvis Dowson
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=5189F404.8090300@linaro.org \
--to=marcin.juszkiewicz@linaro.org \
--cc=angstrom-distro-devel@linuxtogo.org \
--cc=openembedded-core@lists.openembedded.org \
--cc=raj.khem@gmail.com \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.