Compiling a statically-linked BIND 8.2.2-P7

[Kevin Darcy]

Why are you trying to compile a statically-linked named? For security
reasons? You can probably get much more bang for your buck by running
named as a non-root user in a chroot jail, which doesn't require a
statically-linked named. In this case, if you're running as a slave to
any zones, you _may_ wish to statically-link named-xfer, to avoid having
to provide shared libraries in the chroot jail. But that would be more a
matter of convenience rather than security, and if it's a lot of trouble
to compile named-xfer statically-linked, I'd personally be more inclined
to just copy over the shared libraries and be done with it.


- Kevin

stjames08 at my-deja.com wrote:

> Hi All,
>
> I will appreciate all assistance here. I am
> trying to compile a
> statically-linked BIND v8..2.2-P7. I reference
> cuple of www material about
> changing adjusting the CDEBUG flag
> in ./port/linux/Makefile.set from -02 -g
> to -02 -static.
>
> I did, but was never able to compile bind. It
> always come up with the
> following error. I am compiling on RedHat 6.2.
> Does BIND support static
> building???
>
> >>>gcc -D_GNU_SOURCE -02 -static   -o nslookup
> main.o getinfo.o debug.o
> send.o skip.o list.o subr.o commands.o \
>
>                 ../../lib/libbind.a -lfl
>
> /usr/bin/../lib/libc.a(res_init.o): In
> function  '__res_randomid':
> /usr/src/bs/BUILD/glibc-
> 2.1.3/resolv/res_init.c:651: multiple definition
> of
> '__res_randomid'
> ../../libbind.a(res_init.o)(.text+0x98c): first
> defined here
> collect2: ld return 1 exit status
> make[2]: *** [nslookup] Error 1
> make[2]: Leaving directory '/tmp/src/bin/nslookup'
> make[1]: *** [nslookup] Error 2
> make[1]: Leaving directory '/tmp/src/bin'
> make: ***[all] Error 2
>
> Pls help and thank you in advance.
>
> Gbenga
>
> Sent via Deja.com http://www.deja.com/
> Before you buy.