Wilfredo Sanchez <wsanchez@[...].com>  writes:
>    The CPPFLAGS problem isn't cool, but if your description is accurate,
> it's using cpp-precomp in all cases; the regular pre-processor doesn't
> get used unless you ask for it.  This is surprising because in the
> Darwin build, we override CFLAGS, and I have to ensure that -DFOO flags
> and so on are in CPPFLAGS, not CFLAGS, else the build fails.
> 
>    Note that there are no special threading flags for the compiler needed
> in Darwin.  Adding thread support probably adds code, so that may
> explain why you get a different (broken?) perl.  I've not tried threads.

One reason I have always avoided pre-compiled headers on the few machines
which had them is that I have found a tendancy for dependancies to be
poorly handled. e.g. if I build at 9am with a non-thread build it
"precompiles" headers for non-threads. Then when at 9:15 I try a threaded
build it re-uses the "precompiled" headers and they are wrong for
what I think I am doing.

--
Nick Ing-Simmons
http://www.ni-s.u-net.com/