Update README.chromium for gold linker.

Update README.chromium for gold linker.

The binaries for gold were already committed in a
previous CL.

BUG=http://code.google.com/p/chromium/issues/detail?id=127646
r168091

[Nico, 2012-11-14 03:29:25]

lgtm

Can you link to the gold bug (if you have that at hand)?

http://codereview.chromium.org/11363231/diff/2001/README.chromium
File README.chromium (right):

http://codereview.chromium.org/11363231/diff/2001/README.chromium#newcode17
README.chromium:17: The build on a non-Lucid (e.g. Precise) machine, or to build
the 32-bit binary
s/The/To/

[robertm, 2012-11-14 04:05:19]

+olonho

he might know where that was tracked for binutils

On 2012/11/14 03:29:25, Nico wrote:
> lgtm
> 
> Can you link to the gold bug (if you have that at hand)?
> 
> http://codereview.chromium.org/11363231/diff/2001/README.chromium
> File README.chromium (right):
> 
> http://codereview.chromium.org/11363231/diff/2001/README.chromium#newcode17
> README.chromium:17: The build on a non-Lucid (e.g. Precise) machine, or to
build
> the 32-bit binary
> s/The/To/

[Nikolay, 2012-11-14 12:37:10]

Sorry couldn't find the bug, but I've certainly seen that it was recently
reported/fixed.
See http://code.google.com/p/chromium/issues/detail?id=127646 for similar report
on Chrome side.

[Sam Clegg, 2012-11-14 19:36:25]

On 2012/11/14 12:37:10, olonho wrote:
> Sorry couldn't find the bug, but I've certainly seen that it was recently
> reported/fixed.
> See http://code.google.com/p/chromium/issues/detail?id=127646 for similar
report
> on Chrome side.

I can't commit this as I am not yet a chrome commiter, and cl upload
will not upload the gold binaries as they are "too large".

Could somebody commit this for me?  I guess I would need to email
that person the binaries :(

[Nico, 2012-11-14 19:38:28]

On Wed, Nov 14, 2012 at 11:36 AM,  <sbc@chromium.org> wrote:
> On 2012/11/14 12:37:10, olonho wrote:
>>
>> Sorry couldn't find the bug, but I've certainly seen that it was recently
>> reported/fixed.
>> See http://code.google.com/p/chromium/issues/detail?id=127646 for similar
>
> report
>>
>> on Chrome side.
>
>
> I can't commit this as I am not yet a chrome commiter, and cl upload
> will not upload the gold binaries as they are "too large".
>
> Could somebody commit this for me?  I guess I would need to email
> that person the binaries :(

I can land. Put them somewhere in your home dir and email me the path.

>
>
> http://codereview.chromium.org/11363231/

[Nico, 2012-11-15 18:45:24]

Which gcc did you use to build this? (The binaries are 0.5 MB larger than the
old ones. They change rarely so I'm not concerned about the size; just curious)

[Nico, 2012-11-15 18:49:10]

Landed in r167975.

[sbc, 2012-11-15 20:06:34]

Awesome!  Thanks.

On Thu, Nov 15, 2012 at 10:49 AM,  <thakis@chromium.org> wrote:
> Landed in r167975.
>
> http://codereview.chromium.org/11363231/

[Sam Clegg, 2012-11-15 20:57:43]

On 2012/11/15 20:06:34, sbc wrote:
> Awesome!  Thanks.
> 
> On Thu, Nov 15, 2012 at 10:49 AM,  <mailto:thakis@chromium.org> wrote:
> > Landed in r167975.
> >
> > http://codereview.chromium.org/11363231/

Looks like you missed the README.chromium file.  I can land that through the
commit queue I guess?

[Nico, 2012-11-15 21:00:28]

On 2012/11/15 20:57:43, Sam Clegg wrote:
> On 2012/11/15 20:06:34, sbc wrote:
> > Awesome!  Thanks.
> > 
> > On Thu, Nov 15, 2012 at 10:49 AM,  <mailto:thakis@chromium.org> wrote:
> > > Landed in r167975.
> > >
> > > http://codereview.chromium.org/11363231/
> 
> Looks like you missed the README.chromium file.  I can land that through the
> commit queue I guess?

Doh, I just copied ~sbc/www/go*. Yes, you should be able to land that through
the CQ, but please update the CL description (add "The binaries have landed in
rXXX, this is just the corresponding README change" or some such). Sorry!

[Sam Clegg, 2012-11-15 23:34:34]

On 2012/11/15 21:00:28, Nico wrote:
> On 2012/11/15 20:57:43, Sam Clegg wrote:
> > On 2012/11/15 20:06:34, sbc wrote:
> > > Awesome!  Thanks.
> > > 
> > > On Thu, Nov 15, 2012 at 10:49 AM,  <mailto:thakis@chromium.org> wrote:
> > > > Landed in r167975.
> > > >
> > > > http://codereview.chromium.org/11363231/
> > 
> > Looks like you missed the README.chromium file.  I can land that through the
> > commit queue I guess?
> 
> Doh, I just copied ~sbc/www/go*. Yes, you should be able to land that through
> the CQ, but please update the CL description (add "The binaries have landed in
> rXXX, this is just the corresponding README change" or some such). Sorry!

Does the CQ work here?  I doesn't seem to be doing anything :(

[Nico, 2012-11-15 23:36:06]

On 2012/11/15 23:34:34, Sam Clegg wrote:
> Does the CQ work here?  I doesn't seem to be doing anything :(

It's possible it doesn't. I'll land the readme later today.

[Nico, 2012-11-16 00:17:48]

Readme landed in r168091.

By the way, if you just say "BUG=127646", rietveld will auto-link it. If you
want to be explicit, you can say BUG=chromium:127646 (or skia:123, gyp:432,
etc), that way you can link to other projects's bug trackers too.