HELP - Bind Compile Error ( Bind 8.2.2-P5 / Slackware 7.1 / Ker 2.2.16 / Chroot )

[Mark.Andrews at nominum.com]

	Read INSTALL for a list of things that are REQUIRED to be installed
	before named will build.  Hint flex is needed.

	There is no requirement to build named in a chroot area.  You
	may want to run it in one but it should be a minimal area, just
	named-xfer and any libraries required for named-xfer to run.
	chroot filesystems should always be a minimal as possible as you
	don't always know what bugs can be exploited so the less things
	that are there, the less there is to worry about.

	Mark

> 
> Hello,
> 
> I've tried twice to compile Bind in a chroot directory with out success. I
> followed the latest how-to but there seems to be a small snag. If any one cou
> ld
> give me some advice I would appreciate it. Here are the error messages I get.
> 
> make[2]: Entering directory '/chroot/named/src/bin/addr'
> gcc -D_GNU_SOURCE  -O -g -I../../port/linux/include -I../../include  -c addr.
> c
> gcc -D_GNU_SOURCE -O -g    -o addr addr.o \
> 	../../lib/libbind.a -lfl
> /usr/i386-slackware-linux/bin/ld : cannot open -lfl: No such file or director
> y
> collect2: ld returned 1 exit status
> make[2]: *** [addr] Error 1
> make[2]: Leaving directory '/chroot/named/src/bin/addr'
> make[1]: *** [addr] Error 2
> make[1]: Leaving directory '/chroot/named/src/bin'
> make: *** [all] Error 2
> 
> 
>  - Casey McGinty
> 
> 
--
Mark Andrews, Nominum Inc.
1 Seymour St., Dundas Valley, NSW 2117, Australia
PHONE: +61 2 9871 4742                 INTERNET: Mark.Andrews at nominum.com