-
Notifications
You must be signed in to change notification settings - Fork 451
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
mipsle compile #59
Comments
Looks the same as this issue: Looks like there are some suggested approaches in that thread. I would be open to patches that specialize with build constraints based on GOARCH (we have build constraints based on GOOS and CGO right now, but not GOARCH). |
the same issue with GOARCH=mips EDIT:
After that, that package works. However, this is way complicated, time consuming, and not portable (one would have to cross compile c++, and manually change constants... etc etc). |
Use "golang.org/x/sys/unix" instead of "syscall" (fix #59)
This is still broken on mipsle and mips with the same error that OP reported. After the merged patch, the missing fields are still referenced. |
@nocko I believe this is compiling as expected on mips. I just pushed a change to the travis.yml file that adds cross compile targets for arm, mips, and mipsle and those at least compile (I have not personally tested mips, but arm and x64 are in production). |
Hi,
Your library looks solid and can use on linux np. However, I did most recently purchase some new IoT Omega2 processors from onion.io and they could be quite popular.
I have been writing programs in GO and running on it w/no problem. Runs great, small and tight.
I was hoping to get some serial port development going on it, and of course, seem to be quite a few platform specific items breaking.
Your serial lib seems the closest. I try to compile the simple default sample you provide with the library, and get the following error using this compile syntax.
GOOS=linux GOARCH=mipsle go build -compiler gc serial.go
Anything I can do to help you support this platform ?
The text was updated successfully, but these errors were encountered: