-
Notifications
You must be signed in to change notification settings - Fork 43
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
Unable to compile for armhf on Raspberry Pi 3B #4
Comments
I was able to compile it under go version 1.9.7. Here is the instruction: Get into the golang container:
Then downgrade urfave/cli to the version that supports go v1.9:
Now we can install and compile the project:
Once it's done check the compiled binary (goodls):
Now copy the binary to the host machine:
|
@tanaikech could you add the arm builds, please? |
Thank you for your support. Unfortunately, I have no information about "the arm builds". This is due to my poor skill. I deeply apologize for this. |
@tanaikech I'm sorry, I didn't mean/intend to offend you but either I don't understand why did you answer me with sarcasm? |
Thank you for your support. I deeply apologize for my poor English skill. I don't mean to hurt your feeling. Unfortunately, I cannot understand about what you want. Because I have no information about "the ARM build". The reason that I cannot understand about your replying is due to my skill. So I thought that I have to apologize for this. |
Thank you for replying. I could understand about your proposal. So I added them to here. Could you please confirm it? |
Yes, it works, thank you! This issue is 100% resolved |
Since there's no arm binary already uploaded I tried to compile from source on a Raspberry Pi 3B running Raspbian Stretch where the repo go version is 1.7.4. I set $GOPATH to a home subfolder and run "go get -u github.com/tanaikech/goodls" as the manual suggests but I get
So, is there a way to build for armhf? Is perhaps a higher Go version required for this source code? Or perhaps a binary could be uploaded for armhf?
The text was updated successfully, but these errors were encountered: