Bug 73106 - gtest-port.h:499:13: fatal error: 'tr1/tuple' file not found
Summary: gtest-port.h:499:13: fatal error: 'tr1/tuple' file not found
Status: RESOLVED FIXED
Alias: None
Product: Mesa
Classification: Unclassified
Component: Other (show other bugs)
Version: git
Hardware: x86-64 (AMD64) Mac OS X (All)
: medium normal
Assignee: mesa-dev
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2013-12-28 23:27 UTC by Vinson Lee
Modified: 2014-04-14 07:21 UTC (History)
0 users

See Also:
i915 platform:
i915 features:

Attachments

Description Vinson Lee 2013-12-28 23:27:23 UTC 
mesa: e2d53fac1c5b18f5c9e95d39d4e2be4703b0b363 (master)

gtest-1.6.0 build fails on Mac OS X 10.9 Mavericks.

$ make check
[...]  CXX      src/gtest-all.lo
In file included from src/gtest-all.cc:39:
In file included from ../../src/gtest/include/gtest/gtest.h:57:
In file included from ../../src/gtest/include/gtest/internal/gtest-internal.h:40:
../../src/gtest/include/gtest/internal/gtest-port.h:499:13: fatal error: 'tr1/tuple' file not found
#   include <tr1/tuple>  // NOLINT
            ^

$ g++ --version
Configured with: --prefix=/Applications/Xcode.app/Contents/Developer/usr --with-gxx-include-dir=/usr/include/c++/4.2.1
Apple LLVM version 5.0 (clang-500.2.79) (based on LLVM 3.3svn)
Target: x86_64-apple-darwin13.0.0
Thread model: posix

$ sw_vers
ProductName:	Mac OS X
ProductVersion:	10.9.1
BuildVersion:	13B42
Comment 1 Vinson Lee 2014-04-14 07:21:07 UTC 
commit 36fb36aa36d8933fef04c1bdaed3ccc9b5108908
Author: Vinson Lee <vlee@freedesktop.org>
Date:   Wed Feb 26 22:54:24 2014 -0800

    gtest: Update to 1.7.0.
    
    This patch fixes gtest build errors on Mac OS X 10.9.
    
    Bugzilla: https://bugs.freedesktop.org/show_bug.cgi?id=73106
    Signed-off-by: Vinson Lee <vlee@freedesktop.org>
    Tested-by: Ian Romanick <ian.d.romanick@intel.com>
    Acked-by: Ian Romanick <ian.d.romanick@intel.com>

Use of freedesktop.org services, including Bugzilla, is subject to our Code of Conduct. How we collect and use information is described in our Privacy Policy.