[9fans] Python/Mercurial error

[9fans] Python/Mercurial error

[Ramakrishnan Muthukrishnan]

As I wrote in the previous email [1], I have Python and Mercurial
compiled from sources. When I use it to pull the golang sources, I
noticed the following error:

$ hg clone -u release http://code.google.com/p/go
[...]
added 19559 ...
updating to branch release-branch.go1.2
abort: invalid argument: '/sys/src/go/src'
Exception: KeyError(13155,) in module 'threading' from
'/sys/lib/python2.7/threading.pyc' ignored
abort: no such file or directory: '/sys/src/go/src/pkg/net/tcpsock_posix.go'

(I am typing this from looking at the virtualbox screen, pardon me if
there are any errors.)

Also https didn't work with hg as it gave me a tls error. I guess I
didn't build it with tls support. But that is okay..

[1] http://9fans.net/archive/2014/03/378
--
  Ramakrishnan

Re: [9fans] Python/Mercurial error

[David du Colombier]

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

Beside the Mercurial issue, the Go 1.2 release will not work on Plan 9. You
have to follow tip. Just remove "-u release" from the clone line.

--
David du Colombier

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

Re: [9fans] Python/Mercurial error

[Ramakrishnan Muthukrishnan]

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

On Wed, Mar 26, 2014 at 1:05 PM, David du Colombier <0intro@gmail.com> wrote:
> Beside the Mercurial issue, the Go 1.2 release will not work on Plan 9. You
> have to follow tip. Just remove "-u release" from the clone line.

I installed the python/hg binaries from the 9legacy webpage. I also
downloaded the go hg tip and did this:

cd src
./all.rc

I now get errors quite early itself while building lib9.a. Attaching a
screenshot. I still can't seem to copy text to/from virtualbox.

Ramakrishnan

