We use Vagrant and Chef to provision everything, and where possible, I like to keep my OS relatively clean- so I don't have any databases or anything installed in OS X anymore. We have a number of Vagrant and Chef scripts that will take developers from zero to fully running development environment with a simple vagrant init command followed by a few steps for hooking up whatever must be hooked up in the IDE for remote debugging where necessary. It's been fantastic, but we're mostly JVM based.
I could definitely see how clang would screw things up. I don't have experience as a C/C++ developer in OS X for anything other than personal electronics projects.
My personal and professional experience with significant development time in Java, PHP, Python, and Node has been that only Linux could do it as well, but the trade offs for daily desktop use simply aren't worth it. Being able to pump my development environments into a VM of the same flavor as the target environment has given me the best of all worlds. But I've genuinely never run into anything that just refused to work on OSX. I will say that Python and Python env are sometimes a PITA, but not any constant issues.
Various utility scripts need to be written more defensively to run correctly in OS X with its ancient shell and BSD tools.
Overall it's just not worth the hassle, particularly when you need to ramp up new developer machines in minimal time.