You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I have since learned that the syscall package is somewhat deprecated and x/sys/unix should be used instead, but it leads to the same error with s/syscall/unix/ when ported (the APIs and types are the same). It looks like a limitation in the system bindings for go, but I‘m not a systems-, nor a go developer, so I might be missing some subtlety (I’m asking for help tho).
It appears that this commit landed the code in question: 0ffaa4d
cc @masci who has addressed FreeBSD build issues in the past.
The text was updated successfully, but these errors were encountered:
This patch adds a _freebsd.go file that builds instead of the regular
one *only* on Freebsd (to the best of my cross-platform Go abilities).
It imports the C constants S_IRWXG and S_IRWXO and uses them instead
of syscall.S_IRWXG and syscall.S_IRWXO.
ClosesDataDog#2078
tolbrino
pushed a commit
to tolbrino/datadog-agent
that referenced
this issue
Aug 31, 2018
This patch adds a _freebsd.go file that builds instead of the regular
one *only* on Freebsd (to the best of my cross-platform Go abilities).
It imports the C constants S_IRWXG and S_IRWXO and uses them instead
of syscall.S_IRWXG and syscall.S_IRWXO.
ClosesDataDog#2078
I’m trying to build this project under FreeBSD 11.2 and I’m getting this error:
I have since learned that the
syscall
package is somewhat deprecated andx/sys/unix
should be used instead, but it leads to the same error withs/syscall/unix/
when ported (the APIs and types are the same). It looks like a limitation in the system bindings for go, but I‘m not a systems-, nor a go developer, so I might be missing some subtlety (I’m asking for help tho).It appears that this commit landed the code in question: 0ffaa4d
cc @masci who has addressed FreeBSD build issues in the past.
The text was updated successfully, but these errors were encountered: