Fix extensions compile issues for Android on sync_unit_tests.

chrome/browser/extensions/extension_warning_set.cc

Index: chrome/browser/extensions/extension_warning_set.cc
diff --git a/chrome/browser/extensions/extension_warning_set.cc b/chrome/browser/extensions/extension_warning_set.cc
index 84ca4a0e26fa75efdb7a24f0cb582f2b90d850da..77437437aa4b92cf276888cd1d7506f5a97c8846 100644
--- a/chrome/browser/extensions/extension_warning_set.cc
+++ b/chrome/browser/extensions/extension_warning_set.cc
@@ -111,7 +111,7 @@ void ExtensionWarningSet::SetWarning(ExtensionWarningSet::WarningType type,
 void ExtensionWarningSet::ClearWarnings(
     const std::set<ExtensionWarningSet::WarningType>& types) {
   bool deleted_anything = false;
-  for (const_iterator i = warnings_.begin(); i != warnings_.end();) {
+  for (iterator i = warnings_.begin(); i != warnings_.end();) {

[asargent_no_longer_on_chrome, 2012/02/22 21:47:55]

Out of curiousity, are you switching to using a non-const iterator here because
the call to erase below modifies the set?

[David Trainor- moved to gerrit, 2012/02/22 21:51:42]

It looks like our Android stl port of std::set doesn't have an erase method that
takes a const_iterator.  So this gives compile errors when I try to pass a
const_iterator to the erase call :(.

     if (types.find(i->warning_type()) != types.end()) {
       deleted_anything = true;
       warnings_.erase(i++);