Of course it will solve most of the configure problems - because ./configure will run it it's true environment, and therefore, it will be able to guess the values correctly.
I already have samba 3.0.21b compiled with options allowing it to be a true domain controller (LDAP support, ACL support, etc.), and workarounds for problems like lack of NSS in uClibc (Samba needs to resolve system users, and uClibc can't fetch system users from LDAP, only from /etc/passwd + /etc/group).
I also have a kernel compiled with acl + xattr support (actually, ext2/ext3 filesystems), and OpenLDAP (2.3.19) server, too.
For those interested in Unattended installations (http://unattended.sf.net) - it also supports PXE booting via a tftp server, for unattended installations.
So, on ASUS wl-500g (or any other compatibile router to which you can connect a usb stick or a HDD), you can have a compact, but fully functional domain controller for a small office.
With two Windows clients connected, it has even about 15 megs of RAM free.
The only thing that is broken in Samba is smbclient - it's needed for cupsaddsmb for easy printer management:
[2006/02/10 11:36:06, 0] smbd/reply.c:reply_write_and_X(3048)
reply_write_and_X - large offset (40bd << 32) used and we don't support 64 bit offsets.
Every uploaded file (via smbclient, locally) is cut to 16573 bytes, which is "the first network chunk transmitted from smbclient to the server".
If anyone's interested - let me know - I don't really know if running a Samba domain controller on a OpenWRT-compatibile router is the main interest of OpenWRT developers.
And of course - if anyone can resolve the smbclient problem - is welcome.
WPKG - http://wpkg.org
Software deployment / silent installation with Samba