summaryrefslogtreecommitdiffstats
path: root/configure.ac
diff options
context:
space:
mode:
authorDavid Lamparter <equinox@diac24.net>2019-09-02 20:52:56 +0200
committerDavid Lamparter <equinox@diac24.net>2019-09-02 20:52:56 +0200
commit7bfe765ae06fcc0a5570fdd793237e5fa828f7e7 (patch)
tree6cd5fc79270bcf31e53fe14b6a1ddf41f80b1751 /configure.ac
parentMerge pull request #4910 from sworleys/Docker-Update-Libyang (diff)
downloadfrr-7bfe765ae06fcc0a5570fdd793237e5fa828f7e7.tar.xz
frr-7bfe765ae06fcc0a5570fdd793237e5fa828f7e7.zip
build: only build without libcap on request
Linux FRR builds without libcap are massively slow due to the signal-based UID/GID synchronization across threads. This disables the automatic fallback to build without libcap; it can still be requested with "--disable-capabilities" but if the option isn't given in either direction and we can't find libcap that's an error now. Signed-off-by: David Lamparter <equinox@opensourcerouting.org>
Diffstat (limited to '')
-rwxr-xr-xconfigure.ac14
1 files changed, 14 insertions, 0 deletions
diff --git a/configure.ac b/configure.ac
index 676c98438..b30b07d8e 100755
--- a/configure.ac
+++ b/configure.ac
@@ -2007,6 +2007,20 @@ if test "${enable_capabilities}" != "no"; then
-o x"${frr_ac_lcaps}" = x"yes"; then
AC_DEFINE([HAVE_CAPABILITIES], [1], [capabilities])
fi
+
+ case "$host_os" in
+ linux*)
+ if test "$frr_ac_lcaps" != "yes"; then
+ AC_MSG_ERROR([libcap and/or its headers were not found. Running FRR without libcap support built in causes a huge performance penalty.])
+ fi
+ ;;
+ esac
+else
+ case "$host_os" in
+ linux*)
+ AC_MSG_WARN([Running FRR without libcap support built in causes a huge performance penalty.])
+ ;;
+ esac
fi
AC_SUBST([LIBCAP])