On 8 Apr 2008 15:43:41 -0700 Chuck Swiger <[EMAIL PROTECTED]> wrote:
[Take a look at the last part of config.log; it will probably indicate the problem. Normally, a Mac user would install the Xcode developer tools and would get a /usr/bin/cc which is a modified version of GCC 4.0.1 (currently). Also note that this version of the compiler has an optimizer bug (I believe http://gcc.gnu.org/bugzilla/show_bug.cgi?id=28045) ; you can either compile with CFLAGS='-O0', or manually specify all of the -f flags enabled by -O1 or -O2 by hand.] Many thanks for the reply. It not only solved the problem but also helped me identify the source of it. I have two hard drives - one has the Xcode installed but the other one does not have it and it was the startup drive. For some reason ./configure was not reading from the startup disk. When the locate command was entered only the compilers on the drive with Xcode were listed but not the ones on the startup drive. The configuration was also stopped by the PR28045 bug but configure prefixed with CFLAGS='-O0' bypassed the problem. Thanks once again for your expert help. Cheers _______________________________________________ Help us build a comprehensive ClamAV guide: visit http://wiki.clamav.net http://lurker.clamav.net/list/clamav-users.html
