On ArchLinux with a previously gcc built go binary in go1.7rc5: Linux blah 4.6.4-1-ARCH #1 SMP PREEMPT Mon Jul 11 19:12:32 CEST 2016 x86_64 GNU/Linux with the latest: llvm llvm-libs lldb clang clang-tools-extra go env GOARCH="amd64" GOBIN="" GOEXE="" GOHOSTARCH="amd64" GOHOSTOS="linux" GOOS="linux" GOPATH="/root/SQstuff/Code" GORACE="" GOROOT="/root/SQstuff/go1.7rc5" GOTOOLDIR="/root/SQstuff/go1.7rc5/pkg/tool/linux_amd64" CC="gcc" GOGCCFLAGS="-fPIC -m64 -pthread -fmessage-length=0 -fdebug-prefix-map=/tmp/go-build292116724=/tmp/go-build -gno-record-gcc-switches" CXX="g++" CGO_ENABLED="1"
THEN DOING THIS WITH go1.7rc6: CC=/usr/bin/clang GOROOT_BOOTSTRAP=/root/SQstuff/go1.7rc5 ./make.bash It compiles and builds ok. I needed that CC in there because it was confused as to what CC it should be using since I had both gcc and clang installed on my box. On Wednesday, August 10, 2016 at 1:07:50 PM UTC-4, Ian Lance Taylor wrote: > > On Wed, Aug 10, 2016 at 7:00 AM, David Marceau > <uticdmar...@gmail.com <javascript:>> wrote: > > when I install from sources straight from git checkout go1.7rc6 > > go1.7rc6 FAILS on Asus Z97-A-USB31 motherboard with intel i5-4590, > > "../misc/cgo/testsanitizers" > > it core dumps and doesn't give me the success message to start using it > as > > the previous go1.7rc[1-4] did. > > signal: segmentation fault (core dumped) > > FAIL: msan > > FAIL: msan2 > > FAIL: msan3 > > FAIL: msan4 > > ... FAILED > > Could be https://golang.org/issue/16636, which boils down to: clang > -fsanitize=memory doesn't work on some systems. This almost certainly > has nothing to do with the motherboard or processor, but more likely > has something to do with the kernel version and the clang version. > > Ian > -- 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+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
