From: Saul Wold <sgw@linux.intel.com>
To: Armin Kuster <akuster@mvista.com>,
openembedded-core@lists.openembedded.org
Subject: Re: [PATCH] v2 cups: Shouldn't link against libgcrypt without using gcrypt functions
Date: Mon, 09 Jun 2014 13:43:04 -0700 [thread overview]
Message-ID: <53961C58.3020509@linux.intel.com> (raw)
In-Reply-To: <1402345571-28475-1-git-send-email-akuster@mvista.com>
On 06/09/2014 01:26 PM, Armin Kuster wrote:
> backported patch from cups.org to address the cryto dependency issue I am seeing.
>
> http://www.cups.org/str.php?L4399
>
> Signed-off-by: Armin Kuster <akuster@mvista.com>
> ---
> meta/recipes-extended/cups/cups.inc | 1 +
> .../cups/cups/cups-no-gcrypt.patch | 40 ++++++++++++++++++++++
> 2 files changed, 41 insertions(+)
> create mode 100644 meta/recipes-extended/cups/cups/cups-no-gcrypt.patch
>
> diff --git a/meta/recipes-extended/cups/cups.inc b/meta/recipes-extended/cups/cups.inc
> index fd88552..3b8027b 100644
> --- a/meta/recipes-extended/cups/cups.inc
> +++ b/meta/recipes-extended/cups/cups.inc
> @@ -8,6 +8,7 @@ SRC_URI = "http://www.cups.org/software/${PV}/${BP}-source.tar.bz2 \
> file://use_echo_only_in_init.patch \
> file://0001-don-t-try-to-run-generated-binaries.patch \
> file://cups_serverbin.patch \
> + file://cups-no-gcrypt.patch \
> "
>
> LEAD_SONAME = "libcupsdriver.so"
> diff --git a/meta/recipes-extended/cups/cups/cups-no-gcrypt.patch b/meta/recipes-extended/cups/cups/cups-no-gcrypt.patch
> new file mode 100644
> index 0000000..465d353
> --- /dev/null
> +++ b/meta/recipes-extended/cups/cups/cups-no-gcrypt.patch
Please add an Upstream-Status: Backport and included the pointer to the
bug entry.
The patch file itself needs a Signed-off-by: tag.
Thanks
Sau!
> @@ -0,0 +1,40 @@
> +Description: Don't build-depend on libgcrypt, as nothing is used from it
> +Author: Didier Raboud <odyx@debian.org>
> +Bug-Debian: https://bugs.debian.org/638416
> +Bug: http://www.cups.org/str.php?L????
> +Last-Update: 2014-04-07
> +--- a/config-scripts/cups-ssl.m4
> ++++ b/config-scripts/cups-ssl.m4
> +@@ -66,7 +66,6 @@
> + dnl Then look for GNU TLS...
> + if test $have_ssl = 0 -a "x$enable_gnutls" != "xno" -a "x$PKGCONFIG" != x; then
> + AC_PATH_PROG(LIBGNUTLSCONFIG,libgnutls-config)
> +- AC_PATH_PROG(LIBGCRYPTCONFIG,libgcrypt-config)
> + if $PKGCONFIG --exists gnutls; then
> + have_ssl=1
> + SSLLIBS=`$PKGCONFIG --libs gnutls`
> +@@ -84,14 +83,6 @@
> + if test $have_ssl = 1; then
> + CUPS_SERVERCERT="ssl/server.crt"
> + CUPS_SERVERKEY="ssl/server.key"
> +-
> +- if $PKGCONFIG --exists gcrypt; then
> +- SSLLIBS="$SSLLIBS `$PKGCONFIG --libs gcrypt`"
> +- SSLFLAGS="$SSLFLAGS `$PKGCONFIG --cflags gcrypt`"
> +- elif test "x$LIBGCRYPTCONFIG" != x; then
> +- SSLLIBS="$SSLLIBS `$LIBGCRYPTCONFIG --libs`"
> +- SSLFLAGS="$SSLFLAGS `$LIBGCRYPTCONFIG --cflags`"
> +- fi
> + fi
> + fi
> +
> +--- a/cups/http-private.h
> ++++ b/cups/http-private.h
> +@@ -80,7 +80,6 @@
> + # elif defined HAVE_GNUTLS
> + # include <gnutls/gnutls.h>
> + # include <gnutls/x509.h>
> +-# include <gcrypt.h>
> + # elif defined(HAVE_CDSASSL)
> + # include <CoreFoundation/CoreFoundation.h>
> + # include <Security/Security.h>
>
next prev parent reply other threads:[~2014-06-09 20:43 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-06-09 20:26 [PATCH] v2 cups: Shouldn't link against libgcrypt without using gcrypt functions Armin Kuster
2014-06-09 20:43 ` Saul Wold [this message]
2014-06-09 21:06 ` akuster808
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=53961C58.3020509@linux.intel.com \
--to=sgw@linux.intel.com \
--cc=akuster@mvista.com \
--cc=openembedded-core@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.