You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Trying to compile Go 2 from dev.go2go branch as described in the installation guide.
time CGO_ENABLED=0 ./all.bash
Output: 852.37s user 738.07s system 244% cpu 10:51.15 total
Until the mime/quotedprintable package, the overall compiling speed is really fast. It takes almost a few minutes to get to this stage. But when compile step gets here, laptop's fans start working hard at least for 5 minutes. Then the fans stop immediately and start waiting for another 5 minutes, in order to compile next package.
P.S: With ./run.bash --no-rebuild, it still acts same way.
What did you expect to see?
I'm not so sure whether it was this way before. I'm trying to compile on MacBook Pro. (2.6GHz 6-core 9th i7, 16GB)
What did you see instead?
Is it normal for the compiler to behave this way?
The text was updated successfully, but these errors were encountered:
Unlike many projects, the Go project does not use GitHub Issues for general discussion or asking questions. GitHub Issues are used for tracking bugs and proposals only.
What version of Go are you using (
go version
)?What operating system and processor architecture are you using (
go env
)?go env
OutputWhat did you do?
Trying to compile Go 2 from
dev.go2go
branch as described in the installation guide.time CGO_ENABLED=0 ./all.bash
Output:
852.37s user 738.07s system 244% cpu 10:51.15 total
Until the
mime/quotedprintable
package, the overall compiling speed is really fast. It takes almost a few minutes to get to this stage. But when compile step gets here, laptop's fans start working hard at least for 5 minutes. Then the fans stop immediately and start waiting for another 5 minutes, in order to compile next package.P.S: With
./run.bash --no-rebuild
, it still acts same way.What did you expect to see?
I'm not so sure whether it was this way before. I'm trying to compile on MacBook Pro. (2.6GHz 6-core 9th i7, 16GB)
What did you see instead?
Is it normal for the compiler to behave this way?
The text was updated successfully, but these errors were encountered: