I wouldn't go so far as to say gcc is a hard requirement (although it is highly recommended and is the standard for AOLserver usage at AOL). What is a hard requirement is to use the same compiler for both the configure and the make. The problem is that the configure script tests default to 'cc', but the make, I believe, defaults to gcc. This causes inconsistencies that make bad things happen.
I fixed the configure script in 3.5 to have it also default to gcc and that cleared this issue, but it didn't get rolled into 4.0 - this should be done. -Elizabeth Dossy wrote on 3/1/04, 12:37 PM: > It seems that (at least on Solaris) that gcc is a build requirement for > AOLserver -- it doesn't "do the right thing" when using the SUNWspro > compiler (or maybe I'm just guessing here). > > Is gcc a hard requirement? If so, shouldn't the configure script check > $CC to make sure it's gcc (parse "$CC --version" output, etc.) and > complain and abort if it's not? > > -- Dossy > > -- > Dossy Shiobara mail: [EMAIL PROTECTED] > Panoptic Computer Network web: http://www.panoptic.com/ > "He realized the fastest way to change is to laugh at your own > folly -- then you can let go and quickly move on." (p. 70) > > > -- > 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. -- 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.
