-
Notifications
You must be signed in to change notification settings - Fork 6
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
(require osc) fails on 32-bit arm (e.g. raspberry pi 2), possibly x86 as well #5
Comments
I just tried and failed to reproduce this on a VPS running Debian Buster & Racket v7.2:
... so it appears to me that this might actually be a problem with your raspberry pi, or at a minimum some interaction between your raspberry pi and racket and the operating system. There's clearly also something very fishy about the fact that -2147483648 and -2147483647 both map to December 13, 1901. |
Was it x86 or x86_64? My hypothesis was that, according to the documentation of find-seconds:
...since 1900 can't be represented by a 32-bit time_t (the lowest value, according to Wikipedia, is Friday 1901-12-13), it might be returning the error only on 32-bit systems. |
Reproduced on debian buster x86 running in a container:
Same with debian unstable & racket 8.7. |
Ah! My fault, missed the 32-bit information, should have read the title of the issue and not just the comment text. My inclination would be to trap this error and return the hard-coded constant only when the date 1900 can't be found, does that make sense to you? |
Yeah, sure! |
The following line in osc/osc-time.rkt fails on raspberry pi 2 (debian buster, racket 7.2):
With the following error:
I worked around by hard-coding the value
-2208988800
instead, and the package works fine. Maybe it does make sense to simply use the fixed value?The text was updated successfully, but these errors were encountered: