Bug 215603
Summary: | Support go toolchain builds that default to CGO_ENABLED=0 | ||
---|---|---|---|
Product: | Tools | Reporter: | Andrew G. Morgan (morgan) |
Component: | libcap | Assignee: | Andrew G. Morgan (morgan) |
Status: | RESOLVED CODE_FIX | ||
Severity: | normal | ||
Priority: | P1 | ||
Hardware: | All | ||
OS: | Linux | ||
Kernel Version: | n/a | Subsystem: | |
Regression: | No | Bisected commit-id: |
Description
Andrew G. Morgan
2022-02-14 03:17:21 UTC
This is fixed with: https://git.kernel.org/pub/scm/libs/libcap/libcap.git/commit/?id=aae937481ae28c0cfe502309e9acb5c34ba0b2cd For the record, the setup was slightly different. The Go team have not changed the default build characteristics of Go to CGO_ENABLED=0. Instead, I was building the Go build tree with that configuration (to run its in-build tests with CGO_ENABLED=0), and that causes the built compiler to default to CGO_ENABLED=0. I've updated the bug title to reflect the actual issue. |