On Wed, Oct 27, 2004 at 03:31:17PM -0400, Dossy Shiobara wrote: > Perhaps before 4.0.9 is released, I should make another modification to > the AOLserver "configure" script to throw an error if CC isn't some > flavor of the GNU C compiler. But then, would that prevent folks from > building AOLserver with tools like Purify or Insure++?
Purify on Solaris works fine with gcc. Purify and AOLserver both work fine with Sun CC as well, but most people probably want to use gcc anyway, even on Solaris. So, I'd say it's ok for the AOLserver configure script to insist on gcc by default, as long as you give it an optional --allow-non-gcc switch or something like that. That will allow those who really want to use Sun CC to do so, while protecting against the common case of using it by accident. I tried Insure++ once on Solaris, is was incredibly slow on AOLserver that it was completely useless. -- Andrew Piskorski <[EMAIL PROTECTED]> http://www.piskorski.com/ -- AOLserver - http://www.aolserver.com/ To Remove yourself from this list, simply send an email to <[EMAIL PROTECTED]> with the body of "SIGNOFF AOLSERVER" in the email message. You can leave the Subject: field of your email blank.
