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

Using CGO_ENABLED=0 for Alpine Linux, etc. #9

Closed
whosgonna opened this issue May 25, 2022 · 2 comments
Closed

Using CGO_ENABLED=0 for Alpine Linux, etc. #9

whosgonna opened this issue May 25, 2022 · 2 comments

Comments

@whosgonna
Copy link
Sponsor

I'm sorry that I'm not able to better define the reasoning, etc. on this, however the pre-compiled binary won't work on Alpine linux, and just compiling as indicated in the instructions doesn't work:

git clone https://github.com/miconda/sipexer
cd sipexer
go get ./...
go build .

Setting the env var CGO_ENABLED to 0 when building creates a binary that works (for me) in both the default alpine container as well
as my normal Debian distro:

CGO_ENABLED=0 go build .

Given that this works for me on both, I'm not sure if it's better to have the distributed binary and the instructions always reference this, OR to simply add a note in the installation section? Or maybe this is so obvious to someone working in Go that it's unnecessary?

@miconda
Copy link
Owner

miconda commented Jun 27, 2022

Thanks for reporting it! I was not aware of CGO_ENABLED=0 being required and haven't used myself so far (Debian and MacOS). I will add a note in the docs for those that hit the same situation.

miconda added a commit that referenced this issue Jul 11, 2022
@miconda
Copy link
Owner

miconda commented Jul 11, 2022

Readme updated with a note about.

@miconda miconda closed this as completed Jul 11, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants