On Sat, Feb 13, 2016 at 01:35:38AM +0100, Dmitrij D. Czarkoff wrote:
> Antoine Jacoutot said:
> > unset GOPATH; export 
> > GOPATH="/exopi-obj/pobj/xlsx2csv-20150225/go:/usr/local/go-pkg"; go install 
> > -x github.com/tealeg/xlsx2csv
> > WORK=/tmp/go-build671266662
> > mkdir -p $WORK/github.com/tealeg/xlsx/_obj/
> > mkdir -p $WORK/github.com/tealeg/
> > cd /usr/local/go-pkg/src/github.com/tealeg/xlsx
> > /usr/local/go/pkg/tool/openbsd_amd64/compile -o 
> > $WORK/github.com/tealeg/xlsx.a -trimpath $WORK -p github.com/tealeg/xlsx 
> > -complete -buildid 90518c0c038b7176e8b01fb5b752aef4df0eb80d -D 
> > _/usr/local/go-pkg/src/github.com/tealeg/xlsx -I $WORK -pack ./cell.go 
> > ./col.go ./date.go ./doc.go ./file.go ./hsl.go ./lib.go ./reftable.go 
> > ./row.go ./sheet.go ./style.go ./templates.go ./theme.go ./write.go 
> > ./xmlContentTypes.go ./xmlSharedStrings.go ./xmlStyle.go ./xmlTheme.go 
> > ./xmlWorkbook.go ./xmlWorksheet.go
> 
> For some reason go tries to rebuild github.com/tealeg/xlsx package
> (textproc/go-xlsx).  This should never happen, and it indeed never
> happens on my machine.  Interestingly, similar thing happened before
> (http://article.gmane.org/gmane.os.openbsd.ports/77273), and I couldn't
> reproduce it back then either.  Maybe something uncommon in your
> environment?

$ cat /etc/mk.conf                                                              
                                                                                
              
BSDSRCDIR=/exopi-cvs/src
XSRCDIR=/exopi-cvs/xenocara
PORTSDIR=/exopi-cvs/ports
BSDOBJDIR=/exopi-obj/obj
XOBJDIR=/exopi-obj/xobj
WRKOBJDIR=/exopi-obj/pobj
MASTER_SITE_OPENBSD=http://ftp.fr.openbsd.org/pub/OpenBSD/distfiles/
.include "${PORTSDIR}/infrastructure/templates/mk.conf.template"

dpb host file:
COLOR=1
DEFAULT build_user=_pbuild stuck=10800
FETCH_USER=_pfetch
LOG_USER=exopi
STARTUP=/home/exopi/bin/exo-cleanhost
localhost
exopi-1
exopi-2
exopi-3
exopi-4
exopi-5
exopi-6
exopi-7

"/exopi-cvs" is NFS mounted

I wouldn't call this particularly uncommon...
You said that "This should never happen" -- ok but why, because it does; so 
what would trigger a rebuild like this? I don't know the first thing about the 
go build system.
Once we know that, then we can start hunting.

-- 
Antoine

Reply via email to