New issue
Advanced search Search tips

Issue 645607 link

Starred by 1 user

Issue metadata

Status: WontFix
Owner:
Closed: May 2018
Cc:
EstimatedDays: ----
NextAction: ----
OS: ----
Pri: 3
Type: Bug



Sign in to add a comment

GOOS=android go build is not determinisitc

Project Member Reported by bpastene@chromium.org, Sep 9 2016

Issue description

Every build of GOOS=android cipd packages at https://build.chromium.org/p/chromium.infra/builders/infra-continuous-precise-64 creates new binaries, even though the sources don't change.

(Is the culprit GOOS=android or GOARCH=arm? Or a combination of both?)
 
I've investigates this, there are two issues:

1. Linker injects unique build-id section into each build. This can be disabled via LDFLAGS and --build-id=none. Google "ld build-id" for more info.

2. More fatal flaw: cgo generates some temp source files in /tmp/..., and their names end up in debug info section of the executable. I couldn't find a way to override this.

I think the main suspect here is cgo that is indirectly used when compiling with GOOS=android.
Status: WontFix (was: Assigned)
I think I recall turning off continuous GOOS=android building on the infra waterfall. So this doesn't really need to get fixed anymore.

Sign in to add a comment