Skip to content
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

ISSUE-302: Build with Bazel fails on MacOS as of 0.1.1. #80

Open
sijie opened this issue Jun 27, 2020 · 0 comments
Open

ISSUE-302: Build with Bazel fails on MacOS as of 0.1.1. #80

sijie opened this issue Jun 27, 2020 · 0 comments

Comments

@sijie
Copy link
Member

sijie commented Jun 27, 2020

Original Issue: apache#302


One of the reasons we are excited about this package is that it removed any non-Go dependencies, making it easy to build on any environment. As far as I understand, this commit introduced a native dependency: apache#270. Now when I build my project with bazel on MacOS, I see this error:

ERROR: /private/var/tmp/_bazel_matthew/da00a9bee09cb3d27c7323521da8cade/external/com_github_valyala_gozstd/BUILD.bazel:3:1: GoCompilePkg external/com_github_valyala_gozstd/darwin_amd64_stripped/go_default_library%/github.com/valyala/gozstd.a failed (Exit 1) builder failed: error executing command bazel-out/host/bin/external/go_sdk/builder compilepkg -sdk external/go_sdk -installsuffix darwin_amd64 -tags integration -src external/com_github_valyala_gozstd/dict.go -src ... (remaining 55 argument(s) skipped)

Use --sandbox_debug to see verbose messages from the sandbox
clang: error: no such file or directory: './libzstd_darwin_amd64.a'
compilepkg: error running subcommand: exit status 1

I see a reference that this shouldn't be an issue if "cgo is not enabled", but I'm not sure where to set this in my build. You could argue that this isn't an issue for this package and that it's really a bazel issue or an issue with my build settings. Close this issue if you must. Nevertheless, I wanted to let you know that seeing this build failure when I upgraded to 0.1.1 made me sad. I'll continue to see if there's a workaround on my end and will update this issue if I find anything.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

1 participant