It works here. Sorry
At the critical moment, mine prints this, what does yours print?
Code:
# ../test/bench/go1
ok _/tmp/SBo/package-google-go-lang/usr/lib/go/test/bench/go1 5.693s
# ../test
real 2m20.518s
user 3m56.910s
sys 0m35.483s
# Checking API compatibility.
Go version is "go1.2", ignoring -next /tmp/SBo/package-google-go-lang/usr/lib/go/api/next.txt
real 0m18.399s
user 0m13.210s
sys 0m1.102s
ALL TESTS PASSED
---
Installed Go for linux/386 in /tmp/SBo/package-google-go-lang/usr/lib/go
Installed commands in /tmp/SBo/package-google-go-lang/usr/bin
The binaries expect /tmp/SBo/package-google-go-lang/usr/lib/go to be copied or moved to /usr/lib/go
Slackware package maker, version 3.14159.
Do you get "ALL TESTS PASSED"? I guess that one (or more) of the tests is failing on your system.
In my personal experience, there are two reasons for a failing test in a SlackBuild. (1) the original developers wrote a test that doesn't work properly, usually for something like locking in a multiprocessor scenario, because there are race conditions in the test that the developers never found, because developers always have much better hardware than I have, or only test their own tests in a VM, or gave the job of writing tests to the most junior developer. (2) one of my memory sticks is starting to go bad.
It gets worse when the SlackBuild (quite reasonably) assumes that the build and tests won't just return an error status without printing an obvious error message. But you really should look closely at the output of the tests. Everything should say "ok" or "?" or "PASS", like this:
Code:
ok unicode/utf16 0.004s
ok unicode/utf8 0.008s
? unsafe [no test files]
real 2m27.288s
user 4m8.284s
sys 0m29.468s
# GOMAXPROCS=2 runtime -cpu=1,2,4
ok runtime 34.918s
# sync -cpu=10
ok sync 0.061s
# ../misc/cgo/stdio
# ../misc/cgo/life
# ../misc/cgo/test
PASS
ok _/tmp/SBo/package-google-go-lang/usr/lib/go/misc/cgo/test 1.181s
PASS
If there's a problem with the tests, and you are
*highly* confident that your system is good, you can remove the 'set -e' line from the SlackBuild.
If there's
not a problem with the tests, then the other possibility is something wrong is happening with the scripts in go/src (all.bash, run.bash etc). There is a comment from Robby in the SlackBuild that says "unset BASH_ENV # Not sure why, but this causes run.bash to fail --rworkman", so you could try unsetting as many environment variables as possible before you run the SlackBuild, on the theory that those scripts may contain more FAIL of the same kind...
Update: Robby applied the BASH_ENV fix I just described on January 30th. Have you got the latest SlackBuild? If not, you should
