On Fri, 2007-03-16 at 16:06 +0100, Fabio Busatto wrote: > On Fri, Mar 16, 2007 at 04:47:11PM +0200, Timo Sirainen wrote: > > On Fri, 2007-03-16 at 14:28 +0100, Fabio Busatto wrote: > > > It seems to be a wrong check in configure, that comes out in a fatal > > > error (crypt symbol not found because the -lcrypt is omitted). > > .. > > > OS: linux > > > > What distribution? I haven't before heard of any OS/distro requiring > > -lcrypt. > > Uhm, Linux/Slackware :) > But it's not Slackware specific (I can confirm for Fedora too), you already > check for crypt in libcrypt in other configure passes (infact if you include > some other auth system, configure includes libcrypt correctly in the build > process). > > I know that crypt() is in libcrypt in all glibc based systems.
Oh, sorry. :) I didn't remember that and looking through configure.in I somehow missed the -lcrypt check and only saw -lcrypto checks. Fixed: http://dovecot.org/list/dovecot-cvs/2007-March/008211.html
signature.asc
Description: This is a digitally signed message part
