From: Matthew Veety <mveety@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 15:59:07 -0400 [thread overview]
Message-ID: <02C52704-4155-474C-A722-45B2EC877927@gmail.com> (raw)
In-Reply-To: <CAJSxfmJUc-dWARjba6PcAMFFoMCkOfu6ovKE5kFxR+7-ooFWsA@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 1705 bytes --]
I don't think changing ldelf.c would fix this issue. IIRC we don't use it on Plan 9.
On May 1, 2013, at 15:25, Skip Tavakkolian <skip.tavakkolian@gmail.com> wrote:
> found the other instance at line ldelf.c:681; the assignment from e32 is indirect via "add". same results as before.
>
>
> On Wed, May 1, 2013 at 12:14 PM, Skip Tavakkolian <skip.tavakkolian@gmail.com> wrote:
>> bootes% grep -n 'rp->add' *.[ch] | grep e32
>> ldelf.c:709: rp->add = e->e32(sect->base+rp->off);
>> ldmacho.c:807: rp->add = (int32)e->e32(s->p+rp->off) + rp->off + 4 - secaddr;
>> ldmacho.c:809: rp->add = (int32)e->e32(s->p+rp->off);
>> ldpe.c:294: rp->add = (int32)le32(rsect->base+rp->off);
>> ldpe.c:300: rp->add = le32(rsect->base+rp->off);
>>
>> it seems that ldelf.c:709 is the only place that fits your instructions. doing the cast has no effect (i.e. fails building cmd/go with the same error messages)
>>
>>
>> On Wed, May 1, 2013 at 11:54 AM, Rob Pike <robpike@gmail.com> wrote:
>>> that means you are building from source
>>>
>>> in the ld directory, look for assignments to rd->add from calls to e32. two do not do a cast to int32. try casting those two and let me know if you can
>>>
>>> i will be at work in a couple of hours, not on a phone, and can offer more help then.
>>>
>>>
>>> -rob
>>>
>>> On May 1, 2013, at 11:31 AM, Skip Tavakkolian <skip.tavakkolian@gmail.com> wrote:
>>>
>>>> yes.
>>>>
>>>>
>>>> On Wed, May 1, 2013 at 11:11 AM, Rob Pike <robpike@gmail.com> wrote:
>>>>> Are you using Plan 9? Because I don't understand how you could get
>>>>> those messages on Plan 9, but I do on other systems.
>>>>>
>>>>> -rob
>
[-- Attachment #2: Type: text/html, Size: 3497 bytes --]
next prev parent reply other threads:[~2013-05-01 19:59 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 [this message]
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
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=02C52704-4155-474C-A722-45B2EC877927@gmail.com \
--to=mveety@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).