]> git.ipfire.org Git - thirdparty/kea.git/commitdiff
[#380,!191] Updated description of the error message and comment. 380-unexpected-boost-include-capture 161-move-hooks-subdirectory-under-kea-own-directory_base 161-move-hooks-subdirectory-under-kea-own-directory_merged
authorTomek Mrugalski <tomasz@isc.org>
Tue, 12 Feb 2019 13:08:22 +0000 (14:08 +0100)
committerFrancis Dupont <fdupont@isc.org>
Tue, 12 Feb 2019 18:14:24 +0000 (13:14 -0500)
m4macros/ax_boost_for_kea.m4

index 0d172cb238409cb969d8777809dc0c23ec1988f5..28d35aed65ef556fccc65d1f1cb226f48f7b3c5f 100644 (file)
@@ -79,13 +79,19 @@ AC_CHECK_HEADERS([boost/shared_ptr.hpp boost/foreach.hpp boost/interprocess/sync
 
 AC_CHECK_HEADERS(boost/asio/coroutine.hpp,,AC_MSG_RESULT(not found, using built-in header.))
 
-# Verify that the path does not capture standard headers.
+# Verify that the path does not include standard headers by mistake.
+# There are two regex.h headers: one is a standard system header (usually
+# in /usr/include) and the second one is provided by boost. If you specify the
+# path to boost in a way that specifies the actual directory, this will mess up
+# the code and we'll end up using the system header rather than the boost. For
+# example, if your boost headers are in /usr/local/include/boost, you should
+# use --with-boost-include=/usr/local/include
 AC_TRY_COMPILE([
 #include <regex.h>
 #ifdef BOOST_RE_REGEX_H
 #error "boost/regex.h"
 #endif],,,
-[AC_MSG_ERROR([${boost_include_path}/regex.h is used in place of /usr/include/regex.h: please remove the extra boost at the end of the include path.])])
+[AC_MSG_ERROR([${boost_include_path}/regex.h is used in place of /usr/include/regex.h: when specifying path to boost, please omit the /boost at the end of the include path.])])
 
 # clang can cause false positives with -Werror without -Qunused-arguments.
 # it can be triggered if used with ccache.