Re: Disabling bind features from top-level configure

I ended up adding --enable/disable-backtrace support to the top-level configure.ac but I wonder if we don't need a way to pass-through arbitrary options to the bind configure.




> On Mar 14, 2022, at 11:25 PM, Philip Prindeville <[email protected]> wrote:
> 
> Hi,
> 
> Does anyone know how to build isc-dhcp such that we can pass in options to bind//bind-x.y.z/configure?
> 
> For instance, what if I want to add --disable-backtrace to BINDCONFIG?
> 
> I'm running into issues with MUSL on ARM 32-bit platforms not having Unwind_GetIP()...
> 
> Thanks
>

-- 
ISC funds the development of this software with paid support subscriptions. Contact us at https://www.isc.org/contact/ for more information.

dhcp-users mailing list
[email protected]
https://lists.isc.org/mailman/listinfo/dhcp-users

--- a/configure.ac
+++ b/configure.ac
@@ -660,6 +660,13 @@ else
 	BINDCONFIG="$BINDCONFIG --with-randomdev=$use_randomdev"
 fi
 
+AC_ARG_ENABLE(backtrace,
+	AS_HELP_STRING([--enable-backtrace], [use libunwind backtracing (default is yes)]),
+	want_backtrace="$enableval", want_backtrace="yes")
+if test "$want_backtrace" = "no"; then
+	BINDCONFIG="$BINDCONFIG --disable-backtrace"
+fi
+
 BINDIOMUX="--disable-kqueue --disable-epoll --disable-devpoll"
 # check kqueue/epoll/devpoll alternative to select
 AC_ARG_ENABLE(kqueue,