Skip to contentSkip to conversation

cmake: Avoid accidentally including libacl.h

PATCH RESEND New Mike Crowe 1 participant 1 message May 27, 2014

lore
Share & tools
lore

Mike Crowe

author
#0 lore raw

PATCH RESEND 1/1 cmake: Avoid accidentally including libacl.h

The cmake recipe doesn't depend on libacl yet cmake will detect libacl.h and use it by default. This risks build failures if libacl.h is unstaged during the build and it also means that the build cmake will sometimes support ACLs and sometimes not.

This can be avoided by setting ENABLE_ACL=0 but until the fix for
http://cmake.org/Bug/view.php?id=14866 is released we also need to set HAVE_ACL_LIBACL_H=0.

---
 meta/recipes-devtools/cmake/cmake-native_2.8.12.2.bb | 1 +
 1 file changed, 1 insertion(+)

(Originally submitted in http://lists.openembedded.org/pipermail/openembedded-core/2014-April/091619.html )

meta/recipes-devtools/cmake/cmake-native_2.8.12.2.bb +1 -0
index 638c074..cd6b1d8 100644
@@ -14,4 +14,5 @@ SRC_URI[sha256sum] = "8c6574e9afabcb9fc66f463bb1f2f051958d86c85c37fccf067eb1a44a
 # Disable ccmake since we don't depend on ncurses
 CMAKE_EXTRACONF = "\
     -DBUILD_CursesDialog=0 \
+    -DENABLE_ACL=0 -DHAVE_ACL_LIBACL_H=0 \
 "
Signature · 1 line
2.0.0.rc2