From: Scott Garman <scott.a.garman@intel.com>
To: poky@yoctoproject.org
Subject: Re: bitbake gs failed
Date: Fri, 29 Apr 2011 14:05:24 -0700 [thread overview]
Message-ID: <4DBB2814.402@intel.com> (raw)
In-Reply-To: <4DBAD1E5.7050001@windriver.com>
On 04/29/2011 07:57 AM, Mark Hatle wrote:
> On 4/29/11 9:24 AM, Joshua Lock wrote:
>> 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:
>
> This is an example of an error condition that needs to be improved. The error
> nothing provides 'gs' is misleading. We have something that provides "gs", what
> we don't have are the dependencies of gs. It would be really nice to correct
> the error message to indicate that, and then skip the traceback.
This is definitely a use case I'm planning to fix for Yocto 1.1.
Scott
--
Scott Garman
Embedded Linux Engineer - Yocto Project
Intel Open Source Technology Center
next prev parent reply other threads:[~2011-04-29 21:05 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
2011-04-29 14:57 ` Mark Hatle
2011-04-29 15:11 ` Joshua Lock
2011-04-29 21:05 ` Scott Garman [this message]
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=4DBB2814.402@intel.com \
--to=scott.a.garman@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.