The patch was not abandoned; that message was a codereview glitch. It's checked in.
We need to find where the bogus relocation is coming from. It *is* bogus, but the error catching it is new. To make progress, feel free to comment out the code that prints the error. I'm pretty sure you'll be fine. But I would like to understand where the bad relocation value is coming from. It's caused by something like a -4 becoming 0xFFFFFFFC, which doesn't matter when everything's 32 bits but is caught by the error checking code that's using 64 bits. -rob
