Different SHA when building in Vagrant compared to release

mantl / consul-cli

Command line interface to Consul HTTP API

Apache License 2.0

251 stars 67 forks source link

Different SHA when building in Vagrant compared to release #12

Closed chrismwendt closed 8 years ago

chrismwendt commented 8 years ago

After spinning up the 64bit vagrant box and building consul-cli, I got a different SHA from the linux_amd64 release.

Here are the commands that I ran after SSHing into the 64bit vagrant box:

$ sudo bash --login
$ cd /opt/gopath/src/github.com/CiscoCloud/consul-cli
$ make
...
$ sha1sum bin/consul-cli
698c102a4873916571faf52317106287dbf46c5b  bin/consul-cli

I also tried make package with just -osarch="linux/amd64", but the SHA was still different.

ChrisAubuchon commented 8 years ago

The release isn't built with Vagrant. I cross-compile using make package to build the releases.

chrismwendt commented 8 years ago

@ChrisAubuchon Which version of go do you use when running make package?

ChrisAubuchon commented 8 years ago

go version go1.4.1 darwin/amd64

chrismwendt commented 8 years ago

Thanks, the go version was the issue.