Is that a typo? I got an error. http://tip.golang.org/doc/go1.1.html worked.
--
You received this message because you are subscribed to the Google Groups "golang-nuts" group.
To unsubscribe from this group and stop receiving emails from it, send an email to golang-nuts...@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.
Hooray I didn't break everything!
Congratulations on the beta, Go team. This is really exciting.
How about go install? remember go build and go run will do the whole process from scratch every time
$ uname -aDarwin Davids-MacBook-Air.local 11.4.2 Darwin Kernel Version 11.4.2: Thu Aug 23 16:25:48 PDT 2012; root:xnu-1699.32.7~1/RELEASE_X86_64 x86_64
go build command-line-arguments: signal: illegal instruction
Hi Go nuts,
We have just released go1.1beta1, a test version of Go 1.1 cut from the default branch at revision 267bb9854177.
This is not a release candidate: We are still finalizing some details and tracking down a couple more bugs, but it should be ready for almost any purpose and there will be no significant changes other than bug fixes before the release. If you want to try out how Go 1.1 works for you, this is a way to get started early.
Please help us by testing your Go programs with the new tool chain and libraries, and report any problems using the issue tracker:
http://golang.org/issue/new
You can download binary and source distributions from the usual place:
https://code.google.com/p/go/downloads/list?q=go1.1beta1
wget http://go.googlecode.com/files/go1.1beta1.linux-amd64.tar.gzMaybe the problem is about my cloud host, but I am not sure. Anyone got the same problem?
tar xvzf go1.1beta1.linux-amd64.tar.gz
./go/bin/go
runtime: panic before malloc heap initialized
fatal error: runtime: cannot allocate heap metadata
To find out what has changed, read the release notes for Go 1.1:
http://tip.golang.org/doc/go1.1html
Documentation for Go 1.1 is available at http://tip.golang.org/
Thanks,
Andrew
If you are running Go, or pretty much anything, you'll want OVZ that uses vSwap. Even on a 64MB OVZ using vSwap I was able to run many Go apps. I also found rsync didn't run out of ram, when a 256MB with burst 512 vps would.
Therefore, when buying OZ vpses, always ask for vSwap. All of my hosts let me have vSwap for no extra charge.
Cheers.
The problem is some isolation containers have broken virtual memory accounting. Virtual memory is supposed to be (nearly) free; I'm amazed OpenVZ is still broken.
There are plenty of cheap VPSs that use tech with non-broken virtual memory accounting, for example KVM, Xen, LXC. One example I use for personal Go stuff: https://www.digitalocean.com/pricing
For the build, http://tip.golang.org/ incorrectly displays: "Build version devel +0a3866d6cc6b Mon Sep 24 20:08:05 2012 -0400."
Go runtime reserves 256MB of virtual memory on startup, check ulimit -v.
root@AY130304222943607e28:~# ulimit -v
unlimited
Sanity check, am not seeing mention in the release notes of the change
to reflect to be able to go into anonymous fields of a struct, so that
encoding/json and friends can show fields from embedded types?
The downloads at the link at the top of the thread are now listed as depricated. I assume it is better to use the go1.1beta at https://code.google.com/p/go/downloads/list ?
--