[-- Attachment #2: go-build.png --]
[-- Type: image/png, Size: 47177 bytes --]

Re: [9fans] Python/Mercurial error

[peterhull90]

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

Could you post or have a look at libc_plan9.h - that file is generated by stripping out some things from /sys/include/libc.h and it appears that something in that process has generated a syntax error.


Pete

ps. I think it’s impossible to copy from vbox unless you have guest additions installed and AFAIK guest additions for plan9 have not been written.








From: Ramakrishnan Muthukrishnan
Sent: ‎Wednesday‎, ‎26‎ ‎March‎ ‎2014 ‎11‎:‎09
To: Fans of the OS Plan 9 from Bell Labs





On Wed, Mar 26, 2014 at 1:05 PM, David du Colombier <0intro@gmail.com> wrote:
> Beside the Mercurial issue, the Go 1.2 release will not work on Plan 9. You
> have to follow tip. Just remove "-u release" from the clone line.

I installed the python/hg binaries from the 9legacy webpage. I also
downloaded the go hg tip and did this:

cd src
./all.rc

I now get errors quite early itself while building lib9.a. Attaching a
screenshot. I still can't seem to copy text to/from virtualbox.

Ramakrishnan

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

Re: [9fans] Python/Mercurial error

[Ramakrishnan Muthukrishnan]

On Wed, Mar 26, 2014 at 5:23 PM,  <peterhull90@gmail.com> wrote:
> Could you post or have a look at libc_plan9.h - that file is generated by
> stripping out some things from /sys/include/libc.h and it appears that
> something in that process has generated a syntax error.

Pete,

Yes, you are right. I see an empty enum declaration:

enum {
}

.. in between the "extern .. tokenize.." and "extern .. malloc .. "
declarations.

I will see how this file is generated. Thank you very much. I am
running 9atom and not the Bell Labs plan9. I am not sure if some
structures are not in sync in any header files.

> ps. I think it’s impossible to copy from vbox unless you have guest
> additions installed and AFAIK guest additions for plan9 have not been
> written.

Ah, okay. Thanks. I think I will install it on natively on my desktop
PC this weekend.

Thanks again.
Ramakrishnan

Re: [9fans] Python/Mercurial error

[Mark van Atten]

>Attaching a
> screenshot. I still can't seem to copy text to/from virtualbox.

One thing you can do is to run Plan 9 in virtualbox but use drawterm
on the host to access it. Then you
can copy/paste from the drawterm window.

Mark.

Re: [9fans] Python/Mercurial error

[David du Colombier]

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.

--
David du Colombier

Re: [9fans] Python/Mercurial error

[Ramakrishnan Muthukrishnan]

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

Re: [9fans] Python/Mercurial error

[Ramakrishnan Muthukrishnan]

On Wed, Mar 26, 2014 at 5:39 PM, Mark van Atten <vanattenmark@gmail.com> wrote:
>>Attaching a
>> screenshot. I still can't seem to copy text to/from virtualbox.
>
> One thing you can do is to run Plan 9 in virtualbox but use drawterm
> on the host to access it. Then you
> can copy/paste from the drawterm window.

I haven't yet configured my system to be a CPU, does that matter? I
will take a dig at it tonight.

Thanks Mark.

Ramakrishnan

Re: [9fans] Python/Mercurial error

[erik quanstrom]

On Wed Mar 26 08:39:24 EDT 2014, 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.

this guess is incorrect.  i installed python/hg on 9atom
3 weeks ago with jeff, and there were no issues at all.

- erik

Re: [9fans] Python/Mercurial error

[erik quanstrom]

> Yes, you are right. I see an empty enum declaration:
>
> enum {
> }
>
> .. in between the "extern .. tokenize.." and "extern .. malloc .. "
> declarations.
>
> I will see how this file is generated. Thank you very much. I am
> running 9atom and not the Bell Labs plan9. I am not sure if some
> structures are not in sync in any header files.

i've seen this before.  but i don't exactly remember how i cleared
it up.  i think it involved mk'ing smaller bits, like mk stage first.
i didn't see this error the last time i tried.

- erik

Re: [9fans] Python/Mercurial error

[David du Colombier]

> this guess is incorrect.  i installed python/hg on 9atom
> 3 weeks ago with jeff, and there were no issues at all.

This is Go, not Python.

--
David du Colombier

Re: [9fans] Python/Mercurial error

[Ramakrishnan Muthukrishnan]

On Wed, Mar 26, 2014 at 7:17 PM, erik quanstrom <quanstro@quanstro.net> wrote:
> On Wed Mar 26 08:39:24 EDT 2014, 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.
>
> this guess is incorrect.  i installed python/hg on 9atom
> 3 weeks ago with jeff, and there were no issues at all.

There wasn't any issue installing hg and python. I have now tried
compiling from source and running the binaries and both work just fine
(I get the threading.py errors occasionally when running hg). The libc
header file error is when I tried to compile go-lang.

--
  Ramakrishnan

Re: [9fans] Python/Mercurial error

[kokamoto]

> 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 also had the same result using the recent Go code.
This is cause by the line of
$GOTOOLDIR/go_bootstrap cleaan -i std
in make.rc.

It can also make the same result for the
$GOTOOLDIR/go_bootstrap install ... line.

My go_bootstrap file size is 5143780.

Has anyone solved this successfully? How?

Kenji

Re: [9fans] Python/Mercurial error

[David du Colombier]

> I also had the same result using the recent Go code.
> This is cause by the line of
> $GOTOOLDIR/go_bootstrap cleaan -i std
> in make.rc.
>
> It can also make the same result for the
> $GOTOOLDIR/go_bootstrap install ... line.
>
> My go_bootstrap file size is 5143780.
>
> Has anyone solved this successfully? How?

Are you running 9atom? Ramakrishnan Muthukrishnan is also
running 9atom. I suspect this problem is specific to 9atom,
since I never encountered it on Plan 9.

Could you run acid on the process and provide us the
output of asm(*PC) and regs()? Thanks.

--
David du Colombier

Re: [9fans] Python/Mercurial error

[kokamoto]

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

> Are you running 9atom? Ramakrishnan Muthukrishnan is also
> running 9atom. I suspect this problem is specific to 9atom,
> since I never encountered it on Plan 9.

Yes, I'm running 9atom.

> Could you run acid on the process and provide us the
> output of asm(*PC) and regs()? Thanks.

Included is a log from go itself.
It's not acid result however.

I hope it may help you.

PS.
go_bootstrap runs safely for a simpler command,
such as go_bootstrap help xxx.

Kenji

[-- Attachment #2: Type: text/plain, Size: 7193 bytes --]

# Building C bootstrap tool.
cmd/dist

# Building compilers and Go bootstrap tool for host, plan9/386.
lib9
libbio
warning: /usr/sys/src/go/src/libbio/bputrune.c:39[/usr/sys/src/go/src/libbio/bputrune.c:1448] result of operation not used
libmach
warning: /usr/sys/src/go/src/libmach/8db.c:207[/usr/sys/src/go/src/libmach/8db.c:2156] unreachable code FUNC
warning: /usr/sys/src/go/src/libmach/sym.c:374[/usr/sys/src/go/src/libmach/sym.c:2196] useless or misleading comparison: UINT < 0
liblink
misc/pprof
cmd/objdump
cmd/prof
cmd/cc
warning: /usr/sys/src/go/src/cmd/cc/y.tab.c:1785[/usr/sys/src/go/src/cmd/cc/y.tab.c:4591] result of operation not used
warning: /usr/sys/src/go/src/cmd/cc/y.tab.c:1785[/usr/sys/src/go/src/cmd/cc/y.tab.c:4591] result of operation not used
warning: /usr/sys/src/go/src/cmd/cc/y.tab.c:1791[/usr/sys/src/go/src/cmd/cc/y.tab.c:4597] result of operation not used
warning: /usr/sys/src/go/src/cmd/cc/y.tab.c:1791[/usr/sys/src/go/src/cmd/cc/y.tab.c:4597] result of operation not used
warning: /usr/sys/src/go/src/cmd/cc/y.tab.c:1788[/usr/sys/src/go/src/cmd/cc/y.tab.c:4594] set and not used: yymsg
warning: /usr/sys/src/go/src/cmd/cc/y.tab.c:1868[/usr/sys/src/go/src/cmd/cc/y.tab.c:4669] set and not used: yytoken
warning: /usr/sys/src/go/src/cmd/cc/y.tab.c:1952[/usr/sys/src/go/src/cmd/cc/y.tab.c:4749] set and not used: yyptr
cmd/gc
warning: /usr/sys/src/go/src/cmd/gc/y.tab.c:2049[/usr/sys/src/go/src/cmd/gc/y.tab.c:5495] useless or misleading comparison: ULONG <= 0xffffffff
warning: /usr/sys/src/go/src/cmd/gc/y.tab.c:2072[/usr/sys/src/go/src/cmd/gc/y.tab.c:5516] useless or misleading comparison: ULONG <= 0xffffffff
warning: /usr/sys/src/go/src/cmd/gc/y.tab.c:2080[/usr/sys/src/go/src/cmd/gc/y.tab.c:5524] useless or misleading comparison: ULONG <= 0xffffffff
warning: /usr/sys/src/go/src/cmd/gc/y.tab.c:2124[/usr/sys/src/go/src/cmd/gc/y.tab.c:5566] result of operation not used
warning: /usr/sys/src/go/src/cmd/gc/y.tab.c:2124[/usr/sys/src/go/src/cmd/gc/y.tab.c:5566] result of operation not used
warning: /usr/sys/src/go/src/cmd/gc/y.tab.c:2127[/usr/sys/src/go/src/cmd/gc/y.tab.c:5569] set and not used: yymsg
warning: /usr/sys/src/go/src/cmd/gc/y.tab.c:2234[/usr/sys/src/go/src/cmd/gc/y.tab.c:5671] set and not used: yytoken
warning: /usr/sys/src/go/src/cmd/gc/y.tab.c:2309[/usr/sys/src/go/src/cmd/gc/y.tab.c:5740] set and not used: yyptr
cmd/8l
cmd/8a
warning: /usr/sys/src/go/src/cmd/8a/y.tab.c:1376[/usr/sys/src/go/src/cmd/8a/y.tab.c:4280] result of operation not used
warning: /usr/sys/src/go/src/cmd/8a/y.tab.c:1376[/usr/sys/src/go/src/cmd/8a/y.tab.c:4280] result of operation not used
warning: /usr/sys/src/go/src/cmd/8a/y.tab.c:1379[/usr/sys/src/go/src/cmd/8a/y.tab.c:4283] set and not used: yymsg
warning: /usr/sys/src/go/src/cmd/8a/y.tab.c:1567[/usr/sys/src/go/src/cmd/8a/y.tab.c:4459] set and not used: yyptr
cmd/8c
cmd/8g
pkg/runtime
pkg/errors
pkg/sync/atomic
pkg/sync
pkg/io
pkg/unicode
pkg/unicode/utf8
pkg/unicode/utf16
pkg/bytes
pkg/math
pkg/strings
pkg/strconv
pkg/bufio
pkg/sort
pkg/container/heap
pkg/encoding/base64
pkg/syscall
pkg/time
pkg/os
pkg/reflect
pkg/fmt
pkg/encoding
pkg/encoding/json
pkg/flag
pkg/path/filepath
pkg/path
pkg/io/ioutil
pkg/log
pkg/regexp/syntax
pkg/regexp
pkg/go/token
pkg/go/scanner
pkg/go/ast
pkg/go/parser
pkg/os/exec
pkg/os/signal
pkg/net/url
pkg/text/template/parse
pkg/text/template
pkg/go/doc
pkg/go/build
cmd/go
sys: trap: invalid opcode pc=0x4f9c9
PC=0x4f9c9

goroutine 16 [running]:
runtime.cmpbody()
	/usr/sys/src/go/src/pkg/runtime/asm_386.s:1251 +0x29 fp=0x10507408
runtime.cmpstring(0x105369c0, 0x10, 0x1053e680, 0x13, 0x1056faa0)
	/usr/sys/src/go/src/pkg/runtime/asm_386.s:1190 +0x15 fp=0x1050740c
io/ioutil.byName.Less(0x104c4a80, 0xa, 0x64, 0x7, 0x6, ...)
	/usr/sys/src/go/src/pkg/io/ioutil/ioutil.go:95 +0x96 fp=0x10507430
io/ioutil.(*byName).Less(0x10536a00, 0x7, 0x6, 0x0)
	/usr/sys/src/go/src/pkg/io/ioutil/ioutil.go:1 +0x7c fp=0x10507450
sort.insertionSort(0x304957d0, 0x10536a00, 0x6, 0xa)
	/usr/sys/src/go/src/pkg/sort/sort.go:32 +0x5c fp=0x10507470
sort.quickSort(0x304957d0, 0x10536a00, 0x6, 0xa, 0x7)
	/usr/sys/src/go/src/pkg/sort/sort.go:185 +0x104 fp=0x10507498
sort.quickSort(0x304957d0, 0x10536a00, 0x0, 0xa, 0x7)
	/usr/sys/src/go/src/pkg/sort/sort.go:180 +0x128 fp=0x105074c0
sort.Sort(0x304957d0, 0x10536a00)
	/usr/sys/src/go/src/pkg/sort/sort.go:200 +0x6c fp=0x105074e0
io/ioutil.ReadDir(0x1053e380, 0x1b, 0x0, 0x0, 0x0, ...)
	/usr/sys/src/go/src/pkg/io/ioutil/ioutil.go:110 +0x155 fp=0x10507528
go/build.(*Context).readDir(0x36ee80, 0x1053e380, 0x1b, 0x0, 0x0, ...)
	/usr/sys/src/go/src/pkg/go/build/build.go:174 +0xa1 fp=0x1050754c
go/build.(*Context).Import(0x36ee80, 0x1dd6b0, 0x1, 0x1053e300, 0x1b, ...)
	/usr/sys/src/go/src/pkg/go/build/build.go:585 +0xce4 fp=0x105079f0
go/build.(*Context).ImportDir(0x36ee80, 0x1053e300, 0x1b, 0x0, 0x2b3090, ...)
	/usr/sys/src/go/src/pkg/go/build/build.go:396 +0x5f fp=0x10507a18
main.func·021(0x1053e300, 0x1b, 0x30495620, 0x1056f6e0, 0x0, ...)
	/usr/sys/src/go/src/cmd/go/main.go:526 +0x2a9 fp=0x10507a9c
path/filepath.walk(0x1053e300, 0x1b, 0x30495620, 0x1056f6e0, 0x10507c6c, ...)
	/usr/sys/src/go/src/pkg/path/filepath/path.go:343 +0x79 fp=0x10507b28
path/filepath.walk(0x1053e140, 0x18, 0x30495620, 0x104a5530, 0x10507c6c, ...)
	/usr/sys/src/go/src/pkg/path/filepath/path.go:368 +0x3a3 fp=0x10507bb4
path/filepath.Walk(0x1053e140, 0x18, 0x10507c6c, 0x0, 0x0)
	/usr/sys/src/go/src/pkg/path/filepath/path.go:390 +0xb0 fp=0x10507be0
main.matchPackages(0xdeffefa8, 0x3, 0x0, 0x0, 0x0)
	/usr/sys/src/go/src/cmd/go/main.go:535 +0x2b3 fp=0x10507ca4
main.allPackages(0xdeffefa8, 0x3, 0x0, 0x0, 0x0)
	/usr/sys/src/go/src/cmd/go/main.go:479 +0x4a fp=0x10507d04
main.importPathsNoDotExpansion(0x1049a018, 0x1, 0x1, 0x0, 0x0, ...)
	/usr/sys/src/go/src/cmd/go/main.go:310 +0x266 fp=0x10507d90
main.importPaths(0x1049a018, 0x1, 0x1, 0x0, 0x0, ...)
	/usr/sys/src/go/src/cmd/go/main.go:320 +0x5b fp=0x10507e04
main.packagesAndErrors(0x1049a018, 0x1, 0x1, 0x0, 0x0, ...)
	/usr/sys/src/go/src/cmd/go/pkg.go:806 +0x19e fp=0x10507e90
main.runClean(0x369f00, 0x1049a018, 0x1, 0x1)
	/usr/sys/src/go/src/cmd/go/clean.go:75 +0x3a fp=0x10507eb8
main.main()
	/usr/sys/src/go/src/cmd/go/main.go:161 +0x449 fp=0x10507f9c
runtime.main()
	/usr/sys/src/go/src/pkg/runtime/proc.c:243 +0x106 fp=0x10507fd0
runtime.goexit()
	/usr/sys/src/go/src/pkg/runtime/proc.c:1426 fp=0x10507fd4
created by _rt0_go
	/usr/sys/src/go/src/pkg/runtime/asm_386.s:101 +0xf7

goroutine 19 [finalizer wait]:
runtime.park(0x5dab0, 0x36e2f8, 0x36d75c)
	/usr/sys/src/go/src/pkg/runtime/proc.c:1350 +0x80
runtime.parkunlock(0x36e2f8, 0x36d75c)
	/usr/sys/src/go/src/pkg/runtime/proc.c:1366 +0x3b
runfinq()
	/usr/sys/src/go/src/pkg/runtime/mgc0.c:2578 +0xb0
runtime.goexit()
	/usr/sys/src/go/src/pkg/runtime/proc.c:1426

ax	0x13
bx	0x10
cx	0x1053e680
dx	0x13
di	0x1053e680
si	0x105369c0
bp	0x10
sp	0x10507404
pc	0x4f9c9
flags	0x10246
cs	0x23
fs	0x1b
gs	0xf010001b
all.rc 255: go_bootstrap 810: sys: trap: invalid opcode pc=0x4f9c9

Re: [9fans] Python/Mercurial error

[erik quanstrom]

which kernel are you running?  the 386 kernel or the 386pae kernel?

- erik

Re: [9fans] Python/Mercurial error

[kokamoto]

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

I've been apart from Plan9 for days, then, please
forgive my silly question.

What is 386pae kernel, and how I can find
which kernel I'm running.

Kenji

[-- Attachment #2: Type: message/rfc822, Size: 3560 bytes --]

From: erik quanstrom <quanstro@quanstro.net>
To: 9fans@9fans.net
Subject: Re: [9fans] Python/Mercurial error
Date: Mon, 31 Mar 2014 09:00:57 -0400
Message-ID: <b9769546c4cbabfac177be309d7d0308@mikro.quanstro.net>

which kernel are you running?  the 386 kernel or the 386pae kernel?

- erik

Re: [9fans] Python/Mercurial error

[erik quanstrom]

On Mon Mar 31 21:01:35 EDT 2014, kokamoto@hera.eonet.ne.jp wrote:

> I've been apart from Plan9 for days, then, please
> forgive my silly question.
>
> What is 386pae kernel, and how I can find
> which kernel I'm running.

the 386pae kernel is in /sys/src/9/pcpae.  it is the same as the pc kernel,
except is uses physical address extension to address more than 4GB
of memory.  (but not too much more.  :-))

- erik

Re: [9fans] Python/Mercurial error

[kokamoto]

> the 386pae kernel is in /sys/src/9/pcpae.  it is the same as the pc kernel,
> except is uses physical address extension to address more than 4GB
> of memory.  (but not too much more.  :-))

Thanks, eric.
I found '9fs atom' just now.☺
Yes, I found /sys/src/9/pcpae and teg2 directory.
Much proceedings were made during I'm sleeping...
Thanks to authors contributed them.

The fact that '9fs atom' is there means atom is
completely independent distribution of Plan9?

By the way, I'm definitely running 386 kernel.

Kenji

Re: [9fans] Python/Mercurial error

[erik quanstrom]

> The fact that '9fs atom' is there means atom is
> completely independent distribution of Plan9?

technically, atom is independent sources, but
i wouldn't read anything into that.

9fs atom is just an easy way to access the source.

> By the way, I'm definitely running 386 kernel.

you'll need to run the pae kernel.  it has support for
sse, which you will need for go.

- erik

Re: [9fans] Python/Mercurial error

[kokamoto]

> you'll need to run the pae kernel.  it has support for
> sse, which you will need for go.

Ok, I'll try it.
I have somewhat complicated feeling on linux's PAE kernal.
Isn't ther anything wrong to run pae kernel, somthing
like some application don't run on it etc.

Kenji

Re: [9fans] Python/Mercurial error

[erik quanstrom]

> Ok, I'll try it.
> I have somewhat complicated feeling on linux's PAE kernal.
> Isn't ther anything wrong to run pae kernel, somthing
> like some application don't run on it etc.

everything should run fine.

- erik

Re: [9fans] Python/Mercurial error

[kokamoto]

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

I built pcpae kernel and recompiled go distribution,
and probably success.
Attached is the go compilation result, and the last line
shows the used go version.

Someone can explain the meaning of the last error?

Kenji

[-- Attachment #2: go.log --]
[-- Type: text/plain, Size: 9204 bytes --]

# Building C bootstrap tool.
cmd/dist

# Building compilers and Go bootstrap tool for host, plan9/386.
lib9
libbio
warning: /usr/sys/src/go/src/libbio/bputrune.c:39[/usr/sys/src/go/src/libbio/bputrune.c:1449] result of operation not used
libmach
warning: /usr/sys/src/go/src/libmach/8db.c:207[/usr/sys/src/go/src/libmach/8db.c:2157] unreachable code FUNC
warning: /usr/sys/src/go/src/libmach/sym.c:374[/usr/sys/src/go/src/libmach/sym.c:2197] useless or misleading comparison: UINT < 0
liblink
misc/pprof
cmd/objdump
cmd/prof
cmd/cc
warning: /usr/sys/src/go/src/cmd/cc/y.tab.c:1785[/usr/sys/src/go/src/cmd/cc/y.tab.c:4592] result of operation not used
warning: /usr/sys/src/go/src/cmd/cc/y.tab.c:1785[/usr/sys/src/go/src/cmd/cc/y.tab.c:4592] result of operation not used
warning: /usr/sys/src/go/src/cmd/cc/y.tab.c:1791[/usr/sys/src/go/src/cmd/cc/y.tab.c:4598] result of operation not used
warning: /usr/sys/src/go/src/cmd/cc/y.tab.c:1791[/usr/sys/src/go/src/cmd/cc/y.tab.c:4598] result of operation not used
warning: /usr/sys/src/go/src/cmd/cc/y.tab.c:1788[/usr/sys/src/go/src/cmd/cc/y.tab.c:4595] set and not used: yymsg
warning: /usr/sys/src/go/src/cmd/cc/y.tab.c:1868[/usr/sys/src/go/src/cmd/cc/y.tab.c:4670] set and not used: yytoken
warning: /usr/sys/src/go/src/cmd/cc/y.tab.c:1952[/usr/sys/src/go/src/cmd/cc/y.tab.c:4750] set and not used: yyptr
cmd/gc
warning: /usr/sys/src/go/src/cmd/gc/y.tab.c:2049[/usr/sys/src/go/src/cmd/gc/y.tab.c:5496] useless or misleading comparison: ULONG <= 0xffffffff
warning: /usr/sys/src/go/src/cmd/gc/y.tab.c:2072[/usr/sys/src/go/src/cmd/gc/y.tab.c:5517] useless or misleading comparison: ULONG <= 0xffffffff
warning: /usr/sys/src/go/src/cmd/gc/y.tab.c:2080[/usr/sys/src/go/src/cmd/gc/y.tab.c:5525] useless or misleading comparison: ULONG <= 0xffffffff
warning: /usr/sys/src/go/src/cmd/gc/y.tab.c:2124[/usr/sys/src/go/src/cmd/gc/y.tab.c:5567] result of operation not used
warning: /usr/sys/src/go/src/cmd/gc/y.tab.c:2124[/usr/sys/src/go/src/cmd/gc/y.tab.c:5567] result of operation not used
warning: /usr/sys/src/go/src/cmd/gc/y.tab.c:2127[/usr/sys/src/go/src/cmd/gc/y.tab.c:5570] set and not used: yymsg
warning: /usr/sys/src/go/src/cmd/gc/y.tab.c:2234[/usr/sys/src/go/src/cmd/gc/y.tab.c:5672] set and not used: yytoken
warning: /usr/sys/src/go/src/cmd/gc/y.tab.c:2309[/usr/sys/src/go/src/cmd/gc/y.tab.c:5741] set and not used: yyptr
cmd/8l
cmd/8a
warning: /usr/sys/src/go/src/cmd/8a/y.tab.c:1376[/usr/sys/src/go/src/cmd/8a/y.tab.c:4281] result of operation not used
warning: /usr/sys/src/go/src/cmd/8a/y.tab.c:1376[/usr/sys/src/go/src/cmd/8a/y.tab.c:4281] result of operation not used
warning: /usr/sys/src/go/src/cmd/8a/y.tab.c:1379[/usr/sys/src/go/src/cmd/8a/y.tab.c:4284] set and not used: yymsg
warning: /usr/sys/src/go/src/cmd/8a/y.tab.c:1567[/usr/sys/src/go/src/cmd/8a/y.tab.c:4460] set and not used: yyptr
cmd/8c
cmd/8g
pkg/runtime
pkg/errors
pkg/sync/atomic
pkg/sync
pkg/io
pkg/unicode
pkg/unicode/utf8
pkg/unicode/utf16
pkg/bytes
pkg/math
pkg/strings
pkg/strconv
pkg/bufio
pkg/sort
pkg/container/heap
pkg/encoding/base64
pkg/syscall
pkg/time
pkg/os
pkg/reflect
pkg/fmt
pkg/encoding
pkg/encoding/json
pkg/flag
pkg/path/filepath
pkg/path
pkg/io/ioutil
pkg/log
pkg/regexp/syntax
pkg/regexp
pkg/go/token
pkg/go/scanner
pkg/go/ast
pkg/go/parser
pkg/os/exec
pkg/os/signal
pkg/net/url
pkg/text/template/parse
pkg/text/template
pkg/go/doc
pkg/go/build
cmd/go

# Building packages and commands for plan9/386.
runtime
errors
sync/atomic
sync
io
unicode
unicode/utf8
bytes
bufio
math
strconv
reflect
encoding/binary
syscall
time
os
fmt
debug/dwarf
debug/elf
strings
debug/gosym
debug/macho
debug/pe
sort
flag
log
cmd/addr2line
hash
crypto
crypto/md5
go/token
path/filepath
go/scanner
go/ast
io/ioutil
go/parser
text/tabwriter
go/printer
os/exec
cmd/cgo
go/format
path
cmd/fix
container/heap
encoding
encoding/base64
unicode/utf16
encoding/json
encoding/xml
regexp/syntax
regexp
net/url
text/template/parse
text/template
go/doc
go/build
compress/flate
hash/crc32
compress/gzip
container/list
crypto/subtle
crypto/cipher
crypto/aes
crypto/des
math/rand
math/big
crypto/elliptic
crypto/ecdsa
crypto/hmac
crypto/rand
crypto/rc4
crypto/rsa
crypto/sha1
crypto/sha256
crypto/dsa
encoding/asn1
crypto/x509/pkix
encoding/hex
encoding/pem
net
crypto/x509
crypto/tls
mime
net/textproto
mime/multipart
net/http
os/signal
cmd/go
runtime/pprof
cmd/gofmt
debug/goobj
cmd/link
debug/plan9obj
cmd/nm
cmd/pack
cmd/yacc
archive/tar
archive/zip
compress/bzip2
compress/lzw
hash/adler32
compress/zlib
container/ring
crypto/sha512
database/sql/driver
database/sql
encoding/ascii85
encoding/base32
encoding/csv
encoding/gob
expvar
hash/crc64
hash/fnv
html
html/template
image/color
image
image/color/palette
image/draw
image/gif
image/jpeg
image/png
index/suffixarray
log/syslog
math/cmplx
net/http/cgi
net/http/cookiejar
net/http/fcgi
net/http/httptest
net/http/httputil
net/http/pprof
net/mail
net/rpc
net/rpc/jsonrpc
net/smtp
os/user
runtime/debug
runtime/race
testing
testing/iotest
testing/quick
text/scanner

# Testing packages.
?   	cmd/addr2line	[no test files]
?   	cmd/cgo	[no test files]
ok  	cmd/fix	0.038s
ok  	cmd/go	0.041s
ok  	cmd/gofmt	0.107s
ok  	cmd/link	0.099s
?   	cmd/nm	[no test files]
ok  	cmd/pack	1.038s
?   	cmd/yacc	[no test files]
ok  	archive/tar	0.031s
ok  	archive/zip	0.594s
ok  	bufio	0.173s
ok  	bytes	0.211s
ok  	compress/bzip2	0.114s
ok  	compress/flate	1.457s
ok  	compress/gzip	0.393s
ok  	compress/lzw	0.746s
ok  	compress/zlib	1.710s
ok  	container/heap	0.020s
ok  	container/list	0.020s
ok  	container/ring	0.033s
?   	crypto	[no test files]
ok  	crypto/aes	0.054s
ok  	crypto/cipher	0.104s
ok  	crypto/des	0.038s
ok  	crypto/dsa	0.054s
ok  	crypto/ecdsa	0.111s
ok  	crypto/elliptic	0.095s
ok  	crypto/hmac	0.024s
ok  	crypto/md5	0.089s
ok  	crypto/rand	0.078s
ok  	crypto/rc4	0.210s
ok  	crypto/rsa	0.738s
ok  	crypto/sha1	0.021s
ok  	crypto/sha256	0.020s
ok  	crypto/sha512	0.023s
ok  	crypto/subtle	0.029s
ok  	crypto/tls	5.062s
ok  	crypto/x509	6.752s
?   	crypto/x509/pkix	[no test files]
ok  	database/sql	0.182s
ok  	database/sql/driver	0.019s
ok  	debug/dwarf	0.143s
ok  	debug/elf	0.240s
ok  	debug/goobj	0.018s
ok  	debug/gosym	0.020s
ok  	debug/macho	0.227s
ok  	debug/pe	0.227s
ok  	debug/plan9obj	0.078s
?   	encoding	[no test files]
ok  	encoding/ascii85	0.024s
ok  	encoding/asn1	0.029s
ok  	encoding/base32	0.025s
ok  	encoding/base64	0.026s
ok  	encoding/binary	0.026s
ok  	encoding/csv	0.025s
ok  	encoding/gob	0.079s
ok  	encoding/hex	0.025s
ok  	encoding/json	0.263s
ok  	encoding/pem	0.023s
ok  	encoding/xml	0.047s
ok  	errors	0.020s
ok  	expvar	0.032s
ok  	flag	0.020s
ok  	fmt	0.093s
ok  	go/ast	0.035s
ok  	go/build	10.093s
ok  	go/doc	0.277s
ok  	go/format	0.030s
ok  	go/parser	0.062s
ok  	go/printer	0.962s
ok  	go/scanner	0.022s
ok  	go/token	0.069s
?   	hash	[no test files]
ok  	hash/adler32	0.031s
ok  	hash/crc32	0.020s
ok  	hash/crc64	0.024s
ok  	hash/fnv	0.021s
ok  	html	0.022s
ok  	html/template	0.146s
ok  	image	0.906s
ok  	image/color	0.027s
?   	image/color/palette	[no test files]
ok  	image/draw	0.148s
ok  	image/gif	0.218s
ok  	image/jpeg	0.402s
ok  	image/png	0.078s
ok  	index/suffixarray	0.028s
ok  	io	0.035s
ok  	io/ioutil	0.024s
ok  	log	0.025s
?   	log/syslog	[no test files]
ok  	math	0.025s
ok  	math/big	0.527s
ok  	math/cmplx	0.021s
ok  	math/rand	0.561s
ok  	mime	0.022s
ok  	mime/multipart	1.587s
--- FAIL: TestResolveIPAddr (0.00 seconds)
	ipraw_test.go:74: ResolveIPAddr(ip6:ipv6-icmp, ::1) failed: write /net/cs: cs: no match
FAIL
FAIL	net	0.948s
ok  	net/http	8.576s
ok  	net/http/cgi	0.161s
ok  	net/http/cookiejar	0.034s
ok  	net/http/fcgi	0.031s
ok  	net/http/httptest	0.061s
ok  	net/http/httputil	0.180s
?   	net/http/pprof	[no test files]
ok  	net/mail	0.024s
ok  	net/rpc	0.181s
ok  	net/rpc/jsonrpc	0.036s
ok  	net/smtp	0.110s
ok  	net/textproto	0.024s
ok  	net/url	0.024s
ok  	os	3.890s
ok  	os/exec	0.470s
ok  	os/signal	0.017s
ok  	os/user	0.021s
ok  	path	0.022s
ok  	path/filepath	1.067s
ok  	reflect	0.168s
ok  	regexp	0.375s
ok  	regexp/syntax	1.337s
ok  	runtime	96.535s
ok  	runtime/debug	0.090s
ok  	runtime/pprof	0.989s
?   	runtime/race	[no test files]
ok  	sort	0.133s
ok  	strconv	0.761s
ok  	strings	0.193s
ok  	sync	0.135s
ok  	sync/atomic	0.143s
ok  	syscall	0.021s
ok  	testing	2.812s
?   	testing/iotest	[no test files]
ok  	testing/quick	0.072s
ok  	text/scanner	0.025s
ok  	text/tabwriter	0.023s
ok  	text/template	0.071s
ok  	text/template/parse	0.029s
ok  	time	3.809s
ok  	unicode	0.027s
ok  	unicode/utf16	0.022s
ok  	unicode/utf8	0.028s
?   	unsafe	[no test files]
53.89u 15.41s 377.21r 	 go test std -short -timeout ...  # status= 1
all.rc 1771: run.rc 2577: time 2583: go 2584: 1

-------
go version
go version devel +1afdecdd77c1 Sat Mar 29 17:10:25 2014 -0400 plan9/386

Re: [9fans] Python/Mercurial error

[David du Colombier]

> Someone can explain the meaning of the last error?

> --- FAIL: TestResolveIPAddr (0.00 seconds)
> 	ipraw_test.go:74: ResolveIPAddr(ip6:ipv6-icmp, ::1) failed: write /net/cs: cs: no match
> FAIL
> FAIL	net	0.948s

The ResolveIPAddr test is failing because you don't have
the ::1 address configured on the loopback.

You can add it with:

ip/ipconfig loopback /dev/null ::1

Anyway, it doesn't really matter if you can't run all
the tests. Go is properly compiled and installed on
your machine and you're now able to use it.

How did you succeed to run go_bootstrap? Have you
just switched from the 9atom pc kernel to the pcpae
kernel?

--
David du Colombier

Re: [9fans] Python/Mercurial error

[David du Colombier]

Two days ago, I've fixed the script mklibc.rc to
generate the libc_plan9.h file properly on 9atom.

https://codereview.appspot.com/82660044/

Please give a try and review this change to
get it submitted before the Go 1.4 release.

--
David du Colombier

Re: [9fans] Python/Mercurial error

[David du Colombier]

> before the Go 1.4 release.

Sorry, I mean Go 1.3 of course.

--
David du Colombier

Re: [9fans] Python/Mercurial error

[kokamoto]

Thanks David.

> How did you succeed to run go_bootstrap? Have you
> just switched from the 9atom pc kernel to the pcpae
> kernel?

I just switched from 9atom pc to pcpae kernel.

When I run /usr/sys/src/go/src/all.rc, it fails
to make $GOROOT/include/plan9/libc_plan9.h.
Then, I removed the lines of empty enum, as
enum
{
}
.

After I made change to $GOROOT/src/make.rc to comment
out the line
../include/plan9/mklibc.rc > ../include/plan9/libc_plan9.h ,
I rerun all.rc.
Everything runs ok then.

Kenji

Re: [9fans] Python/Mercurial error

[kokamoto]

> https://codereview.appspot.com/82660044/
>
> Please give a try and review this change to
> get it submitted before the Go 1.4 release.

I tried this, and compilation becomes seamless.
However, a new test error occured as:
=========
?   	cmd/nm	[no test files]
pack.test 1119: suicide: sys: trap: fault read addr=0xeafffffc pc=0x254b6
*** Test killed: ran too long (3m0s).
FAIL	cmd/pack	180.007s
?   	cmd/yacc	[no test files]
=========

I'm still half sleeping, then,
David, please submit this result to go team from you.

Kenji

Re: [9fans] Python/Mercurial error

[erik quanstrom]

On Wed Apr  2 01:20:42 EDT 2014, 0intro@gmail.com wrote:
> Two days ago, I've fixed the script mklibc.rc to
> generate the libc_plan9.h file properly on 9atom.
>
> https://codereview.appspot.com/82660044/
>
> Please give a try and review this change to
> get it submitted before the Go 1.4 release.

the script itself reminds me of gcc fixincludes.

- erik

Re: [9fans] Python/Mercurial error

[kokamoto]

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

>> https://codereview.appspot.com/82660044/
>>
>> Please give a try and review this change to
>> get it submitted before the Go 1.4 release.

Sorry, David.
I made mistake to copy your patch file to Plan9
system (I've not set abaco yet).

I retried your above patch, and perfectly seamless results
which are included here.

Kenji

[-- Attachment #2: Type: text/plain, Size: 12326 bytes --]

# Building C bootstrap tool.
cmd/dist

# Building compilers and Go bootstrap tool for host, plan9/386.
lib9
libbio
warning: /usr/sys/src/go/src/libbio/bputrune.c:39[/usr/sys/src/go/src/libbio/bputrune.c:1450] result of operation not used
libmach
warning: /usr/sys/src/go/src/libmach/8db.c:207[/usr/sys/src/go/src/libmach/8db.c:2158] unreachable code FUNC
warning: /usr/sys/src/go/src/libmach/sym.c:374[/usr/sys/src/go/src/libmach/sym.c:2198] useless or misleading comparison: UINT < 0
liblink
misc/pprof
cmd/objdump
cmd/prof
cmd/cc
warning: /usr/sys/src/go/src/cmd/cc/y.tab.c:1785[/usr/sys/src/go/src/cmd/cc/y.tab.c:4593] result of operation not used
warning: /usr/sys/src/go/src/cmd/cc/y.tab.c:1785[/usr/sys/src/go/src/cmd/cc/y.tab.c:4593] result of operation not used
warning: /usr/sys/src/go/src/cmd/cc/y.tab.c:1791[/usr/sys/src/go/src/cmd/cc/y.tab.c:4599] result of operation not used
warning: /usr/sys/src/go/src/cmd/cc/y.tab.c:1791[/usr/sys/src/go/src/cmd/cc/y.tab.c:4599] result of operation not used
warning: /usr/sys/src/go/src/cmd/cc/y.tab.c:1788[/usr/sys/src/go/src/cmd/cc/y.tab.c:4596] set and not used: yymsg
warning: /usr/sys/src/go/src/cmd/cc/y.tab.c:1868[/usr/sys/src/go/src/cmd/cc/y.tab.c:4671] set and not used: yytoken
warning: /usr/sys/src/go/src/cmd/cc/y.tab.c:1952[/usr/sys/src/go/src/cmd/cc/y.tab.c:4751] set and not used: yyptr
cmd/gc
warning: /usr/sys/src/go/src/cmd/gc/y.tab.c:2049[/usr/sys/src/go/src/cmd/gc/y.tab.c:5497] useless or misleading comparison: ULONG <= 0xffffffff
warning: /usr/sys/src/go/src/cmd/gc/y.tab.c:2072[/usr/sys/src/go/src/cmd/gc/y.tab.c:5518] useless or misleading comparison: ULONG <= 0xffffffff
warning: /usr/sys/src/go/src/cmd/gc/y.tab.c:2080[/usr/sys/src/go/src/cmd/gc/y.tab.c:5526] useless or misleading comparison: ULONG <= 0xffffffff
warning: /usr/sys/src/go/src/cmd/gc/y.tab.c:2124[/usr/sys/src/go/src/cmd/gc/y.tab.c:5568] result of operation not used
warning: /usr/sys/src/go/src/cmd/gc/y.tab.c:2124[/usr/sys/src/go/src/cmd/gc/y.tab.c:5568] result of operation not used
warning: /usr/sys/src/go/src/cmd/gc/y.tab.c:2127[/usr/sys/src/go/src/cmd/gc/y.tab.c:5571] set and not used: yymsg
warning: /usr/sys/src/go/src/cmd/gc/y.tab.c:2234[/usr/sys/src/go/src/cmd/gc/y.tab.c:5673] set and not used: yytoken
warning: /usr/sys/src/go/src/cmd/gc/y.tab.c:2309[/usr/sys/src/go/src/cmd/gc/y.tab.c:5742] set and not used: yyptr
cmd/8l
cmd/8a
warning: /usr/sys/src/go/src/cmd/8a/y.tab.c:1376[/usr/sys/src/go/src/cmd/8a/y.tab.c:4282] result of operation not used
warning: /usr/sys/src/go/src/cmd/8a/y.tab.c:1376[/usr/sys/src/go/src/cmd/8a/y.tab.c:4282] result of operation not used
warning: /usr/sys/src/go/src/cmd/8a/y.tab.c:1379[/usr/sys/src/go/src/cmd/8a/y.tab.c:4285] set and not used: yymsg
warning: /usr/sys/src/go/src/cmd/8a/y.tab.c:1567[/usr/sys/src/go/src/cmd/8a/y.tab.c:4461] set and not used: yyptr
cmd/8c
cmd/8g
pkg/runtime
pkg/errors
pkg/sync/atomic
pkg/sync
pkg/io
pkg/unicode
pkg/unicode/utf8
pkg/unicode/utf16
pkg/bytes
pkg/math
pkg/strings
pkg/strconv
pkg/bufio
pkg/sort
pkg/container/heap
pkg/encoding/base64
pkg/syscall
pkg/time
pkg/os
pkg/reflect
pkg/fmt
pkg/encoding
pkg/encoding/json
pkg/flag
pkg/path/filepath
pkg/path
pkg/io/ioutil
pkg/log
pkg/regexp/syntax
pkg/regexp
pkg/go/token
pkg/go/scanner
pkg/go/ast
pkg/go/parser
pkg/os/exec
pkg/os/signal
pkg/net/url
pkg/text/template/parse
pkg/text/template
pkg/go/doc
pkg/go/build
cmd/go

# Building packages and commands for plan9/386.
runtime
errors
sync/atomic
sync
io
unicode
unicode/utf8
bytes
bufio
math
strconv
reflect
encoding/binary
syscall
time
os
fmt
debug/dwarf
debug/elf
strings
debug/gosym
debug/macho
debug/pe
sort
flag
log
cmd/addr2line
hash
crypto
crypto/md5
go/token
path/filepath
go/scanner
go/ast
io/ioutil
go/parser
text/tabwriter
go/printer
os/exec
cmd/cgo
go/format
path
cmd/fix
container/heap
encoding
encoding/base64
unicode/utf16
encoding/json
encoding/xml
regexp/syntax
regexp
net/url
text/template/parse
text/template
go/doc
go/build
compress/flate
hash/crc32
compress/gzip
container/list
crypto/subtle
crypto/cipher
crypto/aes
crypto/des
math/rand
math/big
crypto/elliptic
crypto/ecdsa
crypto/hmac
crypto/rand
crypto/rc4
crypto/rsa
crypto/sha1
crypto/sha256
crypto/dsa
encoding/asn1
crypto/x509/pkix
encoding/hex
encoding/pem
net
crypto/x509
crypto/tls
mime
net/textproto
mime/multipart
net/http
os/signal
cmd/go
runtime/pprof
cmd/gofmt
debug/goobj
cmd/link
debug/plan9obj
cmd/nm
cmd/pack
cmd/yacc
archive/tar
archive/zip
compress/bzip2
compress/lzw
hash/adler32
compress/zlib
container/ring
crypto/sha512
database/sql/driver
database/sql
encoding/ascii85
encoding/base32
encoding/csv
encoding/gob
expvar
hash/crc64
hash/fnv
html
html/template
image/color
image
image/color/palette
image/draw
image/gif
image/jpeg
image/png
index/suffixarray
log/syslog
math/cmplx
net/http/cgi
net/http/cookiejar
net/http/fcgi
net/http/httptest
net/http/httputil
net/http/pprof
net/mail
net/rpc
net/rpc/jsonrpc
net/smtp
os/user
runtime/debug
runtime/race
testing
testing/iotest
testing/quick
text/scanner

# Testing packages.
?   	cmd/addr2line	[no test files]
?   	cmd/cgo	[no test files]
ok  	cmd/fix	0.037s
ok  	cmd/go	0.042s
ok  	cmd/gofmt	0.105s
ok  	cmd/link	0.104s
?   	cmd/nm	[no test files]
sys: trap: fault read addr=0xfffffffc pc=0x3a26
PC=0x3a26

goroutine 0 [idle]:
runtime.notesleep(0x1032e614)
	/usr/sys/src/go/src/pkg/runtime/lock_sema.c:166 +0xd6
stopm()
	/usr/sys/src/go/src/pkg/runtime/proc.c:935 +0xcd
findrunnable()
	/usr/sys/src/go/src/pkg/runtime/proc.c:1243 +0x301
schedule()
	/usr/sys/src/go/src/pkg/runtime/proc.c:1326 +0xeb
park0(0x103125a0)
	/usr/sys/src/go/src/pkg/runtime/proc.c:1391 +0xe8
runtime.mcall(0x254a3)
	/usr/sys/src/go/src/pkg/runtime/asm_386.s:190 +0x36

goroutine 16 [chan receive]:
testing.RunTests(0x1838e4, 0x1f6640, 0x5, 0x5, 0x30315201)
	/usr/sys/src/go/src/pkg/testing/testing.go:504 +0x7c6
testing.Main(0x1838e4, 0x1f6640, 0x5, 0x5, 0x1feae0, ...)
	/usr/sys/src/go/src/pkg/testing/testing.go:435 +0x8a
main.main()
	/tmp/go-build125941623/cmd/pack/_test/_testmain.go:55 +0x82

goroutine 19 [finalizer wait]:
runtime.park(0x113d0, 0x1fa144, 0x1f95bc)
	/usr/sys/src/go/src/pkg/runtime/proc.c:1350 +0x80
runtime.parkunlock(0x1fa144, 0x1f95bc)
	/usr/sys/src/go/src/pkg/runtime/proc.c:1366 +0x3b
runfinq()
	/usr/sys/src/go/src/pkg/runtime/mgc0.c:2578 +0xb0
runtime.goexit()
	/usr/sys/src/go/src/pkg/runtime/proc.c:1426

goroutine 25 [runnable]:
syscall.startProcess(0x10357da3, 0x7, 0x10330810, 0x5, 0x6, ...)
	/usr/sys/src/go/src/pkg/syscall/exec_plan9.go:561 +0x12c
syscall.StartProcess(0x10357da3, 0x7, 0x10330810, 0x5, 0x6, ...)
	/usr/sys/src/go/src/pkg/syscall/exec_plan9.go:572 +0x72
os.startProcess(0x10357da3, 0x7, 0x10330810, 0x5, 0x6, ...)
	/usr/sys/src/go/src/pkg/os/exec_plan9.go:33 +0x1e8
os.StartProcess(0x10357da3, 0x7, 0x10330810, 0x5, 0x6, ...)
	/usr/sys/src/go/src/pkg/os/doc.go:24 +0x62
os/exec.(*Cmd).Start(0x10312d20, 0x0, 0x0)
	/usr/sys/src/go/src/pkg/os/exec/exec.go:272 +0x5b4
os/exec.(*Cmd).Run(0x10312d20, 0x0, 0x0)
	/usr/sys/src/go/src/pkg/os/exec/exec.go:234 +0x3a
os/exec.(*Cmd).CombinedOutput(0x10312d20, 0x0, 0x0, 0x0, 0x0, ...)
	/usr/sys/src/go/src/pkg/os/exec/exec.go:364 +0x1ca
cmd/pack.func·005(0x103307e0, 0x5, 0x5, 0x0, 0x0)
	/usr/sys/src/go/src/cmd/pack/pack_test.go:204 +0xf2
cmd/pack.TestHello(0x103663c0)
	/usr/sys/src/go/src/cmd/pack/pack_test.go:221 +0x67e
testing.tRunner(0x103663c0, 0x1f6670)
	/usr/sys/src/go/src/pkg/testing/testing.go:422 +0x87
created by testing.RunTests
	/usr/sys/src/go/src/pkg/testing/testing.go:503 +0x78a

goroutine 28 [syscall]:
syscall.Syscall(0x103e9d18, 0x200, 0x0, 0x0, 0x0, ...)
	/usr/sys/src/go/src/pkg/syscall/asm_plan9_386.s:19 +0x5
syscall.await(0x103e9d18, 0x200, 0x200, 0x104168cc, 0x0, ...)
	/usr/sys/src/go/src/pkg/syscall/zsyscall_plan9_386.go:43 +0x70
syscall.Await(0x10327040, 0x0, 0x0)
	/usr/sys/src/go/src/pkg/syscall/syscall_plan9.go:211 +0xc2
syscall.func·001()
	/usr/sys/src/go/src/pkg/syscall/exec_plan9.go:556 +0x17a
created by syscall.startProcess
	/usr/sys/src/go/src/pkg/syscall/exec_plan9.go:560 +0x103

ax	0x0
bx	0x1032e614
cx	0x1
dx	0x1
di	0x17
si	0x0
bp	0x1fa800
sp	0x103b9f5c
pc	0x3a26
flags	0x10202
cs	0x23
fs	0x1b
gs	0x1b
pack.test 1265: suicide: sys: trap: fault read addr=0xfffffffc pc=0x254b6
FAIL	cmd/pack	0.082s
?   	cmd/yacc	[no test files]
ok  	archive/tar	0.031s
ok  	archive/zip	0.601s
ok  	bufio	0.177s
ok  	bytes	0.220s
ok  	compress/bzip2	0.121s
ok  	compress/flate	1.467s
ok  	compress/gzip	0.421s
ok  	compress/lzw	0.730s
ok  	compress/zlib	1.741s
ok  	container/heap	0.021s
ok  	container/list	0.021s
ok  	container/ring	0.030s
?   	crypto	[no test files]
ok  	crypto/aes	0.054s
ok  	crypto/cipher	0.032s
ok  	crypto/des	0.043s
ok  	crypto/dsa	0.073s
ok  	crypto/ecdsa	0.089s
ok  	crypto/elliptic	0.097s
ok  	crypto/hmac	0.020s
ok  	crypto/md5	0.088s
ok  	crypto/rand	0.078s
ok  	crypto/rc4	0.214s
ok  	crypto/rsa	0.879s
ok  	crypto/sha1	0.021s
ok  	crypto/sha256	0.020s
ok  	crypto/sha512	0.024s
ok  	crypto/subtle	0.032s
ok  	crypto/tls	5.207s
ok  	crypto/x509	6.681s
?   	crypto/x509/pkix	[no test files]
ok  	database/sql	0.182s
ok  	database/sql/driver	0.020s
ok  	debug/dwarf	0.133s
ok  	debug/elf	0.228s
ok  	debug/goobj	0.019s
ok  	debug/gosym	0.020s
ok  	debug/macho	0.243s
ok  	debug/pe	0.227s
ok  	debug/plan9obj	0.079s
?   	encoding	[no test files]
ok  	encoding/ascii85	0.023s
ok  	encoding/asn1	0.028s
ok  	encoding/base32	0.025s
ok  	encoding/base64	0.024s
ok  	encoding/binary	0.027s
ok  	encoding/csv	0.025s
ok  	encoding/gob	0.082s
ok  	encoding/hex	0.021s
ok  	encoding/json	0.281s
ok  	encoding/pem	0.024s
ok  	encoding/xml	0.043s
ok  	errors	0.024s
ok  	expvar	0.035s
ok  	flag	0.021s
ok  	fmt	0.089s
ok  	go/ast	0.034s
ok  	go/build	9.972s
ok  	go/doc	0.254s
ok  	go/format	0.031s
ok  	go/parser	0.062s
ok  	go/printer	0.927s
ok  	go/scanner	0.022s
ok  	go/token	0.061s
?   	hash	[no test files]
ok  	hash/adler32	0.038s
ok  	hash/crc32	0.020s
ok  	hash/crc64	0.020s
ok  	hash/fnv	0.025s
ok  	html	0.022s
ok  	html/template	0.133s
ok  	image	0.924s
ok  	image/color	0.028s
?   	image/color/palette	[no test files]
ok  	image/draw	0.151s
ok  	image/gif	0.227s
ok  	image/jpeg	0.431s
ok  	image/png	0.091s
ok  	index/suffixarray	0.029s
ok  	io	0.037s
ok  	io/ioutil	0.024s
ok  	log	0.029s
?   	log/syslog	[no test files]
ok  	math	0.028s
ok  	math/big	0.540s
ok  	math/cmplx	0.022s
ok  	math/rand	0.572s
ok  	mime	0.027s
ok  	mime/multipart	1.552s
--- FAIL: TestResolveIPAddr (0.00 seconds)
	ipraw_test.go:74: ResolveIPAddr(ip6:ipv6-icmp, ::1) failed: write /net/cs: cs: no match
FAIL
FAIL	net	0.944s
ok  	net/http	8.109s
ok  	net/http/cgi	0.137s
ok  	net/http/cookiejar	0.035s
ok  	net/http/fcgi	0.031s
ok  	net/http/httptest	0.061s
ok  	net/http/httputil	0.180s
?   	net/http/pprof	[no test files]
ok  	net/mail	0.026s
ok  	net/rpc	0.187s
ok  	net/rpc/jsonrpc	0.036s
ok  	net/smtp	0.118s
ok  	net/textproto	0.024s
ok  	net/url	0.029s
ok  	os	3.994s
ok  	os/exec	0.390s
ok  	os/signal	0.017s
ok  	os/user	0.026s
ok  	path	0.027s
ok  	path/filepath	0.990s
ok  	reflect	0.188s
ok  	regexp	0.385s
ok  	regexp/syntax	1.361s
ok  	runtime	89.326s
ok  	runtime/debug	0.108s
ok  	runtime/pprof	0.989s
?   	runtime/race	[no test files]
ok  	sort	0.145s
ok  	strconv	0.774s
ok  	strings	0.203s
ok  	sync	0.147s
ok  	sync/atomic	0.172s
ok  	syscall	0.021s
ok  	testing	2.887s
?   	testing/iotest	[no test files]
ok  	testing/quick	0.071s
ok  	text/scanner	0.026s
ok  	text/tabwriter	0.025s
ok  	text/template	0.076s
ok  	text/template/parse	0.030s
ok  	time	4.077s
ok  	unicode	0.024s
ok  	unicode/utf16	0.023s
ok  	unicode/utf8	0.027s
?   	unsafe	[no test files]
59.66u 17.04s 369.97r 	 go test std -short -timeout ...  # status= 1
all.rc 401: run.rc 1210: time 1216: go 1217: 1

============
go version devel +1afdecdd77c1 Sat Mar 29 17:10:25 2014 -0400 plan9/386

Re: [9fans] Python/Mercurial error

[David du Colombier]

> the script itself reminds me of gcc fixincludes.

This is probably not ideal, but the alternative would be
to split libc.h in three parts: libc.h, fmt.h and utf.h
and only include libc.h in Go (because Go has his own
variants of libfmt and libutf).

--
David du Colombier

Re: [9fans] Python/Mercurial error

[erik quanstrom]

On Thu Apr  3 01:51:59 EDT 2014, 0intro@gmail.com wrote:
> > the script itself reminds me of gcc fixincludes.
>
> This is probably not ideal, but the alternative would be
> to split libc.h in three parts: libc.h, fmt.h and utf.h
> and only include libc.h in Go (because Go has his own
> variants of libfmt and libutf).

why is the alternative to modify plan 9, and why can't they
live with the system fmt/rune routines?

- erik

Re: [9fans] Python/Mercurial error

[David du Colombier]

> Sorry, David.
> I made mistake to copy your patch file to Plan9
> system (I've not set abaco yet).
>
> I retried your above patch, and perfectly seamless results
> which are included here.

I don't think the error you encountered was related to
the patch, since it's only related to a compilation
issue on 9atom. As long as the Go compilation succeed
on 9atom, the patch was successfully applied.

> ?   	cmd/nm	[no test files]
> pack.test 1119: suicide: sys: trap: fault read addr=0xeafffffc
> pc=0x254b6 *** Test killed: ran too long (3m0s).
> FAIL	cmd/pack	180.007s
> ?   	cmd/yacc	[no test files]

It was probably a real error. However, other 9atom
users have not encountered it and it didn't fail
for you the second time you tried, so it would
tend to prove that it doesn't happen every time.

--
David du Colombier

Re: [9fans] Python/Mercurial error

[erik quanstrom]

> > ?   	cmd/nm	[no test files]
> > pack.test 1119: suicide: sys: trap: fault read addr=0xeafffffc
> > pc=0x254b6 *** Test killed: ran too long (3m0s).
> > FAIL	cmd/pack	180.007s
> > ?   	cmd/yacc	[no test files]
>
> It was probably a real error. However, other 9atom
> users have not encountered it and it didn't fail
> for you the second time you tried, so it would
> tend to prove that it doesn't happen every time.

does go make assumptions about where the stack is?

- erik

Re: [9fans] Python/Mercurial error

[Jeff Sickel]

On Apr 3, 2014, at 12:58 AM, erik quanstrom <quanstro@quanstro.net> wrote:
>
> On Thu Apr  3 01:51:59 EDT 2014, 0intro@gmail.com wrote:
>>> the script itself reminds me of gcc fixincludes.
>>
>> This is probably not ideal, but the alternative would be
>> to split libc.h in three parts: libc.h, fmt.h and utf.h
>> and only include libc.h in Go (because Go has his own
>> variants of libfmt and libutf).
>
> why is the alternative to modify plan 9, and why can't they
> live with the system fmt/rune routines?

Go will likely require its own libraries for everything in the
near future.  The Plan 9 variants will have to accept that
as it is just too time consuming to try and keep the headers
clean and still use the original Plan 9 libraries that started
the core Go implementation.

- jas

Re: [9fans] Python/Mercurial error

[David du Colombier]

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

> why is the alternative to modify plan 9, and why can't they
> live with the system fmt/rune routines?

They are incompatible. For example, some Fmt verbs (like %F) does produce
slightly different output. It was an explicit requirement from the Go team
to use their variants of these libraries.

--
David du Colombier

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

Re: [9fans] Python/Mercurial error

[erik quanstrom]

> They are incompatible. For example, some Fmt verbs (like %F) does produce
> slightly different output. It was an explicit requirement from the Go team
> to use their variants of these libraries.

do you see why i think that relationship is upside down?

- erik

Re: [9fans] Python/Mercurial error

[Ramakrishnan Muthukrishnan]

Sorry, late into it again.

David,

I picked the new hg from 9legacy website (2.9.1) and used it to pull
Go source. But I consistently get this error on both Bell Labs plan9
and 9atom on virtualbox.

; hg clone http://code.google.com/p/go
....
...
adding file changes
transaction abort!
failed to truncate 00manifest.i
rollback failed - please run hg recover
abort: invalid arguments
; cd go
; hg recover
no interrupted transaction available
;



--
  Ramakrishnan

Re: [9fans] Python/Mercurial error

[erik quanstrom]

> adding file changes
> transaction abort!
> failed to truncate 00manifest.i
> rollback failed - please run hg recover
> abort: invalid arguments

looks like that error path was never tested.  :-)

- erik

Re: [9fans] Python/Mercurial error

[David du Colombier]

> ; hg clone http://code.google.com/p/go
> ....
> ...
> adding file changes
> transaction abort!
> failed to truncate 00manifest.i
> rollback failed - please run hg recover
> abort: invalid arguments
> ; cd go
> ; hg recover
> no interrupted transaction available
> ;

It looks similar to an issue I encountered occasionally.
I reported it to Jeff Sickel, but we still haven't succeed
to track it down.

--
David du Colombier

Re: [9fans] Python/Mercurial error

[erik quanstrom]

On Thu Apr  3 13:59:36 EDT 2014, 0intro@gmail.com wrote:
> > ; hg clone http://code.google.com/p/go
> > ....
> > ...
> > adding file changes
> > transaction abort!
> > failed to truncate 00manifest.i
> > rollback failed - please run hg recover
> > abort: invalid arguments
> > ; cd go
> > ; hg recover
> > no interrupted transaction available
> > ;
>
> It looks similar to an issue I encountered occasionally.
> I reported it to Jeff Sickel, but we still haven't succeed
> to track it down.

i hope this isn't begging the obvious, but with huge
masses of code, i find it helpful to hunt down the initial
error message and start adding debugging code.

- erik

Re: [9fans] Python/Mercurial error

[Ramakrishnan Muthukrishnan]

On Thu, Apr 3, 2014 at 11:27 PM, David du Colombier <0intro@gmail.com> wrote:
>> ; hg clone http://code.google.com/p/go
>> ....
>> ...
>> adding file changes
>> transaction abort!
>> failed to truncate 00manifest.i
>> rollback failed - please run hg recover
>> abort: invalid arguments
>> ; cd go
>> ; hg recover
>> no interrupted transaction available
>> ;
>
> It looks similar to an issue I encountered occasionally.
> I reported it to Jeff Sickel, but we still haven't succeed
> to track it down.

I tried cloning the go repo multiple times with the new hg and I get
the error *everytime*. :(

--
  Ramakrishnan

Re: [9fans] Python/Mercurial error

[David du Colombier]

> i hope this isn't begging the obvious, but with huge
> masses of code, i find it helpful to hunt down the initial
> error message and start adding debugging code.

I think it's more a matter of spare time and reproducibility ☺.

-- 
David du Colombier

Re: [9fans] Python/Mercurial error

[David du Colombier]

> I tried cloning the go repo multiple times with the new hg and I get
> the error *everytime*. :(

I'm having troubles to reproduce this problem recently.
It seems to depends on your network connection. I suppose
there is an issue somewhere in the networking code.

If that's a problem for you, you can still clone the
repository from Unix, then copy it to Plan 9 and you
can use the other hg commands (like hg pull) from here.
This issue is mostly happening with "clone".

--
David du Colombier

Re: [9fans] Python/Mercurial error

[Ramakrishnan Muthukrishnan]

On Thu, Apr 3, 2014 at 11:53 PM, David du Colombier <0intro@gmail.com> wrote:
>> i hope this isn't begging the obvious, but with huge
>> masses of code, i find it helpful to hunt down the initial
>> error message and start adding debugging code.
>
> I think it's more a matter of spare time and reproducibility ☺.

I could help reproduce the problem and debug it this weekend, if
someone can handhold a bit. I don't know next to nothing about
debugging on a plan9 system but would like to learn. I will try to
read up and see where the error is reported from.

One observation is that on the VirtualBox system, the network
throughput seem to be very very low. The 'hg clone' speeds are ~1/10x
of that while cloning on the GNU/Linux system running natively. So,
perhaps there is something funny going on with the network card. I
could also try on qemu later today.

-- 
  Ramakrishnan

Re: [9fans] Python/Mercurial error

[erik quanstrom]

On Thu Apr  3 21:11:07 EDT 2014, vu3rdd@gmail.com wrote:
> On Thu, Apr 3, 2014 at 11:53 PM, David du Colombier <0intro@gmail.com> wrote:
> >> i hope this isn't begging the obvious, but with huge
> >> masses of code, i find it helpful to hunt down the initial
> >> error message and start adding debugging code.
> >
> > I think it's more a matter of spare time and reproducibility ☺.
> 
> I could help reproduce the problem and debug it this weekend, if
> someone can handhold a bit. I don't know next to nothing about
> debugging on a plan9 system but would like to learn. I will try to
> read up and see where the error is reported from.

i think this is a matter of debugging hg's python, not plan 9.  so
the plan 9 you need to know is the system python libs are in
/sys/lib/python2.7.  :-)

- erik

Re: [9fans] Python/Mercurial error

[Jeff Sickel]

> On Apr 3, 2014, at 1:04 PM, Ramakrishnan Muthukrishnan <vu3rdd@gmail.com> wrote:

> I tried cloning the go repo multiple times with the new hg and I get
> the error *everytime*. :(

What file system are you using?
Have you tried 'hg clone -U'?

There are a few cases with hg where the repository your trying to clone has a file stored in its repo that is longer than a valid path on certain Plan 9 file systems.  This is the case for go, python, and a few other prominent repositories.  In the case of go, getting the repo cloned without the update can work, because it doesn't fail during the file walk that would be invalid during temporary reconstruction if the work area file space.  Then an update to tip later will actually work because it bypasses the garbage file that was replaced|moved in a later commit.

- jas

Re: [9fans] Python/Mercurial error

[Ramakrishnan Muthukrishnan]

On Wed, Apr 2, 2014 at 10:49 AM, David du Colombier <0intro@gmail.com> wrote:
> Two days ago, I've fixed the script mklibc.rc to
> generate the libc_plan9.h file properly on 9atom.
>
> https://codereview.appspot.com/82660044/
>
> Please give a try and review this change to
> get it submitted before the Go 1.4 release.

I got a fresh copy of go from the current hg tip and applied this
patch. I now see some other errors while it builds pkg/math module: I
had not seen these before, so perhaps something new that landed in the
go repo may be responsible for it?

go/src/pkg/math/abs.go:14: internal error: abs ~r1 (type float64)
recorded as live on entry
[...] same error for various other files (acosh.go, asin.go ... )
[...]
go tool dist: FAILED: ...

It will be great if one of the "distributions" like 9atom ship a
version of various tools like hg/python/go along with it.

--
  Ramakrishnan

Re: [9fans] Python/Mercurial error

[David du Colombier]

> I got a fresh copy of go from the current hg tip and applied this
> patch. I now see some other errors while it builds pkg/math module: I
> had not seen these before, so perhaps something new that landed in the
> go repo may be responsible for it?
>
> go/src/pkg/math/abs.go:14: internal error: abs ~r1 (type float64)
> recorded as live on entry
> [...] same error for various other files (acosh.go, asin.go ... )
> [...]
> go tool dist: FAILED: ...

A build issue has been introduced in Go tip yesterday. We're working on it.

Please checkout 5943000dd5ba in the meantime.

--
David du Colombier

Re: [9fans] Python/Mercurial error

[Ramakrishnan Muthukrishnan]

Sorry for the late response, Jeff. Apologies. I just booted up virtualbox.

On Fri, Apr 4, 2014 at 11:09 AM, Jeff Sickel <jas@corpus-callosum.com> wrote:
>
>
>> On Apr 3, 2014, at 1:04 PM, Ramakrishnan Muthukrishnan <vu3rdd@gmail.com> wrote:
>
>> I tried cloning the go repo multiple times with the new hg and I get
>> the error *everytime*. :(
>
> What file system are you using?

I don't know. How do I find out? Is there an equiv of the Unix's fstab
somewhere? I looked a bit but couldn't find it. Still finding my way
around the system.

> Have you tried 'hg clone -U'?

Yes, that gave me same error message.

> There are a few cases with hg where the repository your trying to clone has a file stored in its repo that is longer than a valid path on certain Plan 9 file systems.  This is the case for go, python, and a few other prominent repositories.  In the case of go, getting the repo cloned without the update can work, because it doesn't fail during the file walk that would be invalid during temporary reconstruction if the work area file space.  Then an update to tip later will actually work because it bypasses the garbage file that was replaced|moved in a later commit.

Okay, I will clone it on another Unix system and copy it over into
plan9 for the time being.

Thanks.

-- 
  Ramakrishnan