Fix unresolved shared library dependency on binutils 2.23.

build/common.gypi

Index: build/common.gypi
diff --git a/build/common.gypi b/build/common.gypi
index 52a91e30392da630a489f467da72539eb8f1407c..33e834212d8484c86c238cead065d84adeb2293a 100644
--- a/build/common.gypi
+++ b/build/common.gypi
@@ -3893,7 +3893,7 @@
               '-B<!(cd <(DEPTH) && pwd -P)/<(binutils_dir)',
             ],
           }],
-          ['binutils_version>=224', {
+          ['binutils_version>=223', {

[dshwang, 2014/04/23 15:23:45]

I'm not sure if 222 works also. Anyway, 223 work well on my machine using "GNU
assembler (GNU Binutils for Ubuntu) 2.23.52.20130913"

[Lei Zhang, 2014/04/23 18:14:09]

I'm worried older 2.23 releases didn't have new-dtags enabled but newer 2.23
releases do. Maybe it's ok if they all take --disable-new-dtags.

Let me check this and get back to you.

[dshwang, 2014/04/23 20:05:23]

Thank you for review.
I think omitting --disable-new-dtags does not break old binutils, because we
don't use this flag before https://codereview.chromium.org/196573022

This flag is introduced for brand-new binutils in thirdparty/binutils
I don't think anyone use binutil 2.24 before the CL.

[dshwang, 2014/04/23 20:14:53]

Ah, my previous comment does not make sense.

The core of concern is that this CL try to introduce --disable-new-dtags in
binutils 2.23.
I could not check it yet because googling binutils shows me a lot of wastes.

             # Newer binutils don't set DT_RPATH unless you disable "new" dtags
             # and the new DT_RUNPATH doesn't work without --no-as-needed flag.
             # FIXME(mithro): Figure out the --as-needed/--no-as-needed flags