Re: security/stunnel won't build

["Steven M. Bellovin" <smb%cs.columbia.edu@localhost>]

On Thu, 25 Sep 2008 22:49:36 -0400
"Steven M. Bellovin" <smb%cs.columbia.edu@localhost> wrote:

> This happens on i386-4.0 and amd64-current.
> 
> => Bootstrap dependency digest>=20010302: found digest-20080510
> ===> Checking for vulnerabilities in stunnel-4.24nb1
> ===> Building for stunnel-4.24nb1
> Making all in src
> /bin/sh ../libtool --tag=CC --mode=link cc  -O2 -I/usr/include -Wall
> -Wshadow -Wcast-align -Wpointer-arith -I/usr/include   -L/usr/lib
> -Wl,-R/usr/lib -Wl,-R/usr/pkg/lib -o stunnel   file.o client.o log.o
> options.o protocol.o network.o  resolver.o ssl.o ctx.o  verify.o
> sthreads.o stunnel.o  pty.o libwrap.o  -lz -lutil  -L/usr/lib -lssl
> -lcrypto cc -O2 -Wall -Wshadow -Wcast-align -Wpointer-arith
> -Wl,-R/usr/pkg/lib -o stunnel file.o client.o log.o options.o
> protocol.o network.o resolver.o ssl.o ctx.o verify.o sthreads.o
> stunnel.o pty.o libwrap.o  -lz -lutil -lssl -lcrypto
> -L/usr/pkgsrc/security/stunnel/work/.buildlink/lib libwrap.o: In
> function `auth_libwrap': libwrap.c:(.text+0x48): undefined reference
> to `request_init' libwrap.c:(.text+0x50): undefined reference to
> `sock_host' libwrap.c:(.text+0x58): undefined reference to
> `hosts_access' *** Error code 1
> 
> Stop.
> make: stopped in /usr/pkgsrc/security/stunnel/work/stunnel-4.24/src
> *** Error code 1
> 
> Stop.
> make: stopped in /usr/pkgsrc/security/stunnel/work/stunnel-4.24
> *** Error code 1
> 
> Stop.
> make: stopped in /usr/pkgsrc/security/stunnel
> *** Error code 1
> 
> Stop.
> make: stopped in /usr/pkgsrc/security/stunnel
> 

Following up my own post...

I can make the error go away by turning off the libwrap option, which
is fine for me but disables functionality that others may need.
Besides, it's enabled by default.  I can also make it go away by
patching the configure script; however, pkglint objects to doing things
like that.  Presumably, the right thing to do is to patch one of the
proto-Makefiles, but I don't understand the automake/autoconf stuff
well enough to figure it out.


                --Steve Bellovin, http://www.cs.columbia.edu/~smb