From: Markos Chandras <markos.chandras@gmail.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH] gvfs: Select and depend on libgcrypt
Date: Fri, 21 Jun 2013 11:20:11 +0100 [thread overview]
Message-ID: <1371810011-13339-1-git-send-email-markos.chandras@gmail.com> (raw)
From: Markos Chandras <markos.chandras@imgtec.com>
Fixes the following build problem when building gvfs
without having libgcrypt installed.
gvfsbackendafpbrowse.c:31:20: fatal error: gcrypt.h: No such file or directory
Signed-off-by: Markos Chandras <markos.chandras@imgtec.com>
---
package/gvfs/Config.in | 1 +
package/gvfs/gvfs.mk | 2 +-
2 files changed, 2 insertions(+), 1 deletion(-)
diff --git a/package/gvfs/Config.in b/package/gvfs/Config.in
index e0a945e..3791830 100644
--- a/package/gvfs/Config.in
+++ b/package/gvfs/Config.in
@@ -4,6 +4,7 @@ config BR2_PACKAGE_GVFS
depends on BR2_USE_WCHAR # glib2
depends on BR2_USE_MMU # dbus
depends on BR2_TOOLCHAIN_HAS_THREADS # dbus
+ select BR2_PACKAGE_LIBGCRYPT
select BR2_PACKAGE_LIBGLIB2
select BR2_PACKAGE_DBUS
select BR2_PACKAGE_SHARED_MIME_INFO
diff --git a/package/gvfs/gvfs.mk b/package/gvfs/gvfs.mk
index d99c784..0a2eece 100644
--- a/package/gvfs/gvfs.mk
+++ b/package/gvfs/gvfs.mk
@@ -10,7 +10,7 @@ GVFS_VERSION = $(GVFS_VERSION_MAJOR).$(GVFS_VERSION_MINOR)
GVFS_SOURCE = gvfs-$(GVFS_VERSION).tar.xz
GVFS_SITE = http://ftp.gnome.org/pub/GNOME/sources/gvfs/$(GVFS_VERSION_MAJOR)
GVFS_INSTALL_STAGING = YES
-GVFS_DEPENDENCIES = host-pkgconf host-libglib2 libglib2 dbus shared-mime-info
+GVFS_DEPENDENCIES = host-pkgconf host-libglib2 libgcrypt libglib2 dbus shared-mime-info
GVFS_CONF_OPT = \
--disable-gconf \
--
1.8.2.1
next reply other threads:[~2013-06-21 10:20 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-06-21 10:20 Markos Chandras [this message]
2013-06-21 10:31 ` [Buildroot] [PATCH] gvfs: Select and depend on libgcrypt Thomas Petazzoni
2013-06-21 10:33 ` Markos Chandras
2013-06-21 12:49 ` Markos Chandras
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=1371810011-13339-1-git-send-email-markos.chandras@gmail.com \
--to=markos.chandras@gmail.com \
--cc=buildroot@busybox.net \
/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