Re: DLZ in openBSDs BIND Version

[email protected] Tue, 04 Nov 2008 13:50:49 +0100
Newsgroups gmane.network.dns.bind9.dlz
Message-ID <[email protected]>
Hello again,

I got DLZ support run in OpenBSDs BIND version,
but there are some things to do for the maintainer.

First a config.dlz.in or better all contrib/dlz files from a stanard  
BIND version are
needed.

Even if a config.dlz.in exists it won't work. I had to rebuild the  
configure script with
autoconf. (It seems configure.in was correctly patched but without  
running autoconf after
it.)

I also had to remove the lcrypt compiler switches. They aren't needed  
on OpenBSD.

At least I had to search lcg.h in OpenBSD 4.2 (it was removed in 4.3).
The lcg.h functionallity should be replaced by the new 4.3 by someone.

After this steps I was able to recompile BIND with DLZ support.

I tested it and it works normally so far but I classify the above  
steps as bugs.

Quoting [email protected]:

> Hello,
>
> I'm going to recompile openBSDs BIND Version to enable DLZ support.
>
> I know DLZ is built in and in general should be enabled by using   
> compiler flag
> --with-dlz-xxx or refering to the changelog by using --with-dlz-xxx=yes.
>
> Both doesn't work what means I get a "checking for DLZ...no" output at
> configure. In configure and configure.in a config.dlz.in file is
> called but I don't know anything about the file or the format. It's
> not documented in the net or in local docs. How can I find out more
> about the file, are there docs?
>
> Internal the first problem is USE_DLZ is set to an empty value (I got
> this from the config.log). Referring to the configure script
> config.dlz.in is used to enable USE_DLZ, but how?
>
> I could set USE_DLZ myself to a non empty value but that shouldn't be
> the standard way.
>
> # src/usr.sbin/bind/configure
> #
> # Configure any DLZ drivers.
> #
> # If config.dlz.in selects one or more DLZ drivers, it will set
> # USE_DLZ to a non-empty value, which will be our clue to
> # enable the DLZ core functions.
> #
> # This section has to come after the libtool stuff because it needs to
> # know how to name the driver object files.
> #
>
> USE_DLZ=""
> DLZ_DRIVER_INCLUDES=""
> DLZ_DRIVER_LIBS=""
> DLZ_DRIVER_SRCS=""
> DLZ_DRIVER_OBJS=""
>
>
>
> { echo "$as_me:$LINENO: checking for DLZ" >&5
> echo $ECHO_N "checking for DLZ... $ECHO_C" >&6; }
>
> if test -n "$USE_DLZ"
> then
>          { echo "$as_me:$LINENO: result: yes" >&5
> echo "${ECHO_T}yes" >&6; }
>          USE_DLZ="-DDLZ $USE_DLZ"
>          DLZ_DRIVER_RULES=contrib/dlz/drivers/rules
>          ac_config_files="$ac_config_files $DLZ_DRIVER_RULES"
>
> else
>          { echo "$as_me:$LINENO: result: no" >&5
> echo "${ECHO_T}no" >&6; }
>          DLZ_DRIVER_RULES=/dev/null
> fi
>
> #########################
>
> # src/usr.sbin/bind/configure.in
> #
> # Configure any DLZ drivers.
> #
> # If config.dlz.in selects one or more DLZ drivers, it will set
> # USE_DLZ to a non-empty value, which will be our clue to
> # enable the DLZ core functions.
> #
> # This section has to come after the libtool stuff because it needs to
> # know how to name the driver object files.
> #
>
> USE_DLZ=""
> DLZ_DRIVER_INCLUDES=""
> DLZ_DRIVER_LIBS=""
> DLZ_DRIVER_SRCS=""
> DLZ_DRIVER_OBJS=""
>
> sinclude(contrib/dlz/config.dlz.in)
>
> AC_MSG_CHECKING(for DLZ)
>
> if test -n "$USE_DLZ"
> then
>          AC_MSG_RESULT(yes)
>          USE_DLZ="-DDLZ $USE_DLZ"
>          DLZ_DRIVER_RULES=contrib/dlz/drivers/rules
>          AC_CONFIG_FILES([$DLZ_DRIVER_RULES])
> else
>          AC_MSG_RESULT(no)
>          DLZ_DRIVER_RULES=/dev/null
> fi
>
> AC_SUBST(USE_DLZ)
> AC_SUBST(DLZ_DRIVER_INCLUDES)
> AC_SUBST(DLZ_DRIVER_LIBS)
> AC_SUBST(DLZ_DRIVER_SRCS)
> AC_SUBST(DLZ_DRIVER_OBJS)
> AC_SUBST_FILE(DLZ_DRIVER_RULES)
>
> #########################
>
> # more config.log | grep -A 1 -B 1  DLZ
> configure:29638: result: yes
> configure:29724: checking for DLZ
> configure:29736: result: no
> --
> DEFS='-DHAVE_CONFIG_H'
> DLZ_DRIVER_INCLUDES=''
> DLZ_DRIVER_LIBS=''
> DLZ_DRIVER_OBJS=''
> DLZ_DRIVER_SRCS=''
> DNS_CRYPTO_LIBS=' -lcrypto '
> --
> STRIP=''
> USE_DLZ=''
> USE_GSSAPI=''
> --
> BIND9_MAKE_RULES='/root/bind/bind/make/rules'
> DLZ_DRIVER_RULES='/dev/null'
> LIBBIND9_API='./lib/bind9/api'
>
> Thanks !
>
>
> -------------------------------------------------------------------------
> This SF.Net email is sponsored by the Moblin Your Move Developer's challenge
> Build the coolest Linux based applications with Moblin SDK & win great prizes
> Grand prize is a trip for two to an Open Source event anywhere in the world
> http://moblin-contest.org/redirect.php?banner_id=100&url=/
> _______________________________________________
> Bind-dlz-testers mailing list
> [email protected]
> https://lists.sourceforge.net/lists/listinfo/bind-dlz-testers
>




-------------------------------------------------------------------------
This SF.Net email is sponsored by the Moblin Your Move Developer's challenge
Build the coolest Linux based applications with Moblin SDK & win great prizes
Grand prize is a trip for two to an Open Source event anywhere in the world
http://moblin-contest.org/redirect.php?banner_id=100&url=/