chrome/browser should build on the x86_64 architecture

chrome/browser/chrome_browser_application_mac.mm

Index: chrome/browser/chrome_browser_application_mac.mm
diff --git a/chrome/browser/chrome_browser_application_mac.mm b/chrome/browser/chrome_browser_application_mac.mm
index baed0bbfa736e270e23be7e5bade0a110ca2fddb..3aa0a9c52f27b5cabb3baa668e059ac5c8de0f2a 100644
--- a/chrome/browser/chrome_browser_application_mac.mm
+++ b/chrome/browser/chrome_browser_application_mac.mm
@@ -389,7 +389,10 @@ void SwizzleInit() {
   NSString* actionString = NSStringFromSelector(anAction);
   NSString* value =
         [NSString stringWithFormat:@"%@ tag %d sending %@ to %p",
-                  [sender className], tag, actionString, aTarget];
+                  [sender className],
+                  static_cast<int32_t>(tag),

[Mark Mentovai, 2012/08/20 13:25:58]

The correct way to deal with NSInteger is a cast to long (and a format switch to
%ld). Similarly, NSUInteger is dealt with by a cast to unsigned long and %lu.
See
https://developer.apple.com/library/mac/#documentation/Cocoa/Conceptual/Strin...
.

+                  actionString,
+                  aTarget];
 
   base::mac::ScopedCrashKey key(kActionKey, value);