On Sun, Jul 13, 2025 at 9:06 AM Qingwei Li <qingweili2...@gmail.com> wrote:
> I notice that in cmd/internal/telemetry/counter/, there are counter.go and > counter_bootstrap.go. They are different in the build tags. For counter.go, > the build tag is "//go:build !cmd_go_bootstrap && !compiler_bootstrap". For > counter_bootstrap.go, it is "//go:build cmd_go_bootstrap || > compiler_bootstrap". counter_bootstrap.go does not import > golang.org/x/telemetry/counter while counter.go does. > > After generate project in pkg/bootstrap/src/bootstrap directory, the > command `GOROOT_BOOTSTRAP/bin/go install -tags="math_big_pure_go > compiler_bootstrap purego" bootstrap/cmd/...` is executed. So to build > toolchain1, actually counter_bootstrap.go is used and no vendor packages > are imported. > Thanks, I missed that. Since the bootstrap process works, and vendored packages are used in stages 2 and 3, what is the advantage of supporting vendored packages in stage 1? Ian -- 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. To view this discussion visit https://groups.google.com/d/msgid/golang-nuts/CAOyqgcVjy_FawhFbJ-wZi6uniW5ffed%3DDj77FBMm3etY5zJNWg%40mail.gmail.com.
