Hi Sanni
Read simpler alternative solution belowI am going to dare a rather cryptic solution below. Note that
I HAVE NOT TESTED THIS since I compiled myself the corrected binary 2016.3.
I believe it can work on Linux systems.
* Need to replace /path/to/bin with whatever is the proper binary path in your system (where fgfs is stored); if in doubt, check
1. Backup!
beware we are risking the binary with the following steps
Code: Select all
cd ~/ #best executed as regular user at home
cp /path/to/bin/fgfs ./fgfs.bk -vi
cp /path/to/bin/fgfs ./fgfs -vi
With this step above you created the file fgfs.bk which is the safe backup of the fgfs binary.
If we mess up you can restore like
2. Edit the binaryWe will hexdump the binary first (hexdump), then replace (sed), and then restore the binary (xxd)
Note1: It is a single command
Note2: You really want to use the copy/paste method here, since this is not typo-friendly --beside looking like chicken-scratch.
Code: Select all
hexdump -ve '1/1 "%.2X"' fgfs | \
sed "s@http://weather.noaa.gov/pub/data/observations/metar/stations/@http://tgftp.nws.noaa.gov/data/observations/metar//stations//@g" | \
xxd -r -p > fgfs.patched
Now you have 3 fgfs files. The original (fgfs) the backup (fgfs.bk) and the edited (fgfs.patched)
Simply replace the original with the edited, and try your patched file
Code: Select all
sudo cp fgfs.patched /path/to/bin/fgfs -vi
fgfs
Let us know if this gets you back in byzz.
IH-COL
