Disable warning in leveldb

Disable warning in leveldb

Patch has been committed upstream (internal) but it will be a while before it's
released to code.google.com, and then rolled into Chromium. So, disable
minor warning for now.

R=thakis@chromium.org
BUG=126483
Committed: https://src.chromium.org/viewvc/chrome?view=rev&revision=137678

[scottmg, 2012-05-17 16:32:52]

oops, forgot to push 'm'.

[Nico, 2012-05-17 17:13:25]

lgtm

do windows folks know all these warning codes by hand? if not, maybe add a
comment what this does and which file this is for (see e.g.
third_party/icu/icu.gyp WARNING_CFLAGS for how I did this for mac stuff)

Can you add a go link to internal review somewhere, so that googlers can check
what the state of that is?

[scottmg, 2012-05-17 17:21:44]

On 2012/05/17 17:13:25, Nico wrote:
> lgtm
> 
> do windows folks know all these warning codes by hand? if not, maybe add a
> comment what this does and which file this is for (see e.g.
> third_party/icu/icu.gyp WARNING_CFLAGS for how I did this for mac stuff)

Done.

> 
> Can you add a go link to internal review somewhere, so that googlers can check
> what the state of that is?

Done. (Hopefully no one will be angry with a .corp link 'leak')

[commit-bot: I haz the power, 2012-05-17 17:22:37]

CQ is trying da patch. Follow status at
https://chromium-status.appspot.com/cq/scottmg@chromium.org/10384092/4001

[Nico, 2012-05-17 17:24:45]

thanks!

https://chromiumcodereview.appspot.com/10384092/diff/4001/third_party/levelda...
File third_party/leveldatabase/leveldatabase.gyp (right):

https://chromiumcodereview.appspot.com/10384092/diff/4001/third_party/levelda...
third_party/leveldatabase/leveldatabase.gyp:60: # Internal link:
https://mondrian.corp.google.com/#review/29997992
nit: to not leak .corp links, the usual approach is to create a go/ link and
then say http://go/bla here

[commit-bot: I haz the power, 2012-05-17 17:25:38]

Try job failure for 10384092-4001 on win for step "update".
http://build.chromium.org/p/tryserver.chromium/buildstatus?builder=win&number...

Step "update" is always a major failure.
Look at the try server FAQ for more details.