[Bug 240551] lang/go14 unable to build on 12.x using a custom kernel devoid of COMPAT_FREEBSD11
bugzilla-noreply at freebsd.org
bugzilla-noreply at freebsd.org
Fri Sep 13 07:14:52 UTC 2019
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=240551
Bug ID: 240551
Summary: lang/go14 unable to build on 12.x using a custom
kernel devoid of COMPAT_FREEBSD11
Product: Ports & Packages
Version: Latest
Hardware: Any
OS: Any
Status: New
Severity: Affects Only Me
Priority: ---
Component: Individual Port(s)
Assignee: jlaffaye at FreeBSD.org
Reporter: dewayne at heuristicsystems.com.au
Flags: maintainer-feedback?(jlaffaye at FreeBSD.org)
Assignee: jlaffaye at FreeBSD.org
This is to track the remediation of the bug where go14 will not build on a
custom 12.x kernel unless "options COMPAT_FREEBSD11" is included.
The go folks identified the upcoming problem in 2017. Patches have been
developed, unfortunately only 2 of the three could be successfully applied to
go 1.4.3_5:
https://go-review.googlesource.com/c/go/+/143637/3/src/syscall/export_freebsd_test.go
https://go-review.googlesource.com/c/go/+/143637/3/src/syscall/syscall_freebsd_test.go
but this failed.
https://go-review.googlesource.com/c/go/+/143637/3/src/syscall/syscall_freebsd.go
Incidentally. For those, like me also running ASLR, the patch at
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=235735
also applied cleanly :)
It would be appropriate to close this when we can actually get go14 to build
without requiring additional options to the kernel. Admittedly if you use
GENERIC, you will not see this problem.
It is appreciated that there are enthusiasts looking after
https://github.com/golang/go/wiki/FreeBSD :)
I don't know where I could've found this information before moving from 11.3S
to 12.1-PreRelease, as we wouldn't have upgraded had we know that some of our
key applications would not build. Unfortunately I can't even suggest a
sufficient test for BROKEN-ness - either kern.ident = GENERIC or the custom
kernel may include COMPAT_FREEBSD11.
--
You are receiving this mail because:
You are the assignee for the bug.
More information about the freebsd-ports-bugs
mailing list