Am 20.09.2013 um 13:52 schrieb Adam Ciarciński <adam%NetBSD.org@localhost>: >> Well - no :) >> >> $ ls -l >> /Applications/Xcode.app/Contents/Developer/Platforms/MacOSX.platform/Developer/SDKs/MacOSX10.8.sdk/usr/include/c++/4.2.1/ >> total 168 >> […] >> -rw-r--r-- 1 root wheel 2214 19 Sep 13:58 string >> drwxr-xr-x 57 root wheel 1938 20 Jun 2012 tr1 >> -rw-r--r-- 1 root wheel 5929 19 Sep 13:58 typeinfo >> -rw-r--r-- 1 root wheel 2789 19 Sep 13:58 utility >> […] >> >> $ $ find >> /Applications/Xcode.app/Contents/Developer/Platforms/MacOSX.platform/Developer/SDKs/MacOSX10.8.sdk/usr/include >> -name tuple >> /Applications/Xcode.app/Contents/Developer/Platforms/MacOSX.platform/Developer/SDKs/MacOSX10.8.sdk/usr/include/c++/4.2.1/tr1/tuple > > Well, yes. These includes are for libc++, not libstdc++. Provide > -stdlib=libc++ and it should compile just fine. Okay - the symbolic link isn't needed, just the -stdlib=libc++ flag
Attachment:
patch-devel-googletest
Description: Binary data
Does that patch looks better for you? Cheers -- Jens Rehsack rehsack%gmail.com@localhost