On Oct 5, 2009, at 7:17 PM, Mike Stump wrote:
> On Oct 5, 2009, at 6:35 PM, Rafael Espindola wrote:
>> Second in finding a way of not searching the paths of every
>> supported system :-)
>
> Not to repeat myself or anything like that:
>
> $ gcc -v t.cc 2>&1 | sed -n '/^ /p' | sed -n 2,3p
> /usr/include/c++/4.2.1
> /usr/include/c++/4.2.1/i686-apple-darwin10/x86_64
>
> I have a dream, one day we will just compute the actual path up
> front during the build.
Agreed; this should happen at configure time. It's likely to take some
time to figure out what we need to look for, because the set of
include paths we need to find depends on the target triple, e.g.,
$ gcc -v t.cc 2>&1 | sed -n '/^ /p' | sed -n 2,3p
/usr/include/c++/4.2.1
/usr/include/c++/4.2.1/i686-apple-darwin10/x86_64
vs
$ gcc -m32 -v t.cc 2>&1 | sed -n '/^ /p' | sed -n 2,3p
/usr/include/c++/4.2.1
/usr/include/c++/4.2.1/i686-apple-darwin10
- Doug
_______________________________________________
cfe-commits mailing list
[email protected]
http://lists.cs.uiuc.edu/mailman/listinfo/cfe-commits
