Error when building using GCC 4.9 on Chrome OS

[refi64]

make[3]: Entering directory `/usr/local/tmp/crew/universalcodegrep-0.3.3/src/future'
/bin/bash: warning: setlocale: LC_ALL: cannot change locale (en_US.utf8)
  CXX      libfuture_la-CompileTimeInfo.lo
/bin/bash: warning: setlocale: LC_ALL: cannot change locale (en_US.utf8)
../../libtool: line 1762: warning: setlocale: LC_ALL: cannot change locale (en_US.utf8)
In file included from /usr/local/include/c++/4.9.x/shared_mutex:35:0,
                 from shared_mutex.hpp:40,
                 from CompileTimeInfo.cpp:24:
/usr/local/include/c++/4.9.x/bits/c++14_warning.h:32:2: error: #error This file requires compiler and library support for the forthcoming ISO C++ 2014 standard. This support is currently experimental, and must be enabled with the -std=c++1y or -std=gnu++1y compiler options.
 #error This file requires compiler and library support for the forthcoming \
  ^
In file included from CompileTimeInfo.cpp:24:0:
shared_mutex.hpp:79:13: warning: "Faulty header: <shared_mutex>"
   STATIC_MSG_WARN("Faulty header: <shared_mutex>");
             ^
shared_mutex.hpp:90:13: warning: "Trying to build with broken <shared_mutex> header"
 STATIC_MSG_WARN("Trying to build with broken <shared_mutex> header")
             ^
CompileTimeInfo.cpp:63:13: warning: "__cpp_lib_make_unique is not defined."
 STATIC_MSG_WARN("__cpp_lib_make_unique is not defined.")
             ^
CompileTimeInfo.cpp:74:13: warning: "__cpp_lib_shared_timed_mutex not defined"
 STATIC_MSG_WARN("__cpp_lib_shared_timed_mutex not defined")
             ^
CompileTimeInfo.cpp:79:13: warning: "__cpp_lib_shared_mutex not defined"
 STATIC_MSG_WARN("__cpp_lib_shared_mutex not defined")
...

[refi64]

I believe the fix is to also test for -std=c++1y for C++14 support.

[refi64]

Actually, the problem is in autoconf (not really surprised). When it tests for C++14 support, it checks for strict compliance, even though ucg doesn't use many of the C++14 features. Maybe it should just check for what is uses?

[gvansickle]

Yeah, this is where I get super jealous of Python's:

from __future__ import blah

Post-C++11 is making some baby steps in this direction with the WG-21 feature testing recommendations, but the interim is a bumpy ride due to different levels of compiler compliance, and we still don't end up with a "from future" feature so we can easily skip at least some of the autoconf. But yeah, I definitely need to clean up some of this.

I haven't even looked at Chrome OS (and per Wikipedia, I can't unless I buy a Google tablet or some such.) Can I assume Chromium is close enough, and that I can get an ISO of it somewhere?

[refi64]

Can I assume Chromium is close enough, and that I can get an ISO of it somewhere?

That's actually what I'm using! ;)

You can download a USB disk image here and flash it to a USB. Then, boot it up and install Chromebrew, which will give you Git and GCC out-of-the-box.

Be wary, though: do NOT write the image to any kind of hard drive. Tried that twice, and both times (most recent was Friday) have ended with me breaking out partition recovery tools...