Okay, bad example. The point is, though, if you don't use all possible --without and --disable options, it's possible that configure will pick up something added to the system or changed even if you don't change anything in SFW. And then there are many configure scripts that pick up optional dependencies and don't have a --disable or --without option to stop that.
Laca On Tue, 2006-06-20 at 12:12 -0700, Mike Sullivan wrote: > Laszlo (Laca) Peter wrote: > > >> and if in > >> doubt, the effects of using the autotools-based build system are > >> assumed to be desirable. > > > > No, I don't agree with that. Autotools have some very undesirable > > effects. And SFW cannot avoid them either. Otherwise samba would > > not have been broken by updating gnutls (can't find the bugid). > > Well... > > that bugid is: > > 6435463 snv_41 with new libgnutls breaks samba > > but it's not 'configure' that automatically found libgnutls, samba's > Makefile.sfw adds it explicitly before running configure with: > > "LIBS=-lrt -lgnutls -lsocket -lnsl -lldap" > > I removed it and it built fine (though I have no idea if it works) > so I don't know why it was added, and I don't see any reason why in any > of the bugs listed in the delta (but perhaps I missed it): > > 6332751 Samba is not compiled with LDAP support and lacks the 'net' command. > 6174211 Samba 3.x package should be compiled with ldap support: > --with-ldapsam config opti > on > 6362017 RPC error when login in to Samba 3.0.11 PDC using 64-bit windows > clients (Xp or Wi > n2003) > 6344828 Solaris 10 Samba causes windows explorer into a "Not Responding" > state > > > Mike
