I'm compiling courier-imap on a Solaris 2.6 SUN Ultra-250. After
getting db, openssl, openldap and a compatible version of gcc (the
assembler wasn't working quite right, so I tiptoed from 2.95.2 to
2.95.3) installed for courier, I started up configure, but during the
execution it said that it wasn't happy with our wait().
Following the directives on the FAQ page (keeping in mind this
server has had the patch mentioned), I gave it the --with-waitfunc=wait3
flag and everything continued smoothly. The make went off without a
hitch, but I'd like to know if anyone knows of any bugs generated in the
built binary stemming from this waitlib issue.
Trying to interpret the mention of the bug fix, I'd say that the
error would come up if the program were to run for 248 days in a wait
cycle, but logic says that couldn't be detected by a configure script,
so I'm a bit worried.
Does anyone know if this situation will cause a problem once this
goes into production?
Scott Pestana
_______________________________________________
courier-users mailing list
[EMAIL PROTECTED]
Unsubscribe: https://lists.sourceforge.net/lists/listinfo/courier-users
