I am trying to get dump978-fa (GitHub - flightaware/dump978: FlightAware's 978MHz UAT demodulator)
working on linux debian buster. Whenever I run the makefile it is giving me and error reading " error: redefinition of class boost::system::system_error’
Here is the error:
What is the best way around this?
Please post details (including the boost dev package versions you have installed) in an issue on github.
I’m not aware of any build problems on buster, and we do automated package builds for buster, so it’s probably specific to your environment.
(1) Building dump978-fa is memory intensive. I failed to build it on Pi with 1 GB ram. I could succeed only when I used RPi Model4 with 4 GB ram.
(2) I successfully build the debian package for dump987-fa on RPi Model4 with 4GB ram using following script:
sudo bash -c "$(wget -O - https://raw.githubusercontent.com/abcd567a/piaware-ubuntu-debian-amd64/master/install-dump978-fa.sh)"
This script detects OS version and can build the package on Stretch, Buster, and Bullseye., armhf, arm64, aarch64 and amd64 machines
The script in my above post installs following packages before building the debian package of dump978-fa:
##Build-Tools:
sudo apt install -y git
sudo apt install -y build-essential
sudo apt install -y devscripts
##Build-Depends:
sudo apt install -y debhelper
sudo apt install -y libboost-system-dev
sudo apt install -y libboost-program-options-dev
sudo apt install -y libboost-regex-dev
sudo apt install -y libboost-filesystem-dev
sudo apt install -y libsoapysdr-dev
##Depends:
sudo apt install -y adduser
sudo apt install -y soapysdr-module-rtlsdr
sudo apt install -y lighttpd
Just now wrote Raspberry Pi OS Buster to microSD card and successfully built and installed dump978-fa on it using the bash script in my previous post.
The dump1090-fa fails to build on Raspberry Pi OS Buster image dated 2023-05-23 , possibly because of architecture confusion (aarch64 and armhf)
Yeah, this is likely because uname -m doesn’t name the userspace architecture. This isn’t limited to arm (though the x86-64 / amd64 confusion doesn’t break things currently):
$ dpkg --print-architecture
amd64
$ uname -m
x86_64
There’s a fix for this in the dev branch. but please report this type of build problem on github …
This topic was automatically closed 365 days after the last reply. New replies are no longer allowed.