On Jul 18, 2012, at 3:22 AM, Jim Reid wrote:

> I think too you've compiled in lots of cruft you don't need or understand. 
> Your posting suggests you don't care about having a postfix that uses SASL or 
> MySQL or PCRE and are just blindly following the recipe on this web page 
> instead of reading the Postfix documentation. [Someone who did know about 
> these things would probably have worked out what was behind the compiler 
> warnings that prompted your post.] Unless Apple have really screwed up Lion, 
> compiling postfix should "just work", just as it would on any decent BSD Unix 
> flavour. No secret sauce should be needed.

Hey Jim.  You apparently read more into my posting than what I wrote.  I do 
understand and require the options specified for my configuration here, and was 
not blindly following someone else's setup, and I've also read the Postfix 
documentation.  My problem is with interpreting the errors and warnings 
produced by make, which is not covered in the postfix documentation...


>> [src/util]
>> cc -DUSE_TLS -DUSE_SASL_AUTH -DDEF_SERVER_SASL_TYPE=\"dovecot\" 
>> -DDEF_COMMAND_DIR=\"/usr/local/sbin\" 
>> -DDEF_CONFIG_DIR=\"/usr/local/etc/postfix\" 
>> -DDEF_DAEMON_DIR=\"/usr/local/libexec/postfix\" -DHAS_PCRE 
>> -I/usr/local/include -DHAS_SSL -I/usr/include/openssl -DHAS_MYSQL 
>> -I/usr/local/mysql/include -DBIND_8_COMPAT -DNO_NETINFO 
>> -DRESOLVE_H_NEEDS_ARPA_NAMESER_COMPAT_H -DNO_KQUEUE -g -O -I. -DMACOSX -c 
>> concatenate.c
>> concatenate.c:2:1: warning: '/*' within block comment [-Wcomment]
> 
> You can ignore this. It's a warning from the compiler, not an error. The C 
> compiler is whining about nested comments - "'/*' within block comment". This 
> is not a fatal error at all and the software is being compiled just fine. 
> These nested comments are used throughout the postfix source code.
> 
> Apple might have made the MacOSX Lion compiler scream about warnings related 
> to comments in the source code, but this is unlikely. The -Wcomment thing is 
> the command-line option which makes the compiler scream about nested comments 
> without affecting the actual compilation. However this command-line option 
> (read the man page for gcc) isn't shown above. Check your postfix Makefiles. 
> They all should have a line defining what warnings the compiler should and 
> shouldn't whine about. On mine, this is:
>       WARN    = -Wall -Wno-comment -Wformat -Wimplicit -Wmissing-prototypes \
>               -Wparentheses -Wstrict-prototypes -Wswitch -Wuninitialized \
>                       -Wunused -Wno-missing-braces
> 
> Note the -Wno-comment entry which expressly tells the compiler to shut up 
> about nested comments. It looks likely you've not got this, most probably 
> because you didn't follow the postfix documentation.

Thanks for clarifying that these are just warnings and can be safely ignored.  
I have not edited the makefiles created in any way, and I checked a number of 
the makefiles produced and they all match the WARN statement above, so I'm not 
sure why the warnings about the nested comments were generated.  I have to 
assume that this is something new in Lion and will explore that offline.


Jim


Reply via email to