mirror of
https://github.com/golang/go
synced 2024-09-29 14:24:32 -06:00
dfbbe06a20
cmd/go links mingwex and mingw32 libraries to every package it builds. This breaks when 2 different packages call same gcc standard library function pow. gcc linker appends pow implementation to the compiled package, and names that function "pow". But when these 2 compiled packages are linked together into the final executable, linker complains, because it finds two "pow" functions with the same name. This CL stops linking of mingwex and mingw32 during package build - that leaves pow function reference unresolved. pow reference gets resolved as final executable is built, by having both internal and external linker use mingwex and mingw32 libraries. Fixes #8756 Change-Id: I50ddc79529ea5463c67118d668488345ecf069bc Reviewed-on: https://go-review.googlesource.com/26670 Run-TryBot: Alex Brainman <alex.brainman@gmail.com> TryBot-Result: Gobot Gobot <gobot@golang.org> Reviewed-by: Ian Lance Taylor <iant@golang.org>
18 lines
171 B
Go
18 lines
171 B
Go
package cgotest
|
|
|
|
/*
|
|
#cgo LDFLAGS: -lm
|
|
#include <math.h>
|
|
*/
|
|
import "C"
|
|
import (
|
|
"testing"
|
|
|
|
"./issue8756"
|
|
)
|
|
|
|
func test8756(t *testing.T) {
|
|
issue8756.Pow()
|
|
C.pow(1, 2)
|
|
}
|