Makes --analyzer behave same as --analyzer2

Makes --analyzer behave same as --analyzer2

Then I can convert recipes back to --analyzer and finally remove
--analyzer2. Oy!

BUG=109173
TEST=none
R=thakis@chromium.org

Committed: https://src.chromium.org/viewvc/chrome?view=rev&revision=288360

[Nico, 2014-08-07 21:37:10]

https://codereview.chromium.org/447183006/diff/1/build/gyp_chromium
File build/gyp_chromium (right):

https://codereview.chromium.org/447183006/diff/1/build/gyp_chromium#newcode199
build/gyp_chromium:199: args.append('-Ganalyzer_output_path=' + args.pop(0))
lgtm assuming args always has at least 2 elements in both analyzer and analyzer2
mode

[sky, 2014-08-07 21:41:04]

The CQ bit was checked by sky@chromium.org

[sky, 2014-08-07 21:41:42]

Your assumption is correct.

[commit-bot: I haz the power, 2014-08-07 22:22:22]

CQ is trying da patch. Follow status at
 https://chromium-status.appspot.com/cq/sky@chromium.org/447183006/1

[commit-bot: I haz the power, 2014-08-08 02:45:40]

FYI, CQ is re-trying this CL (attempt #1).
The failing builders are:
  android_dbg_triggered_tests on tryserver.chromium.linux
(http://build.chromium.org/p/tryserver.chromium.linux/builders/android_dbg_tri...)
  win_chromium_rel on tryserver.chromium.win
(http://build.chromium.org/p/tryserver.chromium.win/builders/win_chromium_rel/...)

[commit-bot: I haz the power, 2014-08-08 03:09:17]

The CQ bit was unchecked by commit-bot@chromium.org

[commit-bot: I haz the power, 2014-08-08 03:09:18]

Try jobs failed on following builders:
  android_dbg_triggered_tests on tryserver.chromium.linux
(http://build.chromium.org/p/tryserver.chromium.linux/builders/android_dbg_tri...)

[sky, 2014-08-08 14:45:44]

Committed patchset #1 manually as 288360 (presubmit successful).