Slackware - ARMThis forum is for the discussion of Slackware ARM.
Notices
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
I'm not a go expert, just trying to build some other software which uses go. On both 14.2 and current, running a simple go example pegs one CPU at 100% and does not return (even after hours of running).
Example
Code:
$ cat test.go
package main
import (
"os"
)
func main() {
os.Exit(0)
}
$ /usr/bin/go run test.go
This returns immediately on x86/x86_64, but has the problem described above on arm. Has anyone else noticed this?
"go" has been broken since its inclusion. I have no idea what is wrong with it. If you find out, let me know!
I've looked at this a few times and looked at Debian and Fedora for patches but there were none that had any relation to "go", so perhaps the problem is elsewhere.
I'll confirm it's broken, in both SMP and UP, on ARM but not on x86. "go do anything" even fails to parse. The failure is very early: the standard libpath libraries load, then it deadlocks in an infinite loop.
I'll confirm it's broken, in both SMP and UP, on ARM but not on x86. "go do anything" even fails to parse. The failure is very early: the standard libpath libraries load, then it deadlocks in an infinite loop.
I've been experimenting with gcc-go and now I get something more useful.
Does the test code actually work properly elsewhere?
Code:
root@zippy:~/ac/source/d/gcc/test-code# cat test-go.sh
# https://www.linuxquestions.org/questions/slackware-arm-108/go-pegs-cpu-does-not-return-gcc-go-4175633577/
cat << 'EOF' > /tmp/test.go
package main
import (
"os"
)
func main() {
os.Exit(0)
}
EOF
go run /tmp/test.go
root@zippy:~/ac/source/d/gcc/test-code# sh test-go.sh
# command-line-arguments
/tmp/go-build588487404/b001/_buildid.s: Assembler messages:
/tmp/go-build588487404/b001/_buildid.s:8: Error: junk at end of line, first unrecognized character is `,'
/tmp/go-build588487404/b001/_buildid.s:9: Error: junk at end of line, first unrecognized character is `,'
root@zippy:~/ac/source/d/gcc/test-code#
since this thread is about gcc-go.... after last upgrade-all
.
.
No such file 'gcc-go-8.2.0-arm-2.txz.asc'.
ERROR - Package not installed! md5sum error!
.
.
Try upgrading to gcc-go version 9. It's back in the main tree and seems to work.
14.2 won't get a fix though as I've no idea what the problem was - it's just started working with gcc-9.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.