From: Ramakrishnan Muthukrishnan <vu3rdd@gmail.com>
To: Fans of the OS Plan 9 from Bell Labs <9fans@9fans.net>
Subject: Re: [9fans] Python/Mercurial error
Date: Wed, 26 Mar 2014 18:53:18 +0530 [thread overview]
Message-ID: <CAA6Yd9X2L_f4no3fLwe+KaV6yLneGxeRPRGEYQ_49EKimVPw+Q@mail.gmail.com> (raw)
In-Reply-To: <CANUoZoG08ALOtxOmHoMbZQhYYvCtnq1OpuJhAxX-UtvNbAGU2w@mail.gmail.com>
On Wed, Mar 26, 2014 at 6:08 PM, David du Colombier <0intro@gmail.com> wrote:
> You can easily fix the generated include/plan9/plan9_libc.h file by
> hand for now. It seems /sys/include/libc.h is slightly different on
> 9atom, so the include/plan9/mklibc.rc script have to be adapted. Don't
> forget to comment out the generation of plan9_libc.h in src/make.rc.
I tried that, David. The build proceeds but I get a trap now.
pkg/text/template/parse
pkg/text/template
pkg/go/doc
pkg/go/build
cmd/go
sys: trap: invalid opcode pc=0x4d9e9
PC=4d9e9
goroutine 16 [running]:
runtime.cmpbody()
[.....]
and then it prints a bunch of registers (ax, bx, .. pc, flags, cs ..
gs) and their values. :(
I will see what went wrong with libc header file and try to come up
with some fix.
--
Ramakrishnan
next prev parent reply other threads:[~2014-03-26 13:23 UTC|newest]
Thread overview: 51+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-03-26 3:59 Ramakrishnan Muthukrishnan
2014-03-26 7:35 ` David du Colombier
2014-03-26 11:09 ` Ramakrishnan Muthukrishnan
2014-03-26 11:53 ` peterhull90
2014-03-26 12:08 ` Ramakrishnan Muthukrishnan
2014-03-26 13:50 ` erik quanstrom
2014-04-02 5:19 ` David du Colombier
2014-04-02 5:40 ` David du Colombier
2014-04-02 7:29 ` kokamoto
2014-04-03 5:12 ` kokamoto
2014-04-03 6:00 ` David du Colombier
2014-04-03 6:04 ` erik quanstrom
2014-04-02 12:48 ` erik quanstrom
2014-04-03 5:50 ` David du Colombier
2014-04-03 5:58 ` erik quanstrom
2014-04-03 6:15 ` Jeff Sickel
2014-04-03 6:20 ` David du Colombier
2014-04-03 6:24 ` erik quanstrom
2014-04-03 17:18 ` Ramakrishnan Muthukrishnan
2014-04-03 17:21 ` erik quanstrom
2014-04-03 17:57 ` David du Colombier
2014-04-03 18:01 ` erik quanstrom
2014-04-03 18:23 ` David du Colombier
2014-04-04 1:09 ` Ramakrishnan Muthukrishnan
2014-04-04 1:15 ` erik quanstrom
2014-04-03 18:04 ` Ramakrishnan Muthukrishnan
2014-04-03 19:21 ` David du Colombier
2014-04-04 5:39 ` Jeff Sickel
2014-04-07 18:27 ` Ramakrishnan Muthukrishnan
2014-04-04 10:53 ` Ramakrishnan Muthukrishnan
2014-04-04 11:38 ` David du Colombier
2014-03-26 12:09 ` Mark van Atten
2014-03-26 12:38 ` David du Colombier
2014-03-26 13:23 ` Ramakrishnan Muthukrishnan [this message]
2014-03-31 5:44 ` kokamoto
2014-03-31 6:23 ` David du Colombier
2014-03-31 6:47 ` kokamoto
2014-03-31 13:00 ` erik quanstrom
2014-04-01 0:57 ` kokamoto
2014-04-01 1:03 ` erik quanstrom
2014-04-01 2:27 ` kokamoto
2014-04-01 3:05 ` erik quanstrom
2014-04-01 6:46 ` kokamoto
2014-04-01 13:54 ` erik quanstrom
2014-04-02 2:54 ` kokamoto
2014-04-02 5:10 ` David du Colombier
2014-04-02 6:20 ` kokamoto
2014-03-26 13:47 ` erik quanstrom
2014-03-26 14:13 ` David du Colombier
2014-03-26 14:19 ` Ramakrishnan Muthukrishnan
2014-03-26 13:24 ` Ramakrishnan Muthukrishnan
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=CAA6Yd9X2L_f4no3fLwe+KaV6yLneGxeRPRGEYQ_49EKimVPw+Q@mail.gmail.com \
--to=vu3rdd@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).