From: Denys Dmytriyenko <denis@denix.org>
To: Gary Thomas <gary@mlbassoc.com>
Cc: yocto@yoctoproject.org
Subject: Re: proper recipe for building for beagle xM? meta-ti?
Date: Sun, 04 Mar 2012 15:04:05 -0500 [thread overview]
Message-ID: <20120304200405.GP24667@denix.org> (raw)
In-Reply-To: <4F53C63D.1000305@mlbassoc.com>
On Sun, Mar 04, 2012 at 12:45:01PM -0700, Gary Thomas wrote:
> On 2012-03-04 12:27, Denys Dmytriyenko wrote:
> >On Sun, Mar 04, 2012 at 01:14:17PM -0500, Robert P. J. Day wrote:
> >>On Sun, 4 Mar 2012, Gary Thomas wrote:
> >>
> >>>On 2012-03-04 05:19, Robert P. J. Day wrote:
> >>>>
> >>>> not sure if you're suggesting i should now be able to build
> >>>>for, say, beagleboard with the meta-ti layer, but i cloned meta-ti
> >>>>into my yocto tree, added that layer to bblayers.conf, and tried
> >>>>to
> >>>>
> >>>>$ bitbake core-image-minimal
> >>>>
> >>>>and got what i believe gary was referring to above:
> >>>>
> >>>>$ bitbake core-image-minimal
> >>>>Pseudo is not present but is required, building this first before the main
> >>>>build
> >>>>ERROR: ParseError at
> >>>>/home/rpjday/yocto/git/meta-ti/recipes-misc/payload/bonescript.bb:5:
> >>>>Could not inherit file classes/systemd.bbclass
> >>>>ERROR: Command execution failed: Exited with 1
> >>>>
> >>>> or am i misreading what you wrote?
> >>>
> >>>Oops, that's one more workaround I forgot to mention. This file
> >>>is in OE-core, but not in poky. I made a local copy in my distro
> >>>layer, but there must be a better way to handle it.
> >>
> >> um ... AFAICT, that .bbclass file is in meta-oe, not oe-core. and
> >>since i have meta-openembedded checked out, i simply copied the whole
> >>thing into my yocto tree, then tweaked my bblayers.conf file to look
> >>like:
> >>
> >>BBLAYERS ?= " \
> >> /home/rpjday/yocto/git/meta \
> >> /home/rpjday/yocto/git/meta-yocto \
> >> /home/rpjday/yocto/git/meta-ti \
> >> /home/rpjday/yocto/git/meta-openembedded/meta-oe \
> >> "
> >
> >Either way, meta-oe is still required for meta-ti due to toolchain issues...
>
> Can you explain what the toolchain problems are and why the versions in
> oe-core don't work for meta-ti?
One of the issues:
https://lists.yoctoproject.org/pipermail/meta-ti/2012-February/000491.html
I haven't tried if either 3.0 or a pending 3.1 update for Panda (from
omapzoom/ti-ubuntu), resolve this gcc-4.6 build issue. But either way I
believe there was something else with one of our components not building with
gcc-4.6 - SGX or multimedia, don't remember exactly.
--
Denys
next prev parent reply other threads:[~2012-03-04 21:04 UTC|newest]
Thread overview: 33+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-02-28 18:51 proper recipe for building for beagle xM? meta-ti? Robert P. J. Day
2012-02-28 21:22 ` Bruce Ashfield
2012-02-28 21:55 ` Robert P. J. Day
2012-02-28 22:09 ` Koen Kooi
2012-02-28 22:28 ` Robert P. J. Day
2012-03-02 10:06 ` Koen Kooi
2012-03-02 16:45 ` Stewart, David C
2012-03-02 16:51 ` Robert P. J. Day
2012-03-02 17:15 ` Koen Kooi
2012-03-02 22:22 ` William Mills
2012-03-02 22:33 ` Robert P. J. Day
2012-03-02 22:50 ` William Mills
2012-03-02 23:18 ` Gary Thomas
2012-03-03 0:07 ` William Mills
2012-03-04 6:18 ` Denys Dmytriyenko
2012-03-04 12:19 ` Robert P. J. Day
2012-03-04 12:36 ` Gary Thomas
2012-03-04 12:54 ` Robert P. J. Day
2012-03-04 17:01 ` Koen Kooi
2012-03-04 18:14 ` Robert P. J. Day
2012-03-04 19:27 ` Denys Dmytriyenko
2012-03-04 19:43 ` Robert P. J. Day
2012-03-04 19:45 ` Gary Thomas
2012-03-04 20:01 ` Brian Hutchinson
2012-03-04 20:04 ` Denys Dmytriyenko [this message]
2012-03-04 21:18 ` Robert P. J. Day
2012-03-05 5:12 ` [yocto] " Denys Dmytriyenko
2012-03-05 11:00 ` Robert P. J. Day
2012-03-04 21:38 ` Robert P. J. Day
2012-03-05 4:26 ` Denys Dmytriyenko
2012-03-05 9:52 ` Jack Mitchell
2012-03-04 6:08 ` Denys Dmytriyenko
2012-02-28 22:12 ` Bruce Ashfield
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=20120304200405.GP24667@denix.org \
--to=denis@denix.org \
--cc=gary@mlbassoc.com \
--cc=yocto@yoctoproject.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.