From: Bob Cochran <yocto@mindchasers.com>
To: Luo Zhenhua-B19537 <B19537@freescale.com>
Cc: "meta-freescale@yoctoproject.org" <meta-freescale@yoctoproject.org>
Subject: Re: QorIQ SDKV1.3: bitbake chokes on parsing package.bbclass...
Date: Mon, 24 Dec 2012 10:28:22 -0500 [thread overview]
Message-ID: <50D87496.6010107@mindchasers.com> (raw)
In-Reply-To: <CA452391058F6D4E9715FB2C29D9312A01399E58@039-SN2MPN1-021.039d.mgd.msft.net>
On 12/24/2012 01:58 AM, Luo Zhenhua-B19537 wrote:
> Bob,
>
> Have you met the parse error when building default rootfs images? I guess this issue only happens on your customized recipe, right?
Hi Zhenhua,
I only tried two things after installing sdkv1.3: bitbake
core-image-minimal (no build problems) and bitbake <my-custom-image>
(had the parse problem with package.bbclass)
I'm wondering why you bother bundling poky with your SDK. Why not just
release the meta-fsl-* layers and point the user to which poky branch &
tag you tested against? If this was the case, then I would just need to
fast forward the poky branch to pick up patches.
I continue to be confused why FSL maintains two repos for meta-fsl-ppc.
The one on git.freescale.com is obviously ahead, but the one on yocto
does have some recent, selective patches.
As a SW developer for QorIQ, it would be my preference that the yocto
(BSP) repositories for meta-fsl-* were just a mirror of
git.freescale.com and Freescale wouldn't bother to maintain a separate
poky repo (just patch the one on yocto / OE and reference it).
Wouldn't this be easier for everyone?
Any clarification would be greatly appreciated.
This SDK has been verified on typical Linux distros(Ubuntu, Redhat,
Fedora, CentOS, openSUSE) with Python 2.6/2.7.
>
> BTW, what's the Linux distro and python version on your machine?
FYI: I use Ubuntu 12.04.1, and Python 2.7.3
Thanks,
Bob
>
>
> Best Regards,
>
> Zhenhua
>
>> -----Original Message-----
>> From: meta-freescale-bounces@yoctoproject.org [mailto:meta-freescale-
>> bounces@yoctoproject.org] On Behalf Of Bob Cochran
>> Sent: Monday, December 24, 2012 2:19 PM
>> To: meta-freescale@yoctoproject.org
>> Subject: [meta-freescale] QorIQ SDKV1.3: bitbake chokes on parsing
>> package.bbclass...
>>
>> Hello,
>>
>> Just started working with yocto sdkv1.3 tonight, which I downloaded from
>> FSL web site. I'm working with p1010rdb, and I tried to bake some custom
>> recipes.
>>
>> parse_python() inside codeparser.py errors (IndentationError: unexpected
>> indent) when it tries to parse python function populate_packages inside
>> package.bbclass.
>>
>> It looks like it is choking on the tabs inside populate_packages().
>>
>> FYI: package.bbclass was patched on yocto's poky master branch on 7/11 to
>> convert tabs into 4 spaces (commit:
>> bfd279de3275abbfaf3e630383ec244131e0375f).
>>
>> Looking at FSL's poky.git on git.freescale.com, it appears that this
>> patch wasn't picked up.
>>
>> Bob
>>
>>
>> _______________________________________________
>> meta-freescale mailing list
>> meta-freescale@yoctoproject.org
>> https://lists.yoctoproject.org/listinfo/meta-freescale
>
>
>
next prev parent reply other threads:[~2012-12-24 15:28 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-12-24 6:19 QorIQ SDKV1.3: bitbake chokes on parsing package.bbclass Bob Cochran
2012-12-24 6:58 ` Luo Zhenhua-B19537
2012-12-24 15:28 ` Bob Cochran [this message]
2012-12-25 2:38 ` Luo Zhenhua-B19537
2013-01-02 19:17 ` McClintock Matthew-B29882
2013-01-05 14:02 ` Bob Cochran
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=50D87496.6010107@mindchasers.com \
--to=yocto@mindchasers.com \
--cc=B19537@freescale.com \
--cc=meta-freescale@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.