Fix automake files after README.md -> README rename

Fix automake files after README.md -> README rename

Minor followup to crrev.com/1357773004 and
crrev.com/1361993002 which moved the README and forgot
to update the automake files.
This is to make "./configure && make" work.

TBR=mark@chromium.org

Committed: https://chromium.googlesource.com/breakpad/breakpad/+/9d3e1f1c035ad4d4c31d289fdba279bec047d03a

[Primiano Tucci (use gerrit), 2015-09-28 13:00:51]

primiano@chromium.org changed reviewers:
+ mark@chromium.org

[Primiano Tucci (use gerrit), 2015-09-28 13:01:55]

Mark, TBR-ing this 2 line change. Just cleaning up makefiles to make ./configure
and make workflow working.

This CL reminds me:
http://ecx.images-amazon.com/images/I/41cA94UUuXL._SY344_BO1,204,203,200_.jpg

[Primiano Tucci (use gerrit), 2015-09-28 13:02:13]

Committed patchset #1 (id:1) manually as
9d3e1f1c035ad4d4c31d289fdba279bec047d03a (presubmit successful).

[Ted Mielczarek, 2015-09-28 13:43:07]

ted.mielczarek@gmail.com changed reviewers:
+ ted.mielczarek@gmail.com

[Ted Mielczarek, 2015-09-28 13:43:08]

lgtm

[Ted Mielczarek, 2015-09-28 13:43:31]

(And thanks, I hit this too. We should get some public-facing CI...)

[Mark Mentovai, 2015-09-28 13:52:30]

Primiano Tucci wrote:
> This CL reminds me:
> http://ecx.images-amazon.com/images/I/41cA94UUuXL._SY344_BO1,204,203,200_.jpg

:)

LGTM

[vapier, 2015-09-28 15:37:22]

meh, i don't think there's any realistic alternatives to autotools here

[Primiano Tucci (use gerrit), 2015-09-28 15:38:30]

On 2015/09/28 15:37:22, vapier wrote:
> meh, i don't think there's any realistic alternatives to autotools here

https://en.wikipedia.org/wiki/Stockholm_syndrome :)

[vapier, 2015-09-28 15:52:35]

vapier@chromium.org changed reviewers:
+ vapier@chromium.org

[vapier, 2015-09-28 15:52:36]

not really.  i've used plenty of other build systems, so i'm pretty aware of
their capabilities, especially when it comes to portability and
cross-compilation.  while autotools is not generally easy and has a history of
users cargo-culting code around, it's still the best imo in those two aspects. 
most newer build systems focus on a subset of these requirements.

[Ted Mielczarek, 2015-09-28 16:14:03]

On 2015/09/28 15:52:36, vapier wrote:
> not really.  i've used plenty of other build systems, so i'm pretty aware of
> their capabilities, especially when it comes to portability and
> cross-compilation.  while autotools is not generally easy and has a history of
> users cargo-culting code around, it's still the best imo in those two aspects.

> most newer build systems focus on a subset of these requirements.

This is pretty much true. I'm hoping someone will fix up bazel to be a realistic
alternative...