Bug 657548 – app-admin/vault-0.10.2: ignore or incorrectly interpret MAKEOPTS

• Status: CONFIRMED
• Product: Gentoo Linux

[Description Toralf Förster 2018-06-07 16:57:13 UTC]

pstree attached

[Comment 1 Toralf Förster 2018-06-07 16:57:42 UTC]

Created attachment 535220 [details]
23.20180607-004625

pstree

[Comment 2 Zac Medico 2024-08-03 06:22:23 UTC]

I tested vault-1.16.1 with MAKEOPTS=-j1 just now, and it created one compile process per core:

> \_ bash /usr/lib/portage/python3.12/ebuild-helpers/emake bin
>     \_ make -j1 bin
>         \_ /bin/sh -c GOARCH= GOOS= go generate $(go list ./... | grep -v vendor/ )
>             \_ go generate github.com/hashicorp/vault github.com/hashicorp/vault/audit github.com/hashicor
>                 \_ go run github.com/hashicorp/vault/tools/stubmaker
>                     \_ /var/tmp/portage/app-admin/vault-1.16.1/temp/go-build3351222282/b001/exe/stubmaker
>                         \_ go list -tags=enterprise -e -json=Name,ImportPath,Error,Dir,GoFiles,IgnoredGoFi
>                             \_ /usr/lib/go/pkg/tool/linux_amd64/compile -o /var/tmp/portage/app-admin/vaul
>                             \_ /usr/lib/go/pkg/tool/linux_amd64/compile -o /var/tmp/portage/app-admin/vaul
>                             \_ /usr/lib/go/pkg/tool/linux_amd64/compile -o /var/tmp/portage/app-admin/vaul
>                             \_ /usr/lib/go/pkg/tool/linux_amd64/compile -o /var/tmp/portage/app-admin/vaul
>                             \_ /usr/lib/go/pkg/tool/linux_amd64/compile -o /var/tmp/portage/app-admin/vaul
>                             \_ /usr/lib/go/pkg/tool/linux_amd64/compile -o /var/tmp/portage/app-admin/vaul
>                             \_ /usr/lib/go/pkg/tool/linux_amd64/compile -o /var/tmp/portage/app-admin/vaul
>                             \_ /usr/lib/go/pkg/tool/linux_amd64/compile -o /var/tmp/portage/app-admin/vaul
>                             \_ /usr/lib/go/pkg/tool/linux_amd64/compile -o /var/tmp/portage/app-admin/vaul
>                             \_ /usr/lib/go/pkg/tool/linux_amd64/compile -o /var/tmp/portage/app-admin/vaul
>                             \_ /usr/lib/go/pkg/tool/linux_amd64/compile -o /var/tmp/portage/app-admin/vaul
>                             \_ /usr/lib/go/pkg/tool/linux_amd64/compile -o /var/tmp/portage/app-admin/vaul
>                             \_ /usr/lib/go/pkg/tool/linux_amd64/compile -o /var/tmp/portage/app-admin/vaul
>                             \_ /usr/lib/go/pkg/tool/linux_amd64/compile -o /var/tmp/portage/app-admin/vaul
>                             \_ /usr/lib/go/pkg/tool/linux_amd64/compile -o /var/tmp/portage/app-admin/vaul

[Comment 3 Sam James 2024-08-03 06:23:37 UTC]

https://github.com/golang/go/pull/63137 maybe..

[Comment 4 Zac Medico 2024-08-03 06:37:16 UTC]

It is related to GOMAXPROCS, if I export GOMAXPROCS=1 then it reduces the compile processes as shown in comment #2 down to a single process.

[Comment 5 Sam James 2024-08-03 06:43:04 UTC]

I was convinced we set GOMAXPROCS in one of the Go eclasses, but apparently not.

[Comment 6 Toralf Förster 2024-08-03 07:26:06 UTC]

I do have this here at the tinderbox:

EGO_BUILD_FLAGS="-p $j"
GO19CONCURRENTCOMPILATION=0
GOMAXPROCS=$j

Can I reduce it to GOMAXPROCS?

[Comment 7 Zac Medico 2024-08-03 07:54:05 UTC]

GOMAXPROCS is similar to the make -j option, so it its reasonable to set them to the same value.

However it is notable that GOMAXPROCS does not seem to have an equivalent to the make --load-average option.

[Comment 8 Zac Medico 2024-08-05 00:45:31 UTC]

I suppose the POSIX jobserver support proposed in https://github.com/golang/go/issues/36868 could possibly help to keep GOMAXPROCS under control.