GTTF: Fix build with _GLIBCXX_DEBUG

build/common.gypi

Index: build/common.gypi
diff --git a/build/common.gypi b/build/common.gypi
index 05c474783c911cf3d4ab9a31d2b7ee1b26a1e4c3..94e2eccc80bb7f5d271416fccf24bbd5bff71cc7 100644
--- a/build/common.gypi
+++ b/build/common.gypi
@@ -1568,8 +1568,7 @@
       }],
       ['OS=="linux" and glibcxx_debug==1', {
         'defines': ['_GLIBCXX_DEBUG=1',],
-        'cflags_cc!': ['-fno-rtti'],

[Elliot Glaysher, 2012/10/24 16:39:39]

+tzik

I don't understand why this was here in the first place. Is this actually
harmless to pull out? (Can glibcxx_debug work without C++ RTTI data?)

[Paweł Hajdan Jr., 2012/10/24 16:50:17]

Good question. There was a bug in gcc
(http://gcc.gnu.org/bugzilla/show_bug.cgi?id=40160) that required usage of RTTI
with _GLIBCXX_DEBUG or chrome wouldn't compile. Now we have a more recent gcc in
Ubuntu, and can use _GLIBCXX_DEBUG without RTTI (I've tested that locally and on
trybots).

-        'cflags_cc+': ['-frtti', '-g'],
+        'cflags_cc+': ['-g'],
       }],
       ['remoting==1', {
         'defines': ['ENABLE_REMOTING=1'],