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

Binary 0.5.0 on arm-unknown (RPi 0) appear broken on RPi0W #34

Closed
baekgaard opened this issue Mar 22, 2021 · 4 comments
Closed

Binary 0.5.0 on arm-unknown (RPi 0) appear broken on RPi0W #34

baekgaard opened this issue Mar 22, 2021 · 4 comments

Comments

@baekgaard
Copy link

baekgaard commented Mar 22, 2021

I just installed the binary https://github.com/mfreeborn/heliocron/releases/download/v0.5.0/heliocron-v0.5.0-arm-unknown-linux-gnueabi.tar.gz onto a Raspberry Pi 0 WiFi running Raspbian 10 (buster).

When I call heliocron, it always estimates sunrise and sunset to be at 00:00:00 local time (and hence the day is pretty short).

So something isn't working in that release.

Here is a sample output from the RPi0w (from README.md and works fine on another Linux box I tested on):

user@rpi0w:~/heliocron-v0.5.0-arm-unknown-linux-gnueabi $ ./heliocron -d "7 May 2065" -f "%e %B %Y" -l 55.9533N -o 3.1883W report
LOCATION
--------
Latitude: 55.9533N
Longitude: 3.1883W

DATE
----
2065-05-07 12:00:00 +01:00

Solar noon is at:         2065-05-07 00:00:00 +01:00
The day length is:        0h 0m 0s

Sunrise is at:            2065-05-07 00:00:00 +01:00
Sunset is at:             2065-05-07 00:00:00 +01:00

Civil dawn is at:         2065-05-07 00:00:00 +01:00
Civil dusk is at:         2065-05-07 00:00:00 +01:00

Nautical dawn is at:      2065-05-07 00:00:00 +01:00
Nautical dusk is at:      2065-05-07 00:00:00 +01:00

Astronomical dawn is at:  2065-05-07 00:00:00 +01:00
Astronomical dusk is at:  2065-05-07 00:00:00 +01:00

I assume something doesn't quite build right on this platform, although I haven't tried to rebuild from source.

@GorkaMM
Copy link

GorkaMM commented Mar 27, 2021

Exact same thing on my side. Thanks for the help in advance, @mfreeborn

@mfreeborn
Copy link
Owner

Hmm. Thank you for the reports. I will have a proper look over the next weekend.

@mfreeborn
Copy link
Owner

mfreeborn commented Apr 16, 2021

Thank you both for flagging this issue - I've managed to take a look at this at last. For reasons that I don't entirely understand, it should all be working now that I've recompiled the RPi 0 binary using a the arm-unknown-linux-gnueabihf target triple rather than arm-unknown-linux-gnueabi. I can only seem to find conflicting information regarding which one is correct and which one works at all when compiling for the RPi 0. In this case, both seem to run, but only the hf-variant is correct.

It works on my end, but it would be reassuring if either of you could retry with the new binary on the release page (still v0.5.0).

Edited to add - I did try building from source on the RPi 0 itself, and it worked correctly, but it takes absolutely forever so it's a bit of a non-starter for typical users.

@mfreeborn
Copy link
Owner

No further replies received

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

3 participants