From: Joshua Lock <josh@linux.intel.com>
To: poky@yoctoproject.org
Subject: Re: bitbake gs failed
Date: Fri, 29 Apr 2011 07:24:53 -0700 [thread overview]
Message-ID: <1304087099.2023.1.camel@scimitar> (raw)
In-Reply-To: <4DBA5E83.4050704@windriver.com>
On Fri, 2011-04-29 at 14:45 +0800, Kang Kai wrote:
> Hi Saul,
>
> When I import gs (ghostscript) from oe, I copy the whole directory of gs
> from oe and put it at meta/recipes-extend/gs. When run 'bitbake gs',
> the bitbake comlains:
>
> ERROR: Nothing PROVIDES 'gs'
> ERROR: Command execution failed: Traceback (most recent call last):
> File "/mnt/sda8/poky-neil/bitbake/lib/bb/command.py", line 102, in
> runAsyncCommand
> commandmethod(self.cmds_async, self, options)
> File "/mnt/sda8/poky-neil/bitbake/lib/bb/command.py", line 200, in
> buildTargets
> command.cooker.buildTargets(pkgs_to_build, task)
> File "/mnt/sda8/poky-neil/bitbake/lib/bb/cooker.py", line 827, in
> buildTargets
> taskdata.add_provider(localdata, self.status, k)
> File "/mnt/sda8/poky-neil/bitbake/lib/bb/taskdata.py", line 353, in
> add_provider
> self.add_provider_internal(cfgData, dataCache, item)
> File "/mnt/sda8/poky-neil/bitbake/lib/bb/taskdata.py", line 373, in
> add_provider_internal
> raise bb.providers.NoProvider(item)
> NoProvider: gs
>
> The bb file is in attachment.
> Would you like to help me to check it?
> Thank you!
> Kai
This means the dependency chain for gs is broken, when pulling a recipe
from somewhere else you need to ensure all of its dependencies are
present too:
DEPENDS = "jpeg zlib fontconfig cups gs-tools-native"
I don't think we have cups or gs-tools-native in oe-core?
Regards,
Joshua
--
Joshua Lock
Yocto Build System Monkey
Intel Open Source Technology Centre
next prev parent reply other threads:[~2011-04-29 14:25 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-04-29 6:45 bitbake gs failed Kang Kai
2011-04-29 14:24 ` Joshua Lock [this message]
2011-04-29 14:57 ` Mark Hatle
2011-04-29 15:11 ` Joshua Lock
2011-04-29 21:05 ` Scott Garman
2011-05-03 3:13 ` Kang Kai
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=1304087099.2023.1.camel@scimitar \
--to=josh@linux.intel.com \
--cc=poky@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.