[PATCH] win64 fix for libiberty md5.h

[DJ Delorie]

> That is definitely a concern in some cases, but I'm not very
> troubled by the case of uintptr_t.  If your libiberty build and your
> other builds don't agree on something as basic as uintptr_t, I think
> you have deeper problems.

They might differ on whether or not you think you *have* uintptr_t,
though.  If configure's default guess doesn't match uintptr_t, you
have a problem.  m32c would probably be such a case.

The most common problem we forethought was that the other module just
neglected to include the needed test in their configure.