From: Denys Dmytriyenko <denis@denix.org>
To: Khem Raj <raj.khem@gmail.com>
Cc: meta-ti@yoctoproject.org
Subject: Re: Use of MACHINE_KERNEL_PR in meta-ti recipes
Date: Sat, 03 Dec 2011 18:18:17 -0500 [thread overview]
Message-ID: <20111203231817.GC14132@denix.org> (raw)
In-Reply-To: <CAMKF1sr+w_5PtYQhi-p6epp+pAyJkHPbWwcWK1YUmwo6nqmHSg@mail.gmail.com>
On Sat, Dec 03, 2011 at 01:42:30PM -0800, Khem Raj wrote:
> On Sat, Dec 3, 2011 at 1:13 PM, Khem Raj <raj.khem@gmail.com> wrote:
> > Hi
> >
> > I am seeing this kind of error all over in meta-ti recipes
> >
> >
> > ERROR: Unable to analyse format of PR variable: ${MACHINE_KERNEL_PR}e
> > ERROR: Unable to parse
> > /home/kraj/work/angstrom/sources/meta-ti/recipes-ti/local-power-manager/ti-local-power-manager_1.24.02.09.bb
> >
> > Problem seems to be that these recipes are not getting
> > MACHINE_KERNEL_PR from anywhere but they are using it
> > and its not a standard variable in bitbake.conf either. I have
> > manually patched recipes-ti/includes/ti-staging.inc
> > to contain MACHINE_KERNEL_PR ?= "r0"
> >
> > and patched few recipes which did not include this include to have the
> > definition in them
> >
> > I don't know if this is the right way to fix it but this has got me
> > over the parsing problems
>
> btw. I am using qemuarm machine with angstrom distro on top of oe-core
> and qemuarm conf does not define MACHINE_KERNEL_PR either
Ah, that explains it. Why do you need meta-ti layer with qemuarm? Is there a
specific recipe you need from it or you are just trying all layers in default
setup?
--
Denys
next prev parent reply other threads:[~2011-12-03 23:18 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-12-03 21:13 Use of MACHINE_KERNEL_PR in meta-ti recipes Khem Raj
2011-12-03 21:42 ` Khem Raj
2011-12-03 23:18 ` Denys Dmytriyenko [this message]
2011-12-03 23:26 ` Khem Raj
2011-12-04 0:24 ` Denys Dmytriyenko
2011-12-03 23:16 ` Denys Dmytriyenko
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=20111203231817.GC14132@denix.org \
--to=denis@denix.org \
--cc=meta-ti@yoctoproject.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.