All of lore.kernel.org
 help / color / mirror / Atom feed
From: Gary Thomas <gary@mlbassoc.com>
To: yocto@yoctoproject.org
Subject: Re: build error pandaboard on master
Date: Mon, 30 Jul 2012 10:57:56 -0600	[thread overview]
Message-ID: <5016BD14.1020807@mlbassoc.com> (raw)
In-Reply-To: <5016BB44.8070202@gmail.com>

On 2012-07-30 10:50, Jim Abernathy wrote:
> On 07/30/2012 10:21 AM, Gary Thomas wrote:
>> On 2012-07-30 08:11, Jim Abernathy wrote:
>>> On 07/30/2012 09:56 AM, Gary Thomas wrote:
>>>> On 2012-07-30 07:48, Jim Abernathy wrote:
>>>>> On 07/30/2012 09:15 AM, Gary Thomas wrote:
>>>>>> On 2012-07-30 06:53, Jim Abernathy wrote:
>>>>>>> I'm on master branch trying to build core-image-minimal for the machine "pandaboard". Besides the basics, I put in a license statement for cloud9 into local.conf.
>>>>>>>
>>>>>>> My bblayer.conf is as follows:
>>>>>>>
>>>>>>> # LAYER_CONF_VERSION is increased each time build/conf/bblayers.conf
>>>>>>> # changes incompatibly
>>>>>>> LCONF_VERSION = "5"
>>>>>>>
>>>>>>> BBPATH = "${TOPDIR}"
>>>>>>> BBFILES ?= ""
>>>>>>>
>>>>>>> BBLAYERS ?= " \
>>>>>>>    /home/jim/poky/meta \
>>>>>>>    /home/jim/poky/meta-yocto \
>>>>>>>    /home/jim/meta-openembedded/meta-oe \
>>>>>>>    /home/jim/meta-ti \
>>>>>>>    "
>>>>>>>
>>>>>>> The error I'm getting is:
>>>>>>>
>>>>>>> ERROR: ParseError at /home/jim/meta-ti/recipes-misc/payload/bonescript.bb:5: Could not inherit file classes/systemd.bbclass
>>>>>>>
>>>>>>> Build Configuration:
>>>>>>> BB_VERSION        = "1.15.3"
>>>>>>> TARGET_ARCH       = "arm"
>>>>>>> TARGET_OS         = "linux-gnueabi"
>>>>>>> MACHINE           = "pandaboard"
>>>>>>> DISTRO            = "poky"
>>>>>>> DISTRO_VERSION    = "1.2+snapshot-20120730"
>>>>>>> TUNE_FEATURES     = "armv7a vfp neon cortexa9"
>>>>>>> TARGET_FPU        = "vfp-neon"
>>>>>>> meta
>>>>>>> meta-yocto        = "master:7411158e1f980cd71c432026fa2f68ab80e3541e"
>>>>>>> meta-oe           = "master:9afc488a1b97bfc5378f139ba04a7a5297b15fdb"
>>>>>>> meta-ti           = "master:9bc77dff5f84578e259f8225bfa0656d94a2a60a"
>>>>>>>
>>>>>>> ERROR: Nothing PROVIDES 'pseudo-native'
>>>>>>
>>>>>> Try adding this in local.conf:
>>>>>>   BBMASK ?= ".*/meta-ti/recipes-(misc|bsp/formfactor)/"
>>>>>>
>>>>> BBMASK by itself didn't solve my particular problem.  I'll try the other suggestions and report back.
>>>>
>>>> What other problem do you have?  That BBMASK should keep bitbake from
>>>> trying to parse the recipe mentioned above.
>>>>
>>>> Note: I use these layers with Yocto all the time with that mask...
>>>>
>>>
>>> When I just used the statement:
>>>
>>> BBMASK ?= ".*/meta-ti/recipes-(misc|bsp/formfactor)/"
>>>
>>> I got the same error as my original post.
>>
>> The only way you could get that same error is if you already have a BBMASK
>> statement somewhere and this one is being ignored because of the ?= assignment.
>>
> So I started with a clean build again. This time I only added the BBMASK statement you suggested.  I got the following error:
>
> ERROR: No recipes available for:
> /home/jim/meta-openembedded/meta-systemd/meta-gnome/recipes-gnome/gdm/gdm_2.32.2.bbappend
> /home/jim/meta-openembedded/meta-systemd/meta-efl/recipes-efl/efl/elsa_svn.bbappend
> ERROR: Command execution failed: Exited with 1
>
> I'm guessing the BBMASK needs to call out meta-openembedded/meta-systemd/meta-gnome and meta-efl?

Or don't include those layers - meta-systemd isn't needed by your yocto build.

-- 
------------------------------------------------------------
Gary Thomas                 |  Consulting for the
MLB Associates              |    Embedded world
------------------------------------------------------------


  reply	other threads:[~2012-07-30 16:57 UTC|newest]

Thread overview: 38+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-07-30 12:53 build error pandaboard on master Jim Abernathy
2012-07-30 13:00 ` Martin Jansa
2012-07-30 13:06   ` Jim Abernathy
2012-07-30 13:19     ` Martin Jansa
2012-07-30 13:21       ` Martin Jansa
2012-07-30 13:57       ` Jim Abernathy
2012-07-30 13:15 ` Gary Thomas
2012-07-30 13:48   ` Jim Abernathy
2012-07-30 13:56     ` Gary Thomas
2012-07-30 14:11       ` Jim Abernathy
2012-07-30 14:21         ` Gary Thomas
2012-07-30 14:31           ` Jim Abernathy
2012-07-30 16:50           ` Jim Abernathy
2012-07-30 16:57             ` Gary Thomas [this message]
2012-07-30 17:09               ` Jim Abernathy
2012-07-30 17:16                 ` Gary Thomas
2012-07-30 18:49                   ` Jim Abernathy
2012-07-30 19:11                     ` Gary Thomas
2012-07-31 11:25                       ` Gary Thomas
2012-07-31 11:47                         ` Jim Abernathy
2012-07-31 11:49                           ` Martin Jansa
2012-07-31 11:53                             ` Gary Thomas
2012-07-31 12:00                               ` Jim Abernathy
2012-07-31 12:14                                 ` Gary Thomas
2012-07-31 13:33                                   ` Jim Abernathy
2012-07-31 17:12                                     ` William Mills
  -- strict thread matches above, loose matches on Subject: below --
2012-08-01 18:59 maniacbug
2012-08-02 12:47 ` Jim Abernathy
2012-08-02 15:03   ` Jim Abernathy
2012-08-02 17:07 maniacbug
2012-08-02 17:21 ` Jim Abernathy
2012-08-02 20:22   ` Elvis Dowson
2012-08-03 13:19 Edward Vidal
2012-08-03 13:24 ` Gary Thomas
2012-08-03 13:59 Edward Vidal
2012-08-03 14:06 ` Gary Thomas
2012-08-03 14:37 Edward Vidal
2012-08-03 15:08 ` Edward Vidal

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=5016BD14.1020807@mlbassoc.com \
    --to=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.