Skip site navigation (1)Skip section navigation (2)
Date:      Mon, 31 Aug 2015 10:43:19 -0400
From:      Vick Khera <vivek@khera.org>
To:        FreeBSD Ports List <ports@freebsd.org>
Subject:   unable to boostrap go
Message-ID:  <CALd%2BdcfyxHBuQ9=_E-rj0-aERUK1QcYNpTt0=jmdg%2BG3-VZkag@mail.gmail.com>

next in thread | raw e-mail | index | archive | help
I build my own customized packages using poudriere. Lately (roughy about
when go changed from 1.4 to 1.5) it cannot build the go 1.4.2 bootstrap. It
fails with a bus error. This also is roughly about the time I upgraded my
poudriere server from 10.1 to 10.2.

Is anyone observing this?

Any hints on how to debug it? The poudriere build log ends with this:

===>  Building for go14-1.4.2
cd /var/tmp/usr/ports/lang/go14/work/go/src &&  CC=cc
 GOROOT=/var/tmp/usr/ports/lang/go14/work/go GOROOT_FINAL=/usr/local/go14
 GOBIN= GOARCH=amd64 GOOS=freebsd  /bin/sh make.bash
# Building C bootstrap tool.
cmd/dist
-t: not found
gcc: not found
-t: not found

# Building compilers and Go bootstrap tool for host, freebsd/amd64.
lib9
libbio
liblink
 ....
text/template
go/doc
go/build
cmd/go
Bus error (core dumped)
*** Error code 138

Stop.
make: stopped in /usr/ports/lang/go14
====>> Cleaning up wrkdir
===>  Cleaning for go14-1.4.2
build of lang/go14 ended at Mon Aug 31 10:05:06 EDT 2015
build time: 00:00:14
!!! build failure encountered !!!


In my system log there is this:

Aug 31 10:05:06 lorax kernel: pid 98256 (go_bootstrap), uid 0: exited on
signal 10 (core dumped)

I found a PR relating to the "-t not found" error, but nothing about a full
on core dump. I really do not think this is hardware failure because it
only happens running the go bootstrap and nothing else.



Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?CALd%2BdcfyxHBuQ9=_E-rj0-aERUK1QcYNpTt0=jmdg%2BG3-VZkag>