From: Bill Sargent <butters@station51.net>
To: openembedded-devel@lists.openembedded.org
Subject: Re: OpenLDAP 2.4.21. doesn't create packages
Date: Sun, 04 Jul 2010 23:31:39 +0200 [thread overview]
Message-ID: <4C30FDBB.2090900@station51.net> (raw)
In-Reply-To: <AANLkTil9SMIAhB8Z7wEJ8uzgIT0aVpbK8R6CNgKzc6mu@mail.gmail.com>
On 7/4/2010 7:58 PM, Khem Raj wrote:
>
> suppose your image is console-image then you can add something like
> below to your local.conf
>
> IMAGE_INSTALL_append_pn-console-image = " libldap-2.4-slapd libldap-2.4-bin"
>
>
>
I get this:
ERROR: [/home/bill/oe/openembedded/recipes/images/console-image.bb]
RDEPENDS/RRECOMMENDS or otherwise requires the runtime entity
'libldap-2.4-slapd' but it wasn't found in any PACKAGE or RPROVIDES
variables.
NOTE: Runtime target libldap-2.4-slapd is unbuildable, removing ...
Missing or unbuildable dependency chain was: [libldap-2.4-slapd]
ERROR: Required build target 'console-imageä has no buildable providers.
Missing or unbuilding depenency chain was: [console-image,
libldap-2.4-slapd]
I see the packages. I see this specific package. I even erased the
packages, cleared the staging, and rebuilt them and they're back again,
but it still will not incorporate them in to my image.
Is the recipe correct? SHouldnt the Openldap recipe have a PROVIDES
variable in it saying that it provides these packages?
> _______________________________________________
> Openembedded-devel mailing list
> Openembedded-devel@lists.openembedded.org
> http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/openembedded-devel
next prev parent reply other threads:[~2010-07-04 21:36 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-07-01 18:48 OpenLDAP 2.4.21. doesn't create packages Bill Sargent
2010-07-04 13:55 ` Bill Sargent
2010-07-04 17:58 ` Khem Raj
2010-07-04 21:31 ` Bill Sargent [this message]
2010-07-05 0:33 ` Khem Raj
2010-07-06 9:51 ` Bill Sargent
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=4C30FDBB.2090900@station51.net \
--to=butters@station51.net \
--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.