Allow linker initialization of lazy instance

remoting/host/plugin/host_log_handler.cc

 // Copyright (c) 2011 The Chromium Authors. All rights reserved.
 // Use of this source code is governed by a BSD-style license that can be
 // found in the LICENSE file.
 
 #include "remoting/host/plugin/host_log_handler.h"
 
 #include "base/lazy_instance.h"
 #include "remoting/base/util.h"
 #include "remoting/host/plugin/host_script_object.h"
 
 namespace remoting {
 
 // Records whether or not we have a scriptable object registered for logging.
 // This is set inside the lock, but is read (in LogToUI) outside of a lock so
 // that we don't needlessly slow down the system when we log.
 static bool g_has_logging_scriptable_object = false;
 
 // The lock that protects the logging globals.
 static base::LazyInstance<base::Lock,
                           base::LeakyLazyInstanceTraits<base::Lock> >
-    g_logging_lock(base::LINKER_INITIALIZED);
+    g_logging_lock = LAZY_INSTANCE_INITIALIZER;
 
 // The scriptable object that will display the log information to the user.
 static HostNPScriptObject* g_logging_scriptable_object = NULL;
 
 // The previously registered LogMessageHandler. If not NULL, we call this after
 // we're doing processing the log message.
 static logging::LogMessageHandlerFunction g_logging_old_handler = NULL;
 
 // Set to true when we register our global log handler so that we don't try
 // to register it twice.
@@ skipping 82 matching lines @@
   }
 
   // Call the next log handler in the chain.
   if (g_logging_old_handler)
     return (g_logging_old_handler)(severity, file, line, message_start, str);
 
   return false;
 }
 
 }  // namespace remoting