Since the new 3.2.x releases --with-static-libs=libtalloc,libtdb,libnetapi,libaddns,libsmbclient,libsmbsharemodes,libwbclient can't link libwbclient statically to the binaries. $ ldd ./bin/net libcrypt.so.1 => /lib/libcrypt.so.1 (0x4001e000) libresolv.so.2 => /lib/libresolv.so.2 (0x4004c000) libnsl.so.1 => /lib/libnsl.so.1 (0x4005f000) libdl.so.2 => /lib/libdl.so.2 (0x40074000) libreadline.so.5 => /pkg/lib/libreadline.so.5 (0x40078000) libncurses.so.5 => /pkg/lib/libncurses.so.5 (0x400a5000) libwbclient.so.0 => /pkg/lib/libwbclient.so.0 (0x400e7000) libc.so.6 => /lib/libc.so.6 (0x400f0000) /lib/ld-linux.so.2 (0x40000000) libtalloc.so.1 => /pkg/lib/libtalloc.so.1 (0x40207000) Modifiying the source/Makefile, and replacing libwbclient.so with libwbclient.a solved the problem till 3.2.1, but since 3.2.2 this trick does not works any more.
The entire point of libwbclient is to provide a shared lib interface between smbd (and other applications) and winbindd. Allowing a static link just recouples the two.