Summary: | dev-lang/go-1.14: mlock of signal stack failed: 12 | ||
---|---|---|---|
Product: | Gentoo Linux | Reporter: | Robin Hallabro-Kokko <robin> |
Component: | Current packages | Assignee: | William Hubbs <williamh> |
Status: | RESOLVED FIXED | ||
Severity: | normal | CC: | fedeliallalinea, jstein |
Priority: | Normal | Keywords: | PullRequest |
Version: | unspecified | ||
Hardware: | All | ||
OS: | Linux | ||
See Also: |
https://github.com/gentoo/gentoo/pull/14868 https://github.com/golang/go/issues/37436 |
||
Whiteboard: | |||
Package list: | Runtime testing required: | --- | |
Attachments: |
emerge info
build.log |
Description
Robin Hallabro-Kokko
2020-03-08 17:31:06 UTC
Created attachment 617526 [details]
emerge info
Created attachment 617528 [details]
build.log
Emerge works fine with FEATURES=-userpriv but it may cause problems as documented upstreams at https://github.com/golang/go/issues/37436 Opened a pull request to explicitly check for running kernel version before proceeding. The bug has been closed via the following commit(s): https://gitweb.gentoo.org/repo/gentoo.git/commit/?id=7e804a5ea4822b370bc0eb2fc33296ba4ec4cb7e commit 7e804a5ea4822b370bc0eb2fc33296ba4ec4cb7e Author: William Hubbs <william.hubbs@sony.com> AuthorDate: 2020-03-08 18:43:15 +0000 Commit: William Hubbs <williamh@gentoo.org> CommitDate: 2020-03-09 17:10:45 +0000 dev-lang/go: 1.14: check running kernel version before compiling Compilation will fail if the host is running certain versions of the Linux kernel with the message: runtime: mlock of signal stack failed: 12 Note from williamh: The original pr checked for kernel versions not listed in the upstream issue, so I reworked it. Also, it used pkg_setup instead of pkg_pretend for the checks. Closes: https://bugs.gentoo.org/711884 Closes: https://github.com/gentoo/gentoo/pull/14868 Signed-off-by: William Hubbs <williamh@gentoo.org> dev-lang/go/go-1.14.ebuild | 22 +++++++++++++++++++++- 1 file changed, 21 insertions(+), 1 deletion(-) In go-1.14.1 the commited message is removed but bug already exists (see [1]). [1] https://forums.gentoo.org/viewtopic-p-8437762.html |