Passing these through CACHED_CONFIGUREVARS doesn't change the build, but makes
the recipe clearer.

Signed-off-by: Ross Burton <ross.bur...@intel.com>
---
 meta/recipes-devtools/rsync/rsync_3.1.2.bb | 9 ++++-----
 1 file changed, 4 insertions(+), 5 deletions(-)

diff --git a/meta/recipes-devtools/rsync/rsync_3.1.2.bb 
b/meta/recipes-devtools/rsync/rsync_3.1.2.bb
index 5f4733f..4b91ac7 100644
--- a/meta/recipes-devtools/rsync/rsync_3.1.2.bb
+++ b/meta/recipes-devtools/rsync/rsync_3.1.2.bb
@@ -7,15 +7,14 @@ PACKAGECONFIG ??= "acl attr"
 PACKAGECONFIG[acl] = "--enable-acl-support,--disable-acl-support,acl,"
 PACKAGECONFIG[attr] = "--enable-xattr-support,--disable-xattr-support,attr,"
 
+# By default, if crosscompiling, rsync disables a number of
+# capabilities, hardlinking symlinks and special files (i.e. devices)
+CACHED_CONFIGUREVARS += "rsync_cv_can_hardlink_special=yes 
rsync_cv_can_hardlink_symlink=yes"
+
 # rsync 3.0 uses configure.sh instead of configure, and
 # makefile checks the existence of configure.sh
 do_configure_prepend () {
        rm -f ${S}/configure ${S}/configure.sh
-
-       # By default, if crosscompiling, rsync disables a number of
-       # capabilities, hardlinking symlinks and special files (i.e. devices)
-       export rsync_cv_can_hardlink_special=yes
-       export rsync_cv_can_hardlink_symlink=yes
 }
 
 do_configure_append () {
-- 
2.8.0.rc3

-- 
_______________________________________________
Openembedded-core mailing list
Openembedded-core@lists.openembedded.org
http://lists.openembedded.org/mailman/listinfo/openembedded-core

Reply via email to