From: Phil Blundell <philb@gnu.org>
To: McClintock Matthew-B29882 <B29882@freescale.com>,
Patches and discussions about the oe-core layer
<openembedded-core@lists.openembedded.org>
Subject: Re: [RFC] gcc-cross.inc: Add depedency on BUILD_ARCH
Date: Thu, 24 Nov 2011 10:54:58 +0000 [thread overview]
Message-ID: <1322132099.26081.43.camel@phil-desktop> (raw)
In-Reply-To: <CAEsOVNezsZu5dDEKZCiPd6ya8bmgyejMCmFvrgJ1br2JQQqs9w@mail.gmail.com>
On Thu, 2011-11-24 at 07:29 +0000, McClintock Matthew-B29882 wrote:
> On Thu, Nov 24, 2011 at 1:21 AM, Khem Raj <raj.khem@gmail.com> wrote:
> > hmmm I guess cross recipes are special they should not have been built
> > under target recipes. Adding build arch to package name would be ok
> > too but may be if they were built under directory of their own which
> > was something like <build>-<host>-<target> then it would also solve
> > the problem i think
>
> I agree - this is the discussion I'm trying to start. ;)
It's certainly true that the way the cross recipes are done at the
moment does suck. Really, they should be built as primarily native and
the target arch ought to just be encoded into ${PN} somehow, rather than
the current arrangement of pretending that they are target recipes.
(All the runtime bits are, or should be, packaged separately by either
libgcc or gcc-runtime so they will already get the right PACKAGE_ARCH.)
There are some old (and probably rather bit-rotten) patches to do that
in the pb/toolchain-desuck branch of oe-classic. I'm not sure whether
any of that stuff will apply to modern oe-core but the general principle
ought still to be valid.
p.
next prev parent reply other threads:[~2011-11-24 11:01 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-11-23 9:40 [RFC] gcc-cross.inc: Add depedency on BUILD_ARCH Matthew McClintock
2011-11-24 3:28 ` Khem Raj
2011-11-24 3:35 ` McClintock Matthew-B29882
2011-11-24 3:37 ` Khem Raj
2011-11-24 3:55 ` McClintock Matthew-B29882
2011-11-24 3:55 ` McClintock Matthew-B29882
2011-11-24 7:21 ` Khem Raj
2011-11-24 7:29 ` McClintock Matthew-B29882
2011-11-24 10:40 ` Richard Purdie
2011-11-24 10:54 ` Phil Blundell [this message]
2011-11-24 18:03 ` Khem Raj
2011-11-24 18:08 ` Phil Blundell
2011-11-24 18:29 ` Khem Raj
2011-11-24 23:56 ` McClintock Matthew-B29882
2011-11-25 0:17 ` Richard Purdie
2011-11-25 1:52 ` McClintock Matthew-B29882
2011-11-28 22:50 ` McClintock Matthew-B29882
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=1322132099.26081.43.camel@phil-desktop \
--to=philb@gnu.org \
--cc=B29882@freescale.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 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.