OS X - -traditional-cpp vs. -no-cpp-precomp

Hi there,

I am currently trying to compile neon on OS X 10.1.1. Two observations:

1) in order to be able to compile the neon you include in the source
tar ball, I needed to modify the Makefile.in and add
"-no-cpp-precomp" to the CPPFLAGS. Of course this is not the proper
way of doing it, rather configure should add this on darwin systems.
If you don't specify that flag, compilation fails

2) APR specifies -traditional-cpp on Darwin/MacOS X. However, for
almost every use, this flag is to be considered depracted. Rather,
use -no-cpp-precomp

-traditional-cpp will (as the name implies) use the traditional CPP
from gnu, which leads to troubles in some headers files from Apple.
It is possible that you are getting away with it currently, but you
may run out of luck in the future.

OTOH, -no-cpp-precomp fixes the actual problem, namely, only the
precomp mode is turned off. The precomp mode uses a more lazy
scanning scheme, which causes it to choke on some files. It tries to
retry in non-precomp mode, but that always fails.

Cheers,

Max

-- 
-----------------------------------------------
Max Horn
Software Developer
email: <mailto:max@quendi.de>
phone: (+49) 6151-494890
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org