Actually, the problem happens also without c-archive. I've put out a repro repo at: https://github.com/steeve/rules_go_ios_arm
You'll need to run this on macOS (because iOS...). On Monday, August 27, 2018 at 4:37:37 PM UTC+2, Steeve Morin wrote: > > Hey folks, > > I'm trying to build a project with Bazel on with buildmode=c-archive, and > I'm running into the following issue on ios_arm and Go 1.11 only: > > sync.(*Map).Load: relocation target sync/atomic.(*Value).Load not defined > sync.(*Map).Store: relocation target sync/atomic.(*Value).Load not defined > sync.(*Map).LoadOrStore: relocation target sync/atomic.(*Value).Load not > defined > sync.(*Map).dirtyLocked: relocation target sync/atomic.(*Value).Load not > defined > internal/testlog.Logger: relocation target sync/atomic.(*Value).Load not > defined > > Go 1.10 works fine. > > Now I know this is probably something that rules_go is doing wrong, > because gomobile is working as expected. > That said, I am not sure where to look on how to pinpoint the issue, so I > would gladly appreciate pointers. > > The revelant rules_go issue is at: > https://github.com/bazelbuild/rules_go/issues/1693#issuecomment-416081365 > > There was a similar problem with ios_386 which was solved by not building > the stdlib with -shared. > > Thanks! > -- 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.
