On 2 Mar 2012, at 12:08, Chandler Carruth wrote: > Still, even if you are unable to use the GCC detection logic, you can still > setup the header search from the driver. There are plenty of non-GCC header > search options set up from the driver with explicit paths not fundamentally > different from how you're setting up the paths here. The difference is it > keeps the toolchain-specific logic.
Perhaps you could point me in the correct direction. I was only able to find one example of a header being included in a system toolchain anywhere where only -stdlib=libc++ was defined. This was for Darwin, and it was in exactly the same place that I modified. David _______________________________________________ cfe-commits mailing list [email protected] http://lists.cs.uiuc.edu/mailman/listinfo/cfe-commits
