-
Notifications
You must be signed in to change notification settings - Fork 17.8k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
x/sys/unix: Capsicum support breaks freebsd build #21136
Comments
Breaks compilation of any go package on FBSD i386 too. |
I filed #21163 |
AFAIK we don't have a freebsd/386 trybot. |
Hello. May I claim this issue? |
CL https://golang.org/cl/51270 mentions this issue. |
@slon, yes, you could've sent a change (no need to ask), but the fix was simple enough that I just sent it. |
Now that golang/go#21136 is fixed
Capsicum support was added by https://golang.org/cl/47290, but oinly for amd64. This broke the freebsd/386 build which was subsequently fixed by http://golang.org/cl/51270. However, even with this fix the tests still fail to build due to the missing Cap* functions and types. Fix the build/test on FreeBSD 386 for real by re-running mkall.sh to get all the Capsicum functions and types. Updates golang/go#21136 Change-Id: I54fe2c4567674b07dedad677756369a43a1f0ef6
Change https://golang.org/cl/51570 mentions this issue: |
Capsicum support was added by https://golang.org/cl/47290, but only for amd64. This broke the freebsd/386 build which was subsequently fixed by http://golang.org/cl/51270. However, even with this fix the tests still fail to build due to the missing Capsicum functions and types. Fix the build/test on freebsd/386 for real by re-running mkall.sh on FreeBSD 11.1-RELEASE (inside VirtualBox) to get all the Capsicum functions and types. Some zerrors constants were removed or converted to enums in the FreeBSD headers. Manually move them to a dedicated file. Do the same for amd64, where these constants were removed by accident in https://golang.org/cl/47290. Updates golang/go#21136 Change-Id: I54fe2c4567674b07dedad677756369a43a1f0ef6
Capsicum support was added by https://golang.org/cl/47290, but only for amd64. This broke the freebsd/386 build which was subsequently fixed by http://golang.org/cl/51270. However, even with this fix the tests still fail to build due to the missing Capsicum functions and types. Fix the build/test on freebsd/386 for real by re-running mkall.sh on FreeBSD 11.1-RELEASE (inside VirtualBox) to get all the Capsicum functions and types. Some zerrors constants were removed or converted to enums in the FreeBSD headers. Manually move them to a dedicated file. Do the same for amd64, where these constants were removed by accident in https://golang.org/cl/47290. Updates golang/go#21136 Change-Id: I54fe2c4567674b07dedad677756369a43a1f0ef6 Reviewed-on: https://go-review.googlesource.com/51570 Reviewed-by: Brad Fitzpatrick <[email protected]> Run-TryBot: Brad Fitzpatrick <[email protected]> TryBot-Result: Gobot Gobot <[email protected]>
I'm getting this error too @ncw, how did you solve it? |
@hacdias just update - it should be fixed now. It is for me any way. |
I'm getting this error on Travis though with Go 1.8.3. I'll try to figure out why. |
What version of FreeBSD are those with problems running? |
In my case it's cross compiling on Ubuntu Trusty on Travis CI. |
I guess whatever you're using for cross-compiling is not up-to-date... |
I'll check that out, thanks @benlaurie |
@hacdias You need to update |
The build is still broken on freebsd/arm.
|
Yeah, I get the exact same error on Travis, which always downloads the latest commit of each dependency through |
It's also broken on openbsd/arm6:
No error without ldflags. |
That's an obviously different issue. Please file a new issue and makes this issue focus on FreeBSD stuff. |
I am using goxc, to cross-compile but getting exactly this error, tried to update
|
The problem is goxc doesn't have support for current FreeBSD, it seems. |
@benlaurie Hi, thanks for the hint, I just tried with this:
and is working. |
The Capsicum types and constants in x/sys/unix were not generated for freebsd/arm or freebsd/386 in https://golang.org/cl/47290. I fixed the situation for freebsd/386 in https://golang.org/cl/51570 and will try to get a freebsd/arm system set up somewhere to generate them there as well (I didn't manage to generate them using a cross-compile setup). |
Change https://golang.org/cl/53639 mentions this issue: |
Change https://golang.org/cl/53691 mentions this issue: |
It was broken by https://golang.org/cl/47290 Fixes golang/go#21136 Change-Id: I2a08869fd44a9776f0dc7d461814e1df4e606b5d Reviewed-on: https://go-review.googlesource.com/51270 Reviewed-by: Ian Lance Taylor <[email protected]>
Capsicum support was added by https://golang.org/cl/47290, but only for amd64. This broke the freebsd/386 build which was subsequently fixed by http://golang.org/cl/51270. However, even with this fix the tests still fail to build due to the missing Capsicum functions and types. Fix the build/test on freebsd/386 for real by re-running mkall.sh on FreeBSD 11.1-RELEASE (inside VirtualBox) to get all the Capsicum functions and types. Some zerrors constants were removed or converted to enums in the FreeBSD headers. Manually move them to a dedicated file. Do the same for amd64, where these constants were removed by accident in https://golang.org/cl/47290. Updates golang/go#21136 Change-Id: I54fe2c4567674b07dedad677756369a43a1f0ef6 Reviewed-on: https://go-review.googlesource.com/51570 Reviewed-by: Brad Fitzpatrick <[email protected]> Run-TryBot: Brad Fitzpatrick <[email protected]> TryBot-Result: Gobot Gobot <[email protected]>
Re-run mkall.sh on FreeBSD-11.1-RELEASE armv6 for Capsicum consts and POSIX.1-2008 path relative *at() syscalls. Add errors_freebsd_arm.go generated semi-automatically using: https://gist.github.com/paulzhol/c6d54dc2baf2a6bd204b343a15459661 Similar to https://golang.org/cl/51570. In order to handle C enum based constants that mkerrors.sh missed. Use fix from https://golang.org/cl/53639 to run Capsicum tests only on amd64. Fixes golang/go#21136 Change-Id: I9681b033531090e6b1c5e2446a442deb39cf3066 Reviewed-on: https://go-review.googlesource.com/53691 Reviewed-by: Brad Fitzpatrick <[email protected]> Reviewed-by: Tobias Klauser <[email protected]> Run-TryBot: Brad Fitzpatrick <[email protected]> TryBot-Result: Gobot Gobot <[email protected]>
Please answer these questions before submitting your issue. Thanks!
What version of Go are you using (
go version
)?go version go1.8.3 linux/amd64
What operating system and processor architecture are you using (
go env
)?What did you do?
What did you expect to see?
No error
What did you see instead?
I bisected the problem to this commit
golang/sys@7a4fde3
@benlaurie committed with @ianlancetaylor
According to https://go-review.googlesource.com/c/47290/ the trybots ran OK so I'm a bit puzzled about this.
The text was updated successfully, but these errors were encountered: