From mboxrd@z Thu Jan  1 00:00:00 1970
MIME-Version: 1.0
In-Reply-To: <CANUoZoG08ALOtxOmHoMbZQhYYvCtnq1OpuJhAxX-UtvNbAGU2w@mail.gmail.com>
References: <CAA6Yd9UXY1d_rAv+SVy-yreynCVZfuGrHCZd4h_FuwZYhAFO9w@mail.gmail.com>
	<CANUoZoH28roGrBMvsRuZ0dpfYRHUSbaFb3Nj_PbX10ws2Veb3Q@mail.gmail.com>
	<CAA6Yd9VfU3V0=QO2H29hZ9G-qnPcwqH=DSsP1yeT-WB1ky=vHw@mail.gmail.com>
	<CALAsyW2qq8y04oNhhYY0SnP4Zh38cDZYZweMwRU7-54L1bXtpQ@mail.gmail.com>
	<CANUoZoG08ALOtxOmHoMbZQhYYvCtnq1OpuJhAxX-UtvNbAGU2w@mail.gmail.com>
From: Ramakrishnan Muthukrishnan <vu3rdd@gmail.com>
Date: Wed, 26 Mar 2014 18:53:18 +0530
Message-ID: <CAA6Yd9X2L_f4no3fLwe+KaV6yLneGxeRPRGEYQ_49EKimVPw+Q@mail.gmail.com>
To: Fans of the OS Plan 9 from Bell Labs <9fans@9fans.net>
Content-Type: text/plain; charset=UTF-8
Subject: Re: [9fans] Python/Mercurial error
Topicbox-Message-UUID: d0e13096-ead8-11e9-9d60-3106f5b1d025

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