[9fans] Plan 9 port of the Go toolchain

2011-04-11 Thread Lucio De Re
I have tweaked the Plan 9 native ar.h to allow for manual adjustment around the different needs of Go and native Plan 9 toolchains, so now: #ifndef SARNAME #define SARNAME 16 #endif SARNAME can be predefined to the 64 that Go prefers. Unfortunately, it's a short term

Re: [9fans] Plan 9 port of the Go toolchain

2011-04-11 Thread Lucio De Re
PS: I still can't link an executable with the version of 8l from the Go toolchain that I built under Plan 9, but I'm hoping to get there soon. It's of some consolation to me that I see exactly the same results under Ubuntu, so that particular problem isn't in the 8l executable created for Plan

Re: [9fans] Plan 9 port of the Go toolchain

2011-04-11 Thread Lucio De Re
PS: I still can't link an executable with the version of 8l from the Go toolchain that I built under Plan 9, but I'm hoping to get there soon. It's of some consolation to me that I see exactly the same results under Ubuntu, so that particular problem isn't in the 8l executable created for

Re: [9fans] Plan 9 port of the Go toolchain

2011-04-09 Thread Russ Cox
.../src/cmd/8a/asm.c, around line #900:                /* This null SHdr must appear before all others */                sh = newElfShdr(elfstr[ElfStrEmpty]); My guess is that this needs to be followed by an instruction to write out the header, which in fact does not take place. The code

[9fans] Plan 9 port of the Go toolchain

2011-04-08 Thread Lucio De Re
.../src/cmd/8a/asm.c, around line #900: /* This null SHdr must appear before all others */ sh = newElfShdr(elfstr[ElfStrEmpty]); My guess is that this needs to be followed by an instruction to write out the header, which in fact does not take place. I will not be