From mboxrd@z Thu Jan 1 00:00:00 1970 MIME-Version: 1.0 In-Reply-To: <02C52704-4155-474C-A722-45B2EC877927@gmail.com> References: <02C52704-4155-474C-A722-45B2EC877927@gmail.com> From: Rob Pike Date: Wed, 1 May 2013 13:46:03 -0700 Message-ID: To: Fans of the OS Plan 9 from Bell Labs <9fans@9fans.net> Content-Type: text/plain; charset=UTF-8 Subject: Re: [9fans] Go tip build fails Topicbox-Message-UUID: 4f031a58-ead8-11e9-9d60-3106f5b1d025 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