-
-
Notifications
You must be signed in to change notification settings - Fork 220
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
Builds fails on 32 bit systems #707
Comments
Thanks for the heads up! I believe we can just convert the 32 to 31, it's an upper limit on how long a slice can be (which is actually 1<<31 for 32 bit systems since |
Can you try v2.20.29 and tell me if it works? |
Hello, the new versions gives the same error type but different value
|
Off-by-one error, please check v2.20.30! |
Hello, the 32bit build is unfortunately still broken.
the goStringArray has the new -1, the goBytes still has 31
|
Must have been late, how does v2.20.31 do? |
I really hope this is now fixed in v2.20.32, I have no idea why the address space for 32-bit systems is not |
Hello, 2.20.32 seems to be working Thank you :) |
Hello,
I was updating the minify package in the Alpine Linux repos from 1.20.24 to 1.20.28 when I noticed that most if not all 32bit systems failed (log: https://gitlab.alpinelinux.org/Misthios/aports/-/jobs/1394860 ) with the same error:
I have made some changes to those file to get the build passing (log: https://gitlab.alpinelinux.org/Misthios/aports/-/jobs/1395003 ).
But since those changed are untested since I do not use those bindings.
Here are the changes:
The text was updated successfully, but these errors were encountered: