In the latest release of FTL (v5.2): https://github.com/pi-hole/ftl/releases there are 3 ARM builds:
Analyzed them with readelf command and it seems that both first two are hard-float and last is soft-float.
Question 1: Shouldn't pihole-FTL-arm-linux-gnueabi be soft-float ?
I do have an armv5 machine which is soft-float. Output of uname -a:
Linux debian-nas 4.20.6-kirkwood-tld-1 #1 PREEMPT Thu Jan 31 21:41:45 PST 2019 armv5tel GNU/Linux
When I'm installing pihole it downloads and installs pihole-FTL-arm-linux-gnueabi which is hard-float does not work on a soft-float machine.
Question 2: Is this a bug or is it normal ? I don't know if that build should either be soft-float or the installer detects the architecture wrong.
Finally, I checked out the source code at V5.2, built and installed the pihole-FTL binary and everything is working fine, but every time I do a pihole reconfigure (needed to fix when I mess up something) the installer states: Corruption detected and reinstalls again the wrong binary for my architecture.
So, Question 3: What can I do for the installer to not detect the binary as corrupted when is built and installed locally ?