From: akuster808 <akuster808@gmail.com>
To: Saul Wold <sgw@linux.intel.com>,
Armin Kuster <akuster@mvista.com>,
openembedded-core@lists.openembedded.org
Subject: Re: [PATCH] cups: Fix build failure
Date: Mon, 09 Jun 2014 13:22:45 -0700 [thread overview]
Message-ID: <53961795.9080703@gmail.com> (raw)
In-Reply-To: <5393E053.6080006@linux.intel.com>
Saul,
I found a fix from cups.org to address this. I have back ported the
patch and will submit a v2 cups patch
thanks,
- Armin
On 06/07/2014 09:02 PM, Saul Wold wrote:
> On 06/07/2014 07:30 AM, Armin Kuster wrote:
>> The follwing error was seen when no crypt dependency was included.
>>
>> In file included from cups-private.h:29:0,
>> | from attr.c:26:
>> | http-private.h:83:24: fatal error: gcrypt.h: No such file or directory
>> | # include <gcrypt.h>
>> | ^
>>
>> Add bcrypt to DEPENDS
>>
>> Signed-off-by: Armin Kuster <akuster@mvista.com>
>> ---
>> meta/recipes-extended/cups/cups.inc | 2 +-
>> 1 file changed, 1 insertion(+), 1 deletion(-)
>>
>> diff --git a/meta/recipes-extended/cups/cups.inc
>> b/meta/recipes-extended/cups/cups.inc
>> index fd88552..249eac4 100644
>> --- a/meta/recipes-extended/cups/cups.inc
>> +++ b/meta/recipes-extended/cups/cups.inc
>> @@ -1,7 +1,7 @@
>> SUMMARY = "An Internet printing system for Unix"
>> SECTION = "console/utils"
>> LICENSE = "GPLv2 & LGPLv2"
>> -DEPENDS = "gnutls libpng jpeg dbus dbus-glib zlib libusb"
>> +DEPENDS = "gnutls libpng jpeg dbus dbus-glib zlib libusb bcrypt"
>
> Do we really want to enable crypt here or make it optional? If we set
> ac_cv_search_crypt=no on the EXTRA_OECONF line, then we can remove
> this floating dependency or make it a PACKAGECONFIG setting
>
> Sau!
>
>> PROVIDES = "cups14"
>>
>> SRC_URI = "http://www.cups.org/software/${PV}/${BP}-source.tar.bz2 \
>>
prev parent reply other threads:[~2014-06-09 20:22 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-06-07 14:30 [PATCH] cups: Fix build failure Armin Kuster
2014-06-08 4:02 ` Saul Wold
2014-06-08 19:50 ` akuster@mvista
2014-06-09 20:22 ` akuster808 [this message]
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=53961795.9080703@gmail.com \
--to=akuster808@gmail.com \
--cc=akuster@mvista.com \
--cc=openembedded-core@lists.openembedded.org \
--cc=sgw@linux.intel.com \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox