--- Comment #16 from Matthew Miller <mattdm(a)redhat.com> ---
Soooooo, this means that:
1. Unsetting CC at the top of the %check file should work
2. This is probably the right thing to do, because we're not using a wrapper at
unsetting CC didn't work. I had to set CC to /usr/bin/gcc to make it work.
That's confusing (and why I jumped through the hoops above). Why's that? Uh oh:
$ grep mygcc . -r
Binary file ./bin/go matches
./src/cmd/go/zdefaultcc.go:const defaultCC =
./src/cmd/cgo/zdefaultcc.go:const defaultCC =
Binary file ./pkg/tool/linux_amd64/cgo matches
We've got the path to the gcc wrapper in the build tree built into the whole
thing -- looks like golang 1.2 wants to keep using the wrapper it was built
with. That seems logical, but raises some... interesting questions.
a) Should all go programs built by the go compiler use our RPM flags? (That is,
should we _ship_ the mygcc wrapper?)
b) If so, might that introduce horrible bugs?
c) If not, should we seek an exception for building golang itself?
You are receiving this mail because:
You are on the CC list for the bug.