Comment 5 for bug 1289067

This afternoon I confirmed that even with the latest cmd/go from the upstream trunk this error still occurs, and still occurs on all platforms, even amd64, not just gccgo only platforms.

The underlying cause is duplicate symbols being present, essentially the package under test is compiled twice, once normally, once with the test runner, then the linker tries to mash it all together.

I'm trying to distil a smaller test case for the upstream bug report