From: Khem Raj <raj.khem@gmail.com>
To: Diana Thayer <garbados@gmail.com>
Cc: openembedded-devel@lists.openembedded.org
Subject: Re: [meta-openwrt] Issues adding layer using readme instructions
Date: Fri, 04 Aug 2017 22:56:07 +0000 [thread overview]
Message-ID: <CAMKF1soVgTtENN2DG_ESg02coXAtjzuWn=jMt3ydhz_HdLfXbA@mail.gmail.com> (raw)
In-Reply-To: <CA++8a_CQEZBUGm_u04cA1EddT=QnMxgWqEY8ZJGiVrTnbaKmoA@mail.gmail.com>
Yes, please!
On Fri, Aug 4, 2017 at 2:37 PM Diana Thayer <garbados@gmail.com> wrote:
> That did the trick. Should I submit a patch to remove it?
>
> On Fri, Aug 4, 2017 at 2:34 PM, Khem Raj <raj.khem@gmail.com> wrote:
>
>> Ok please look for this class being inherited in this layer and delete it
>> it has been merged into image class in oe-core we should have kept an empty
>> class in or-core for backward compatibility but that's another matter
>>
>> On Fri, Aug 4, 2017 at 2:30 PM Diana Thayer <garbados@gmail.com> wrote:
>>
>>> Alright. I've added it manually. I get this error:
>>>
>>> ```
>>> ParseError at
>>> /home/garbados/openembedded-core/meta-openwrt/recipes-core/images/
>>> openwrt-base-image.bb:5: Could not inherit file
>>> classes/image_types_uboot.bbclass
>>> ```
>>>
>>> This is also the error Toaster gives me when trying to build the layer.
>>>
>>> On Fri, Aug 4, 2017 at 2:25 PM, Khem Raj <raj.khem@gmail.com> wrote:
>>>
>>>> Hi Diana
>>>>
>>>> Haven't seen anyone report this error thus far
>>>> I would suggest to add the layer manually to
>>>> Bblayer.conf and see how then you get better error messages during
>>>> parse
>>>>
>>>> On Fri, Aug 4, 2017 at 1:45 PM Diana Thayer <garbados@gmail.com> wrote:
>>>>
>>>>> Hello!
>>>>>
>>>>> I'm experiencing issues building with meta-openwrt. Following the
>>>>> instructions in the readme <https://github.com/kraj/meta-openwrt>, I
>>>>> get
>>>>> this error:
>>>>>
>>>>> ```
>>>>> $ bitbake-layers add-layer ../meta-openwrt
>>>>> NOTE: Starting bitbake server...
>>>>> Loading cache: 100% |#############################
>>>>>
>>>>> #####################################################################################|
>>>>> Time: 0:00:00
>>>>> Loaded 66 entries from dependency cache.
>>>>> ERROR: Parse failure with the specified layer added
>>>>> | ETA:
>>>>> --:--:--
>>>>> ```
>>>>>
>>>>> What failed? Why? How do I debug it? I followed the directions step by
>>>>> step, both within openembedded-core and poky.
>>>>>
>>>>> Thanks for any help you can provide.
>>>>>
>>>>> Best regards,
>>>>> Diana
>>>>> --
>>>>> _______________________________________________
>>>>> Openembedded-devel mailing list
>>>>> Openembedded-devel@lists.openembedded.org
>>>>> http://lists.openembedded.org/mailman/listinfo/openembedded-devel
>>>>>
>>>>
>>>
>
next prev parent reply other threads:[~2017-08-04 22:56 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-08-04 20:44 [meta-openwrt] Issues adding layer using readme instructions Diana Thayer
2017-08-04 21:25 ` Khem Raj
2017-08-04 21:30 ` Diana Thayer
2017-08-04 21:34 ` Khem Raj
2017-08-04 21:36 ` Diana Thayer
2017-08-04 22:56 ` Khem Raj [this message]
2017-08-04 23:12 ` Diana Thayer
2017-08-05 0:04 ` Andreas Müller
2017-08-11 20:13 ` Diana Thayer
2017-08-11 21:10 ` Khem Raj
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='CAMKF1soVgTtENN2DG_ESg02coXAtjzuWn=jMt3ydhz_HdLfXbA@mail.gmail.com' \
--to=raj.khem@gmail.com \
--cc=garbados@gmail.com \
--cc=openembedded-devel@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.