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

[BUG]: Building a plugin that uses badger fails #1833

Closed
jasonf-trustgrid opened this issue Dec 2, 2022 · 1 comment · Fixed by #1910
Closed

[BUG]: Building a plugin that uses badger fails #1833

jasonf-trustgrid opened this issue Dec 2, 2022 · 1 comment · Fixed by #1910
Labels
kind/bug Something is broken.

Comments

@jasonf-trustgrid
Copy link

What version of Badger are you using?

github.com/dgraph-io/badger/v3 v3.2103.4

What version of Go are you using?

GOVERSION="go1.19.1"

Have you tried reproducing the issue with the latest release?

Yes

What is the hardware spec (RAM, CPU, OS)?

Macbook Pro 2021 Intel Core i5 w/ 16GB RAM

What steps will reproduce the bug?

create a plugin that uses badger,
try to compile that plugin with go build -buildmode=plugin

Expected behavior and actual result.

Compilation should succeed and a shared object should be produced.

Instead the following error is reported:

# github.com/cespare/xxhash
asm: xxhash_amd64.s:120: when dynamic linking, R15 is clobbered by a global variable access and is used here: 00092 (/Users/jasonfowler/go/pkg/mod/github.com/cespare/[email protected]/xxhash_amd64.s:120)       ADDQ    R15, AX
asm: assembly failed

Additional information

No response

@jasonf-trustgrid jasonf-trustgrid added the kind/bug Something is broken. label Dec 2, 2022
mangalaman93 added a commit that referenced this issue Mar 18, 2023
@mangalaman93
Copy link
Contributor

This is related to cespare/xxhash#54. I have created a PR to upgrade xxhash. Thanks for filling the issue.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
kind/bug Something is broken.
Development

Successfully merging a pull request may close this issue.

2 participants