Cannot compile golang from src on RaspberryPi (Model B) running Raspbmc

[gopherbot]

by abonello00:

I'm having problems compiling golang v1.1 from src on a Rasberry Pi Model B running a
recent install of Raspbmc. The build fails here:

.
.
.
# Building packages and commands for linux/arm.
runtime
errors
sync/atomic
sync
io
unicode
unicode/utf8
bytes
bufio
math
syscall
# syscall
pkg/syscall/env_unix.go:72: undefined: EINVAL
pkg/syscall/env_unix.go:76: undefined: EINVAL
pkg/syscall/env_unix.go:81: undefined: EINVAL
pkg/syscall/exec_linux.go:72: undefined: PR_SET_PDEATHSIG
pkg/syscall/exec_linux.go:92: undefined: PTRACE_TRACEME
pkg/syscall/exec_linux.go:158: undefined: F_SETFD
pkg/syscall/exec_linux.go:158: undefined: FD_CLOEXEC
pkg/syscall/exec_linux.go:168: undefined: F_SETFD
pkg/syscall/lsf_linux.go:40: undefined: IFNAMSIZ
pkg/syscall/lsf_linux.go:40: invalid array bound IFNAMSIZ
pkg/syscall/exec_linux.go:168: too many errors


I ran an explicit go_bootstrap command, and the offending line seems to be the one
below. The EINVAL const is defined in zerrors_linux_arm.go, but that .go file isn't
being included in the compile command below. I've attached the full output of the
go_bootstrap command.

$ ../pkg/tool/linux_arm/go_bootstrap install -a -x std
.
.
.
/mnt/skittle/linux.rpi/go/pkg/tool/linux_arm/5g -o $WORK/syscall/_obj/_go_.5 -p syscall
-D _/mnt/skittle/linux.rpi/go/src/pkg/syscall -I $WORK ./env_unix.go ./exec_linux.go
./exec_unix.go ./lsf_linux.go ./netlink_linux.go ./race0.go ./sockcmsg_linux.go
./sockcmsg_unix.go ./str.go ./syscall.go ./syscall_linux.go ./syscall_linux_arm.go
./syscall_unix.go ./zsyscall_linux_arm.go ./zsysnum_linux_arm.go ./ztypes_linux_arm.go

Attachments:

1. go_bootstrap_output.txt (44873 bytes)

[davecheney]

Comment 1:

This is on me to confirm this breakage.

Owner changed to @davecheney.

Status changed to Accepted.

[minux]

Comment 2:

if the syscall package failed to compile, how could go_bootstrap be built?

[gopherbot]

Comment 3 by abonello00:

I'm not too familiar with the sequence of steps run by make.bash, but after letting it
run its course (and failing in compilation of pkg/syscall as per above), a go_bootstrap
binary is indeed getting left at:
go/pkg/tool/linux_arm/go_bootstrap

[davecheney]

Comment 4:

Hello,
I have just completed a build of go1.1.1 without incident on a raspbmc install. I don't
know which version, it auto updated itself to whatever it felt was a good choice.
Would you be able to give as much detail about your login environment as possible and/or
try the build again with a new user agent and/or new install?

Labels changed: added priority-later, removed priority-triage.

Status changed to Started.

[gopherbot]

Comment 5 by abonello00:

Hi Dave
Thanks for trying to reproduce this. Your report of a clean compile on Raspbmc convinced
me that there's something different about my setup causing the compile error.
I tracked it down: I was building go/ on a a cifs-mounted drive living on another
machine. That drive has an NTFS filesystem, ie. fuseblk on cifs.
When I untarred the go/ 1.1.1 src directly onto the Raspberry Pi's SD card filesystem,
it compiled without problems first time. I assume that there's some file permissions
problem on the cifs drive which is causing a certain part of the go compile to
misbehave. Maybe you can shed some light on that?
Thanks for your help in narrowing this down. Had me foxed for a while.
Andrew.

[minux]

Comment 6:

i don't know if cifs could be the problem, have you checked the permission of
src/pkg/syscall/zerrors_linux_arm.go in your original cifs-backed mount?
as i said earlier, if cmd/dist could build syscall package and then build go_bootstrap
successfully, i doubt that file has wrong permission or unreadable.
perhaps something changes that file during the build process, i don't know.
let's close this issue as retracted, feel free to comment (and reopen it) if you have
more discoveries.

Status changed to Retracted.