Piaware on Void Linux

FlightAware ADS-B Flight Tracking
1

Did anyone try to build it on the latest void ARM platform?

Here is where I got so far:

xbps-install -y tcl openssl-c_rehash autoconf

TCLlauncher seems to be needed for piaware

git clone https://github.com/flightaware/tcllauncher
$ cd tcllauncher
$ autoconf
$ ./configure --prefix=/opt/tcl
$ make
$ make install

This will not build

autoconf
configure.in:38: warning: The macro `AC_HELP_STRING' is obsolete.
configure.in:38: You should run autoupdate.
./lib/autoconf/general.m4:204: AC_HELP_STRING is expanded from...
tclconfig/tcl.m4:43: TEA_PATH_TCLCONFIG is expanded from...
configure.in:38: the top level
configure.in:39: warning: The macro `AC_TRY_COMPILE' is obsolete.
configure.in:39: You should run autoupdate.
./lib/autoconf/general.m4:2847: AC_TRY_COMPILE is expanded from...
tclconfig/tcl.m4:353: TEA_LOAD_TCLCONFIG is expanded from...
configure.in:39: the top level
configure.in:62: warning: The macro `AC_TRY_COMPILE' is obsolete.
configure.in:62: You should run autoupdate.
./lib/autoconf/general.m4:2847: AC_TRY_COMPILE is expanded from...
lib/m4sugar/m4sh.m4:692: _AS_IF_ELSE is expanded from...
lib/m4sugar/m4sh.m4:699: AS_IF is expanded from...
./lib/autoconf/general.m4:2249: AC_CACHE_VAL is expanded from...
./lib/autoconf/general.m4:2270: AC_CACHE_CHECK is expanded from...
tclconfig/tcl.m4:3255: TEA_SETUP_COMPILER is expanded from...
configure.in:62: the top level
configure.in:62: warning: The macro `AC_TRY_LINK' is obsolete.
configure.in:62: You should run autoupdate.
./lib/autoconf/general.m4:2920: AC_TRY_LINK is expanded from...
lib/m4sugar/m4sh.m4:692: _AS_IF_ELSE is expanded from...
lib/m4sugar/m4sh.m4:699: AS_IF is expanded from...
./lib/autoconf/general.m4:2249: AC_CACHE_VAL is expanded from...
./lib/autoconf/general.m4:2270: AC_CACHE_CHECK is expanded from...
tclconfig/tcl.m4:2283: TEA_MISSING_POSIX_HEADERS is expanded from...
tclconfig/tcl.m4:3255: TEA_SETUP_COMPILER is expanded from...
configure.in:62: the top level
configure.in:62: warning: The macro `AC_HAVE_HEADERS' is obsolete.
configure.in:62: You should run autoupdate.
./lib/autoconf/oldnames.m4:35: AC_HAVE_HEADERS is expanded from...
tclconfig/tcl.m4:2283: TEA_MISSING_POSIX_HEADERS is expanded from...
tclconfig/tcl.m4:3255: TEA_SETUP_COMPILER is expanded from...
configure.in:62: the top level
configure.in:133: warning: The macro `AC_HELP_STRING' is obsolete.
configure.in:133: You should run autoupdate.
./lib/autoconf/general.m4:204: AC_HELP_STRING is expanded from...
tclconfig/tcl.m4:729: TEA_ENABLE_THREADS is expanded from...
configure.in:133: the top level
configure.in:140: warning: The macro `AC_HELP_STRING' is obsolete.
configure.in:140: You should run autoupdate.
./lib/autoconf/general.m4:204: AC_HELP_STRING is expanded from...
tclconfig/tcl.m4:672: TEA_ENABLE_SHARED is expanded from...
configure.in:140: the top level
configure.in:148: warning: The macro `AC_HELP_STRING' is obsolete.
configure.in:148: You should run autoupdate.
./lib/autoconf/general.m4:204: AC_HELP_STRING is expanded from...
tclconfig/tcl.m4:1038: TEA_CONFIG_CFLAGS is expanded from...
configure.in:148: the top level
configure.in:148: warning: The macro `AC_TRY_LINK' is obsolete.
configure.in:148: You should run autoupdate.
./lib/autoconf/general.m4:2920: AC_TRY_LINK is expanded from...
lib/m4sugar/m4sh.m4:692: _AS_IF_ELSE is expanded from...
lib/m4sugar/m4sh.m4:699: AS_IF is expanded from...
./lib/autoconf/general.m4:2249: AC_CACHE_VAL is expanded from...
./lib/autoconf/general.m4:2270: AC_CACHE_CHECK is expanded from...
tclconfig/tcl.m4:1038: TEA_CONFIG_CFLAGS is expanded from...
configure.in:148: the top level
configure.in:148: warning: The macro `AC_HELP_STRING' is obsolete.
configure.in:148: You should run autoupdate.
./lib/autoconf/general.m4:204: AC_HELP_STRING is expanded from...
lib/m4sugar/m4sh.m4:699: AS_IF is expanded from...
tclconfig/tcl.m4:1038: TEA_CONFIG_CFLAGS is expanded from...
configure.in:148: the top level
configure.in:148: warning: The macro `AC_TRY_COMPILE' is obsolete.
configure.in:148: You should run autoupdate.
./lib/autoconf/general.m4:2847: AC_TRY_COMPILE is expanded from...
tclconfig/tcl.m4:1038: TEA_CONFIG_CFLAGS is expanded from...
configure.in:148: the top level
configure.in:148: warning: The macro `AC_TRY_LINK' is obsolete.
configure.in:148: You should run autoupdate.
./lib/autoconf/general.m4:2920: AC_TRY_LINK is expanded from...
lib/m4sugar/m4sh.m4:692: _AS_IF_ELSE is expanded from...
lib/m4sugar/m4sh.m4:699: AS_IF is expanded from...
./lib/autoconf/general.m4:2249: AC_CACHE_VAL is expanded from...
./lib/autoconf/general.m4:2270: AC_CACHE_CHECK is expanded from...
lib/m4sugar/m4sh.m4:699: AS_IF is expanded from...
tclconfig/tcl.m4:1038: TEA_CONFIG_CFLAGS is expanded from...
configure.in:148: the top level
configure.in:148: warning: The macro `AC_TRY_LINK' is obsolete.
configure.in:148: You should run autoupdate.
./lib/autoconf/general.m4:2920: AC_TRY_LINK is expanded from...
lib/m4sugar/m4sh.m4:692: _AS_IF_ELSE is expanded from...
lib/m4sugar/m4sh.m4:699: AS_IF is expanded from...
./lib/autoconf/general.m4:2249: AC_CACHE_VAL is expanded from...
./lib/autoconf/general.m4:2270: AC_CACHE_CHECK is expanded from...
lib/m4sugar/m4sh.m4:699: AS_IF is expanded from...
lib/m4sugar/m4sh.m4:699: AS_IF is expanded from...
tclconfig/tcl.m4:1038: TEA_CONFIG_CFLAGS is expanded from...
configure.in:148: the top level
configure.in:148: warning: The macro `AC_TRY_RUN' is obsolete.
configure.in:148: You should run autoupdate.
./lib/autoconf/general.m4:2997: AC_TRY_RUN is expanded from...
tclconfig/tcl.m4:1038: TEA_CONFIG_CFLAGS is expanded from...
configure.in:148: the top level
configure.in:148: warning: The macro `AC_TRY_COMPILE' is obsolete.
configure.in:148: You should run autoupdate.
./lib/autoconf/general.m4:2847: AC_TRY_COMPILE is expanded from...
tclconfig/tcl.m4:2699: TEA_TCL_EARLY_FLAG is expanded from...
tclconfig/tcl.m4:2712: TEA_TCL_EARLY_FLAGS is expanded from...
tclconfig/tcl.m4:1038: TEA_CONFIG_CFLAGS is expanded from...
configure.in:148: the top level
configure.in:148: warning: The macro `AC_TRY_COMPILE' is obsolete.
configure.in:148: You should run autoupdate.
./lib/autoconf/general.m4:2847: AC_TRY_COMPILE is expanded from...
lib/m4sugar/m4sh.m4:692: _AS_IF_ELSE is expanded from...
lib/m4sugar/m4sh.m4:699: AS_IF is expanded from...
./lib/autoconf/general.m4:2249: AC_CACHE_VAL is expanded from...
tclconfig/tcl.m4:2746: TEA_TCL_64BIT_FLAGS is expanded from...
tclconfig/tcl.m4:1038: TEA_CONFIG_CFLAGS is expanded from...
configure.in:148: the top level
configure.in:148: warning: The macro `AC_TRY_COMPILE' is obsolete.
configure.in:148: You should run autoupdate.
./lib/autoconf/general.m4:2847: AC_TRY_COMPILE is expanded from...
lib/m4sugar/m4sh.m4:692: _AS_IF_ELSE is expanded from...
lib/m4sugar/m4sh.m4:699: AS_IF is expanded from...
./lib/autoconf/general.m4:2249: AC_CACHE_VAL is expanded from...
./lib/autoconf/general.m4:2270: AC_CACHE_CHECK is expanded from...
tclconfig/tcl.m4:2746: TEA_TCL_64BIT_FLAGS is expanded from...
tclconfig/tcl.m4:1038: TEA_CONFIG_CFLAGS is expanded from...
configure.in:148: the top level
configure.in:154: warning: The macro `AC_HELP_STRING' is obsolete.
configure.in:154: You should run autoupdate.
./lib/autoconf/general.m4:204: AC_HELP_STRING is expanded from...
tclconfig/tcl.m4:857: TEA_ENABLE_SYMBOLS is expanded from...
configure.in:154: the top level
configure.in:205: warning: The macro `AC_HELP_STRING' is obsolete.
configure.in:205: You should run autoupdate.
./lib/autoconf/general.m4:204: AC_HELP_STRING is expanded from...
configure.in:205: the top level
configure.in:225: warning: AC_C_BIGENDIAN should be used with AC_CONFIG_HEADERS

Therefore this will not build:
git clone GitHub - flightaware/piaware: Client-side package and programs for forwarding ADS-B data to FlightAware

make -C package install
make[1]: Entering directory ‘/home/radar/piaware/package’
install -d /usr/lib/piaware_packages /usr/lib/piaware_packages/ca
install fa_piaware_config.tcl fa_adept_client.tcl fa_sudo.tcl fa_services.tcl fa_sysinfo.tcl fa_gps.tcl piaware.tcl tryfinallyshim.tcl egm96.tcl egm96geoid.tcl pkgIndex.tcl /usr/lib/piaware_packages
install ca/*.pem /usr/lib/piaware_packages/ca
c_rehash /usr/lib/piaware_packages/ca
Doing /usr/lib/piaware_packages/ca
make -C helpers install
make[2]: Entering directory ‘/home/radar/piaware/package/helpers’
install -d /usr/lib/piaware_packages/helpers
install -m 0755 update-piaware-config droproot restart-receiver restart-network /usr/lib/piaware_packages/helpers
make[2]: Leaving directory ‘/home/radar/piaware/package/helpers’
make -C fa_adept_codec install
make[2]: Entering directory ‘/home/radar/piaware/package/fa_adept_codec’
install -d /usr/lib/fa_adept_codec
install fa_adept_codec.tcl fa_adept_schema.tcl none.codec adept_1.x.codec adept_2.1.codec adept_2.2.codec pkgIndex.tcl /usr/lib/fa_adept_codec
make[2]: Leaving directory ‘/home/radar/piaware/package/fa_adept_codec’
make[1]: Leaving directory ‘/home/radar/piaware/package’
make -C programs/piaware install
make[1]: Entering directory ‘/home/radar/piaware/programs/piaware’
which: no tcllauncher in (/usr/bin:/bin:/usr/sbin:/sbin:/usr/local/sbin:/usr/local/bin)
install -d /usr/bin /usr/lib/piaware
install -m 0755 /usr/bin/piaware
install: missing destination file operand after ‘/usr/bin/piaware’
Try ‘install --help’ for more information.
make[1]: *** [Makefile:15: install] Error 1
make[1]: Leaving directory ‘/home/radar/piaware/programs/piaware’
make: *** [Makefile:19: install] Error 2

It would be very nice having a void linux package containing all the necessary components :innocent:

2

(1) What are outputs of following 2 commands:

uname -a

lsb_release -a

(2) Have you tried the following automated install scripts for piaware and dump1090-fa?

https://github.com/abcd567a/piaware-ubuntu-debian-amd64

Automated Installation of piaware 7.2, dump1090-fa 7.2, piaware-web 7.2, and dump978-fa 7.2 (by building packages from source code), on following OS:

(1) Ubuntu 18, 20, & 22 - amd64 / x86_64

(2) Debian 9, 10, & 11 - amd64 / x86_64

(3) Linux Mint 19, 20, & 21 - amd64 / x86_64

(4) Kali-linux 2021 & 2022 - amd64

(5) On RPI Model 3 & 4 (32-bit & 64-bit / armv7l & aarch64) Raspberry Pi OS Stretch, Buster, & Bullseye, DietPi OS Stretch, Buster, & Bullseye, Ubuntu 18, 20, and 22 for RPi, and Kali 2021 for RPi

 

3

I guarantee you tons of things would break due to systemd checks, void is using runit as the init system.

As I see this is some TCL thingy internally and has a main binary. I even managed just to scp it from a raspbian box

s -al /usr/lib/ | grep piaw
drwxr-xr-x 3 root root 4096 Mar 4 2022 piaware
drwxr-xr-x 2 root root 4096 Mar 4 2022 piaware-config
drwxr-xr-x 2 root root 4096 Mar 4 2022 piaware-status
drwxr-xr-x 4 root root 4096 Mar 4 2022 piaware_packages

Plus this
/usr/lib/Tcllauncher1.8/

Now I get:

./piaware 
application-specific initialization failed: can't find package Tclx
can't find package Tclx
    while executing
"package require Tclx"
    (file "/usr/lib/Tcllauncher1.8/tcllauncher.tcl" line 5)

No tclx package in Void again either :frowning:

Anyway this is a hackintosh as that box is old as hell

piaware -v
7.1

I’m actually working on phasing it out, I would prefer getting the latest of everything on the new one.

4

@zymucicp

About almost 3 years ago I succeeded in installing dump1090-fa on Fedora & Red Hat Enterprise Linux (RHEL), but failed to install piaware on them due to tcllauncher. :angry: :sob:

https://discussions.flightaware.com/t/howto-install-dump1090-fa-on-fedora-and-rhel-x86-64/60004/7

5

Why dont you try some other debian based OS like RaspberryPi OS (LITE) or DietPiOS? What is architecture / CPU of that old box?

6

@zymucicp

Have you tried OS SLAX?

[SOLVED] SLAX Linux AMD64 OS: faup1090 is not working

7

I love void Linux a lot that’s why. Don’t you guys want to release a single C binary just as a feeder? I don’t need the local webserver crap I just want to send data to flightaware that’s all.

Flightradar has a single binary which does this for example and they even provide statically compiled binary package I can just run, works fine on Void as well.

9

 

Yes, indeed

 

FLIGHTRADAR24 amd64 - STATICALLY LINKED LIBRARIES

~ $ wget https://repo-feed.flightradar24.com/linux_x86_64_binaries/fr24feed_1.0.25-3_amd64.tgz

~ $ tar -xvzf fr24feed_1.0.25-3_amd64.tgz

~ $ cd fr24feed_amd64

~/fr24feed_amd64 $ file fr24feed
fr24feed: ELF 64-bit LSB executable, x86-64, version 1 (GNU/Linux), statically linked, BuildID[sha1]=538c181675a9e019b529fa5edfe4bf343c218aed, for GNU/Linux 3.2.0, stripped

 

FLIGHTRADAR24 i386 - STATICALLY LINKED LIBRARIES

~ $ wget https://repo-feed.flightradar24.com/linux_x86_binaries/fr24feed_1.0.25-3_i386.tgz  

~ $ tar -xvzf fr24feed_1.0.25-3_i386.tgz 

~ $ cd fr24feed_i386

~/fr24feed_i386 $ file fr24feed
fr24feed: ELF 32-bit LSB executable, Intel 80386, version 1 (GNU/Linux), statically linked, BuildID[sha1]=ef4cb27598c3d462636350b36402dd637d1af495, for GNU/Linux 3.2.0, stripped

 

PLANEFINDER amd64 - DYNAMICALLY LINKED LIBRARIES

wget http://client.planefinder.net/pfclient_5.0.162_amd64.tar.gz   

~ $ tar -xvzf pfclient_5.0.162_amd64.tar.gz
pfclient

~ $ file pfclient
pfclient: ELF 64-bit LSB executable, x86-64, version 1 (SYSV), dynamically linked, interpreter /lib64/ld-linux-x86-64.so.2, for GNU/Linux 2.6.32, BuildID[sha1]=9b621363cfa26562a7613f16a693ff97960828e6, with debug_info, not stripped

~ $ ldd pfclient
libpthread.so.0
libm.so.6
librt.so.1
libc.so.6

 

PLANEFINDER i386 - DYNAMICALLY LINKED LIBRARIES

wget http://client.planefinder.net/pfclient_5.0.161_i386.tar.gz


~ $ tar -xvzf pfclient_5.0.161_i386.tar.gz

~ $ file pfclient
pfclient: ELF 32-bit LSB executable, Intel 80386, version 1 (SYSV), dynamically linked, interpreter /lib/ld-linux.so.2, for GNU/Linux 2.6.32, BuildID[sha1]=fb0690ab91fec04c639cb819fd16000c187e533f, with debug_info, not stripped


~ $ ldd pfclient
libpthread.so.0
libm.so.6
librt.so.1
libc.so.6
10

OS = Debian 11.5 amd64

abcd@debian-11-5:~$ lsb_release -a
No LSB modules are available.
Distributor ID: Debian
Description:    Debian GNU/Linux 11 (bullseye)
Release:        11
Codename:       bullseye

 

Piaware amd64

abcd@debian-11-5:~$ file /usr/bin/piaware
/usr/bin/piaware: ELF 64-bit LSB pie executable, x86-64, version 1 (SYSV), dynamically linked, interpreter /lib64/ld-linux-x86-64.so.2, BuildID[sha1]=723147343fe59131e6741104d3807e6330dedf3d, for GNU/Linux 3.2.0, stripped

 

abcd@debian-11-5:~$ ldd /usr/bin/piaware
        linux-vdso.so.1 (0x00007ffcaa362000)
        libtcl8.6.so => /lib/x86_64-linux-gnu/libtcl8.6.so (0x00007f6bf0339000)
        libc.so.6 => /lib/x86_64-linux-gnu/libc.so.6 (0x00007f6bf0164000)
        libdl.so.2 => /lib/x86_64-linux-gnu/libdl.so.2 (0x00007f6bf015e000)
        libz.so.1 => /lib/x86_64-linux-gnu/libz.so.1 (0x00007f6bf0141000)
        libpthread.so.0 => /lib/x86_64-linux-gnu/libpthread.so.0 (0x00007f6bf011f000)
        libm.so.6 => /lib/x86_64-linux-gnu/libm.so.6 (0x00007f6beffdb000)
        /lib64/ld-linux-x86-64.so.2 (0x00007f6bf051c000)

 

dump1090-fa amd64

abcd@debian-11-5:~$ file /usr/bin/dump1090-fa
/usr/bin/dump1090-fa: ELF 64-bit LSB pie executable, x86-64, version 1 (SYSV), dynamically linked, interpreter /lib64/ld-linux-x86-64.so.2, BuildID[sha1]=475d539bfe28e298149c21f331292863d2c9f31e, for GNU/Linux 3.2.0, stripped

 

abcd@debian-11-5:~$ ldd /usr/bin/dump1090-fa
        linux-vdso.so.1 (0x00007ffd567ef000)
        libpthread.so.0 => /lib/x86_64-linux-gnu/libpthread.so.0 (0x00007f1582873000)
        libm.so.6 => /lib/x86_64-linux-gnu/libm.so.6 (0x00007f158272f000)
        librtlsdr.so.0 => /lib/x86_64-linux-gnu/librtlsdr.so.0 (0x00007f158271f000)
        libbladeRF.so.2 => /lib/x86_64-linux-gnu/libbladeRF.so.2 (0x00007f1582693000)
        libhackrf.so.0 => /lib/x86_64-linux-gnu/libhackrf.so.0 (0x00007f158248d000)
        libLimeSuite.so.20.10-1 => /lib/x86_64-linux-gnu/libLimeSuite.so.20.10-1 (0x00007f15823b9000)
        libncurses.so.6 => /lib/x86_64-linux-gnu/libncurses.so.6 (0x00007f158238d000)
        libtinfo.so.6 => /lib/x86_64-linux-gnu/libtinfo.so.6 (0x00007f158235e000)
        libc.so.6 => /lib/x86_64-linux-gnu/libc.so.6 (0x00007f1582189000)
        /lib64/ld-linux-x86-64.so.2 (0x00007f1582918000)
        libusb-1.0.so.0 => /lib/x86_64-linux-gnu/libusb-1.0.so.0 (0x00007f158216b000)
        libstdc++.so.6 => /lib/x86_64-linux-gnu/libstdc++.so.6 (0x00007f1581f9e000)
        libgcc_s.so.1 => /lib/x86_64-linux-gnu/libgcc_s.so.1 (0x00007f1581f84000)
        libdl.so.2 => /lib/x86_64-linux-gnu/libdl.so.2 (0x00007f1581f7c000)
        libudev.so.1 => /lib/x86_64-linux-gnu/libudev.so.1 (0x00007f1581f54000)

 

 

++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++

ARM (armv7l)

 
++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++

 

 

OS = PIAWARE SD CARD IMAGE VER 7.2 on ARM (armv7l) Raspberry Pi

pi@piaware:~ $ uname -a
Linux piaware 5.15.76-v7l+ #1597 SMP Fri Nov 4 12:14:58 GMT 2022 armv7l GNU/Linux

pi@piaware:~ $ lsb_release -a
No LSB modules are available.
Distributor ID: Raspbian
Description:    Raspbian GNU/Linux 11 (bullseye)
Release:        11
Codename:       bullseye

 

PIAWARE ver 7.2 on ARM (armv7l)

pi@piaware:~ $ file /usr/bin/piaware
/usr/bin/piaware: ELF 32-bit LSB executable, ARM, EABI5 version 1 (SYSV), dynamically linked, interpreter /lib/ld-linux-armhf.so.3, BuildID[sha1]=15f804e98244ebf0304b0ffcf871f4bcd2b18ff2, for GNU/Linux 3.2.0, stripped   

pi@piaware:~ $ ldd /usr/bin/piaware
        linux-vdso.so.1 (0xbee33000)
        /usr/lib/arm-linux-gnueabihf/libarmmem-${PLATFORM}.so => /usr/lib/arm-linux-gnueabihf/libarmmem-v7l.so (0xb6ece000)
        libtcl8.6.so => /lib/arm-linux-gnueabihf/libtcl8.6.so (0xb6d3a000)
        libc.so.6 => /lib/arm-linux-gnueabihf/libc.so.6 (0xb6be6000)
        /lib/ld-linux-armhf.so.3 (0xb6ee3000)
        libdl.so.2 => /lib/arm-linux-gnueabihf/libdl.so.2 (0xb6bd2000)
        libz.so.1 => /lib/arm-linux-gnueabihf/libz.so.1 (0xb6baa000)
        libpthread.so.0 => /lib/arm-linux-gnueabihf/libpthread.so.0 (0xb6b7e000)
        libm.so.6 => /lib/arm-linux-gnueabihf/libm.so.6 (0xb6b0f000)

 

DUMP1090-FA ver 7.2 on ARM (armv7l)

pi@piaware:~ $ file /usr/bin/dump1090-fa
/usr/bin/dump1090-fa: ELF 32-bit LSB executable, ARM, EABI5 version 1 (SYSV), dynamically linked, interpreter /lib/ld-linux-armhf.so.3, BuildID[sha1]=d50e436b72d39c687c7be75bceec791066e7fbf5, for GNU/Linux 3.2.0, stripped

pi@piaware:~ $ ldd /usr/bin/dump1090-fa
        linux-vdso.so.1 (0xbecf2000)
        /usr/lib/arm-linux-gnueabihf/libarmmem-${PLATFORM}.so => /usr/lib/arm-linux-gnueabihf/libarmmem-v7l.so (0xb6f9c000)
        libpthread.so.0 => /lib/arm-linux-gnueabihf/libpthread.so.0 (0xb6f70000)
        libm.so.6 => /lib/arm-linux-gnueabihf/libm.so.6 (0xb6f01000)
        librtlsdr.so.0 => /lib/arm-linux-gnueabihf/librtlsdr.so.0 (0xb6ee3000)
        libbladeRF.so.2 => /lib/arm-linux-gnueabihf/libbladeRF.so.2 (0xb6e55000)
        libhackrf.so.0 => /lib/arm-linux-gnueabihf/libhackrf.so.0 (0xb6e3f000)
        libLimeSuite.so.20.10-1 => /lib/arm-linux-gnueabihf/libLimeSuite.so.20.10-1 (0xb6d91000)
        libncurses.so.6 => /lib/arm-linux-gnueabihf/libncurses.so.6 (0xb6d62000)
        libtinfo.so.6 => /lib/arm-linux-gnueabihf/libtinfo.so.6 (0xb6d30000)
        libc.so.6 => /lib/arm-linux-gnueabihf/libc.so.6 (0xb6bdc000)
        /lib/ld-linux-armhf.so.3 (0xb6fb1000)
        libusb-1.0.so.0 => /lib/arm-linux-gnueabihf/libusb-1.0.so.0 (0xb6bb4000)
        libatomic.so.1 => /lib/arm-linux-gnueabihf/libatomic.so.1 (0xb6b9b000)
        libstdc++.so.6 => /lib/arm-linux-gnueabihf/libstdc++.so.6 (0xb6a13000)
        libgcc_s.so.1 => /lib/arm-linux-gnueabihf/libgcc_s.so.1 (0xb69e6000)
        libdl.so.2 => /lib/arm-linux-gnueabihf/libdl.so.2 (0xb69d2000)
        libudev.so.1 => /lib/arm-linux-gnueabihf/libudev.so.1 (0xb699e000)

 

11

What is your point with this? :smiley:

Hard to find that download link doesn’t it? :rofl:

wget https://repo-feed.flightradar24.com/rpi_binaries/fr24feed_1.0.30-3_armhf.tgz

ldd ./fr24feed
not a dynamic executable

file ./fr24feed
./fr24feed: ELF 32-bit LSB executable, ARM, EABI5 version 1 (GNU/Linux), statically linked, BuildID[sha1]=59719f430b9e39cc87a7118893af0e70bd9df059, for GNU/Linux 3.2.0, stripped

 ./fr24feed 
libcommon read_config failed - /etc/fr24feed.ini
error | Local time: 2022-12-06 16:48:18 +0100
error | GMT+0 time: 2022-12-06 15:48:18 +0100
error | Your machine should be set as GMT+0 time zone!
warning | Time zone is not set to GMT+0
______  _  _         _      _                    _              _____    ___ 
|  ___|| |(_)       | |    | |                  | |            / __  \  /   |
| |_   | | _   __ _ | |__  | |_  _ __  __ _   __| |  __ _  _ __`' / /' / /| |
|  _|  | || | / _` || '_ \ | __|| '__|/ _` | / _` | / _` || '__| / /  / /_| |
| |    | || || (_| || | | || |_ | |  | (_| || (_| || (_| || |  ./ /___\___  |
\_|    |_||_| \__, ||_| |_| \__||_|   \__,_| \__,_| \__,_||_|  \_____/    |_/
               __/ |                                                         
              |___/                                                          
[main][i]FR24 Feeder/Decoder
[main][i]Version: 1.0.30-3/generic
[main][i]Built on Sep  1 2022 09:40:07 (HEAD-00021a4.git/Linux/static_armel)
[main][i]Running on: void

Wohohohoho. Literally took me 30 seconds to get this up and running and I already blow a whole afternoon on that piaware tcl garbage nowhere near to be working. It’s questionable if I want to keep feeding data into this project in the future for any reasons. To be honest I don’t know why I doing it currently either I hardly use any of these plane trackers, probably just for fun but this tcl fuckery is starting to be not so funny. :crazy_face:

I mean I remember the old eggdrop was written in TCL but who the hell is just using this dead language for anything these days.

12

@zymucicp

You will need to build 2 linux binaries if you want to upload data to Flightaware
piaware
faup1090

You will need 3rd binary if you want to participate in MLAT
fa-mlat-client

For example of building complete set, see below

 

 

 

 

13

Not at all hard to get armhf binary even if I dont know its direct download link.
Here is how I did it:
I have installed fr24feed on RPi using its .deb package, and can easily extract Linux binary from it by method shown in screenshot below:

CLICK ON SCREENSHOT TO SEE LARGER SIZE

image
image670×576 32.7 KB

 

 

pi@piaware:~ $ apt-cache policy fr24feed
fr24feed:
  Installed: 1.0.30-3
  Candidate: 1.0.30-3
  Version table:
 *** 1.0.30-3 500
        500 http://repo.feed.flightradar24.com flightradar24/raspberrypi-stable  armhf Packages
        100 /var/lib/dpkg/status

pi@piaware:~ $ ls *.deb
ls: cannot access '*.deb': No such file or directory


pi@piaware:~ $ sudo apt download fr24feed
Get:1 http://repo.feed.flightradar24.com flightradar24/raspberrypi-stable armhf  fr24feed armhf 1.0.30-3 [3,476 kB]
Fetched 3,476 kB in 1s (3,210 kB/s)
W: Download is performed unsandboxed as root as file '/home/pi/fr24feed_1.0.30-3 _armhf.deb' couldn't be accessed by user '_apt'. - pkgAcquire::Run (13: Permissi on denied)

pi@piaware:~ $ ls *.deb
fr24feed_1.0.30-3_armhf.deb

pi@piaware:~ $ sudo mkdir extracted
pi@piaware:~ $ ls extracted
pi@piaware:~ $ sudo dpkg -x fr24feed_1.0.30-3_armhf.deb extracted

pi@piaware:~ $ ls extracted/usr/bin/
fr24feed  fr24feed-status

pi@piaware:~ $ file extracted/usr/bin/fr24feed
extracted/usr/bin/fr24feed: ELF 32-bit LSB executable, ARM, EABI5 version 1 (GNU /Linux), statically linked, BuildID[sha1]=59719f430b9e39cc87a7118893af0e70bd9df0 59, for GNU/Linux 3.2.0, stripped

pi@piaware:~ $ ldd extracted/usr/bin/fr24feed
        not a dynamic executable
14

Again what’s your point copying that here when I said I get it working in couple of minutes, the topic is not about fr24 but piaware.

From what you posted:

depends=(‘git’ ‘autoconf’ ‘tcl’ ‘tcllib’ ‘tclx’ ‘tcltls’
‘python’ ‘tk’ ‘tcllauncher’ ‘net-tools’)

And here is the problem void linux don’t have tclx, tcllauncher and it’s an issue building them (this is might be the main reason why there is no void linux package :face_with_symbols_over_mouth:)

All the related packets to TCL:

[-] bwidget-1.9.14_2                 Set of extension widgets for Tcl/Tk
[-] jimtcl-0.81_1                    Small footprint implementation of the Tcl programming language
[-] jimtcl-devel-0.81_1              Small footprint implementation of the Tcl programming language -- development files
[-] nextcloud-client-3.6.2_1         NextCloud Desktop client
[-] nextcloud-client-devel-3.6.2_1   NextCloud Desktop client - development files
[-] nextcloud-client-dolphin-3.6.2_1 NextCloud Desktop client - KDE dolphin integration
[-] nextcloud-client-kwallet-3.6.2_1 NextCloud Desktop client - kwallet credential backend
[-] partclone-0.3.19_1               File system clone and restore utilities
[-] targetcli-fb-2.1.54_3            CLI for configuring the LIO generic SCSI target
[*] tcl-8.6.12_1                     TCL scripting language
[-] tcl-devel-8.6.12_1               TCL scripting language - development files
[-] tcllib-1.21_1                    Set of pure-Tcl extensions
[-] tcltls-1.7.22_1                  Binding to OpenSSL toolkit
[-] tk-8.6.12_1                      TK graphical user interface toolkit for TCL
[-] tk-devel-8.6.12_1                TK graphical user interface toolkit for TCL - development files
[-] tklib-0.7_1                      Companion to Tcllib, for Tk related packages
[-] weechat-tcl-3.7.1_2              Fast, light and extensible IRC client - tcl plugin
[-] znc-tcl-1.8.2_13                 Advanced IRC Bouncer - tcl plugin
16

@zymucicp

TL;DR

Either quit Void Linux and use another Linux OS which is compatible to piaware

OR

If you want to continue using Void Linux, then quit trying to feed Flightaware.

17

OR

Wait until devs make a void linux package :smiling_imp:

You would be surprised how often option 3 works if you have patience. :stuck_out_tongue_winking_eye:

1 Like
18

Then you should point your request for “piaware arm binary with Statically Linked Libraries” to developers @obj and @eric1tran .

They may:

  • Either make this binary available at Flightawate site
    OR
  • May guide you how to build it yourself.

Of-course you cannot build piaware on Void Linux due to missing dependencies.
However you may build the piaware binary with statically linked libraries on “RPi with RaspberryPi OS”, as this will have all the required dependencies.

Once you have built piaware binary with statically Linked Libraries on RPi/RaspberryPiOS, you can SCP it to Box with Void Linux.

1 Like
19

No plans to do this currently.

A static binary is not a terrible idea but there are some fairly large technical obstacles to it.

2 Likes
20

This topic was automatically closed 365 days after the last reply. New replies are no longer allowed.