9fans - fans of the OS Plan 9 from Bell Labs
 help / color / mirror / Atom feed
From: Skip Tavakkolian <skip.tavakkolian@gmail.com>
To: Fans of the OS Plan 9 from Bell Labs <9fans@9fans.net>
Subject: Re: [9fans] Go tip build fails
Date: Wed,  1 May 2013 11:56:38 -0700	[thread overview]
Message-ID: <CAJSxfmL90ZB1ph3_wxSUe740bsZyEH5fxQZP=nQOqK+xCd4agw@mail.gmail.com> (raw)
In-Reply-To: <20130501203039.65653bee@zinc.9fans.fr>

[-- Attachment #1: Type: text/plain, Size: 2087 bytes --]

the diagnostic string only appears in one place; it's in this presumably
abandoned patch:
 https://codereview.appspot.com/9036046/



On Wed, May 1, 2013 at 11:30 AM, David du Colombier <0intro@gmail.com>wrote:

> > Go build is failing today and no mention of it in issue tracker.
> > Anyone else seeing this problem?
>
> Same problem here.
>
> cmd/go
> main.parseMetaGoImports: pc-relative relocation address is too big:
> 0x10003b677
> main.parseMetaGoImports: pc-relative relocation address is too big:
> 0x100040cf3
> main.parseMetaGoImports: pc-relative relocation address is too big:
> 0x100049702
> main.init·1: pc-relative relocation address is too big: 0x10003b61a
> main.init·1: pc-relative relocation address is too big: 0x100000325
> main.init·1: pc-relative relocation address is too big: 0x100000317
> main.buildCompiler.Set: pc-relative relocation address is too big:
> 0x10003b5c7
> main.buildCompiler.Set: pc-relative relocation address is too big:
> 0x1000555a2
> main.buildCompiler.Set: pc-relative relocation address is too big:
> 0x100040b62
> main.buildCompiler.Set: pc-relative relocation address is too big:
> 0x100055508
> main.buildCompiler.Set: pc-relative relocation address is too big:
> 0x100040ad0
> main.buildCompiler.Set: pc-relative relocation address is too big:
> 0x100040b13
> main.buildCompiler.Set: pc-relative relocation address is too big:
> 0x10005f1ed
> main.buildCompiler.String: pc-relative relocation address is too big:
> 0x10003b3f7
> main.init·2: pc-relative relocation address is too big: 0x10003b3ca
> main.init·2: pc-relative relocation address is too big: 0x1000553a5
> main.init·2: pc-relative relocation address is too big: 0x100040965
> main.init·2: pc-relative relocation address is too big: 0x10005532f
> main.init·2: pc-relative relocation address is too big: 0x1000408f7
> main.addBuildFlags: pc-relative relocation address is too big: 0x10003b2b7
> main.addBuildFlags: pc-relative relocation address is too big: 0x10005a7fb
> too many errors
>
> --
> David du Colombier
>
>

[-- Attachment #2: Type: text/html, Size: 2625 bytes --]

  reply	other threads:[~2013-05-01 18:56 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-05-01 17:55 Skip Tavakkolian
2013-05-01 18:11 ` Rob Pike
2013-05-01 18:20   ` Jacob Todd
2013-05-01 18:31   ` Skip Tavakkolian
2013-05-01 18:54     ` Rob Pike
2013-05-01 19:14       ` Skip Tavakkolian
2013-05-01 19:25         ` Skip Tavakkolian
2013-05-01 19:59           ` Matthew Veety
2013-05-01 20:46             ` Russ Cox
2013-05-01 20:49               ` Jacob Todd
2013-05-01 20:58               ` Skip Tavakkolian
2013-05-01 21:32                 ` Rob Pike
2013-05-01 20:46             ` Rob Pike
2013-05-01 19:18       ` David du Colombier
2013-05-01 18:30 ` David du Colombier
2013-05-01 18:56   ` Skip Tavakkolian [this message]
2013-05-01 22:41 ` Rob Pike
2013-05-01 18:26 sl

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to='CAJSxfmL90ZB1ph3_wxSUe740bsZyEH5fxQZP=nQOqK+xCd4agw@mail.gmail.com' \
    --to=skip.tavakkolian@gmail.com \
    --cc=9fans@9fans.net \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).