I found if installing from the tar.gz file download, I am able to run the ../configure command in the build folder. Output is as follows:
dominick@dominick-AOA150:~/Xastir-Release-2.1.4/build$ ../configure checking for a BSD-compatible install... /usr/bin/install -c checking whether build environment is sane... yes checking for a thread-safe mkdir -p... /bin/mkdir -p checking for gawk... gawk checking whether make sets $(MAKE)... yes checking whether make supports nested variables... yes checking whether make supports nested variables... (cached) yes Configuring xastir 2.1.4 checking build system type... i686-pc-linux-gnu checking host system type... i686-pc-linux-gnu checking whether make supports the include directive... yes (GNU style) checking for gcc... gcc checking whether the C compiler works... yes checking for C compiler default output file name... a.out checking for suffix of executables... checking whether we are cross compiling... no checking for suffix of object files... o checking whether we are using the GNU C compiler... yes checking whether gcc accepts -g... yes checking for gcc option to accept ISO C89... none needed checking whether gcc understands -c and -o together... yes checking dependency style of gcc... gcc3 checking dependency style of gcc... (cached) gcc3 checking how to run the C preprocessor... gcc -E checking for grep that handles long lines and -e... /bin/grep checking for egrep... /bin/grep -E checking for ANSI C header files... yes checking for sys/types.h... yes checking for sys/stat.h... yes checking for stdlib.h... yes checking for string.h... yes checking for memory.h... yes checking for strings.h... yes checking for inttypes.h... yes checking for stdint.h... yes checking for unistd.h... yes checking minix/config.h usability... no checking minix/config.h presence... no checking for minix/config.h... no checking whether it is safe to define __EXTENSIONS__... yes checking for gcc... (cached) gcc checking whether we are using the GNU C compiler... (cached) yes checking whether gcc accepts -g... (cached) yes checking for gcc option to accept ISO C89... (cached) none needed checking whether gcc understands -c and -o together... (cached) yes checking dependency style of gcc... (cached) gcc3 checking dependency style of gcc... (cached) gcc3 checking how to run the C preprocessor... gcc -E checking whether ln -s works... yes checking whether make sets $(MAKE)... (cached) yes checking for gawk... (cached) gawk checking for ranlib... ranlib checking for devices... found /dev/ttyS0 and /dev/ttyS1 checking for search paths... done checking for the pthreads library -lpthreads... no checking whether pthreads work without any flags... no checking whether pthreads work with -Kthread... no checking whether pthreads work with -kthread... no checking for the pthreads library -llthread... no checking whether pthreads work with -pthread... yes checking for joinable pthread attribute... PTHREAD_CREATE_JOINABLE checking if more special flags are required for pthreads... no checking for cc_r... gcc checking whether compiler accepts -Wno-unused-parameter... yes checking for compiler flags... using -g -O2 -pipe -W -Wall -Wpointer-arith -Wstrict-prototypes -Wno-unused-parameter -pthread checking for system... Linux checking for gm... no checking for /usr/bin/gm.exe... no checking for convert... /usr/bin/convert checking for /usr/bin/convert.exe... no checking for lpr... /usr/bin/lpr checking for gv... no checking for festival... /usr/bin/festival checking for gpsman... /usr/bin/gpsman checking for X... libraries , headers checking for gethostbyname... yes checking for connect... yes checking for remove... yes checking for shmat... yes checking for IceConnectionNumber in -lICE... yes checking for library containing tan... -lm checking for XextAddDisplay in -lXext... yes checking for XtDisplay in -lXt... no checking for XmTextFindString in -lXm... no checking for sed... /bin/sed checking for mv... /bin/mv checking for xfontsel... /usr/bin/xfontsel checking curl/curl.h usability... no checking curl/curl.h presence... no checking for curl/curl.h... no checking for wget... /usr/bin/wget checking for main in -lcompat... no checking for sched_yield in -lrt... yes checking whether byte ordering is bigendian... no checking for Motif headers... configure: error: **** NO MOTIF HEADERS FOUND **** install Motif development headers or use --with-motif-includes to specify location of Xm/Xm.h Unfortunately my success was short lived, now it hangs up at the "make" command. The only variable I changed was installing from "Xastir-Release-2.1.4 tar.gz file, from the git clone download. dominick@dominick-AOA150:~/Xastir-Release-2.1.4/build$ make make: *** No targets specified and no makefile found. Stop. dominick@dominick-AOA150:~/Xastir-Release-2.1.4/build$ Interestingly, I replicated both installation procedures on this machine (Acer Aspire One with Xubuntu) and my Raspberry pi 3B. Both ended up with the same result. I was sure update, upgrade, and install all packages in both instances. There must be something I am missing. Thank you, Dominick On Sun, Jan 5, 2020 at 6:33 PM <xastir-requ...@lists.xastir.org> wrote: > Send Xastir mailing list submissions to > xastir@lists.xastir.org > > To subscribe or unsubscribe via the World Wide Web, visit > http://xastir.org/mailman/listinfo/xastir > or, via email, send a message with subject or body 'help' to > xastir-requ...@lists.xastir.org > > You can reach the person managing the list at > xastir-ow...@lists.xastir.org > > When replying, please edit your Subject line so it is more specific > than "Re: Contents of Xastir digest..." > > > Today's Topics: > > 1. Re: Xastir Digest, Vol 689, Issue 1 (Dominick Spina) > 2. Re: Xastir Digest, Vol 689, Issue 1 (Lee D Bengston) > > > ---------------------------------------------------------------------- > > Message: 1 > Date: Sun, 5 Jan 2020 17:58:19 -0500 > From: Dominick Spina <dom...@gmail.com> > To: xastir@lists.xastir.org > Subject: Re: [Xastir] Xastir Digest, Vol 689, Issue 1 > Message-ID: > < > caa4_0xexmfbksjbgu6nu7m9qcvrxhxzonvjhnc5o0bvzoji...@mail.gmail.com> > Content-Type: text/plain; charset="UTF-8" > > Lee, > > I have started a fresh install in my home directory without using sudo > privileges as you recommended. I deleted the files from the previous > install in the usr/local/bin directory. > > I am still getting the same problem with ../configure. I am not able to > make it to the sudo make install step. > > I did try running ./update-xastir and received this output: > > dominick@dominick-AOA150:~/Xastir$ ./update-xastir > > Sun Jan 5 17:47:17 EST 2020 > > Already up to date. > > > > > > Sun Jan 5 17:47:18 EST 2020 > > 6) Removing autom4te.cache directory... > > 5) Running aclocal... > > ./bootstrap.sh: 15: ./bootstrap.sh: aclocal: not found > > 4) Running autoheader... > > ./bootstrap.sh: 18: ./bootstrap.sh: autoheader: not found > > 3) Running autoconf... > > ./bootstrap.sh: 21: ./bootstrap.sh: autoconf: not found > > 2) Running automake... > > ./bootstrap.sh: 25: ./bootstrap.sh: automake: not found > > 1) Generating derived language files..... > > Bootstrap complete. > > > > > > Sun Jan 5 17:47:19 EST 2020 > > > > > > Sun Jan 5 17:47:19 EST 2020 > > ./update-xastir: 38: ./update-xastir: ../configure: not found > > > > > > Sun Jan 5 17:47:19 EST 2020 > > ************************************************ > > Building for Unix/Linux/MacOSX Operating Systems > > ************************************************ > > [sudo] password for dominick: > > make: *** No rule to make target 'clean'. Stop. > > > > > > Sun Jan 5 17:47:23 EST 2020 > > make: *** No targets specified and no makefile found. Stop. > > make: *** No rule to make target 'install-strip'. Stop. > > chmod: cannot access '/usr/local/bin/xastir': No such file or directory > > > > Sun Jan 5 17:47:23 EST 2020 > > dominick@dominick-AOA150:~/Xastir$ > > > > > When I try to use ../configure, build, or make command, I get this: > > > > dominick@dominick-AOA150:~/Xastir$ cd build > > dominick@dominick-AOA150:~/Xastir/build$ ../configure > > bash: ../configure: No such file or directory > > dominick@dominick-AOA150:~/Xastir/build$ > > > KB1WOH > > On Sun, Jan 5, 2020 at 4:42 PM <xastir-requ...@lists.xastir.org> wrote: > > > Send Xastir mailing list submissions to > > xastir@lists.xastir.org > > > > To subscribe or unsubscribe via the World Wide Web, visit > > http://xastir.org/mailman/listinfo/xastir > > or, via email, send a message with subject or body 'help' to > > xastir-requ...@lists.xastir.org > > > > You can reach the person managing the list at > > xastir-ow...@lists.xastir.org > > > > When replying, please edit your Subject line so it is more specific > > than "Re: Contents of Xastir digest..." > > > > > > Today's Topics: > > > > 1. Re: Xastir weather alerts (Curt Mills) > > 2. Re: Xastir weather alerts (Apostolos Kefalas) > > 3. Re: Xastir weather alerts (Apostolos Kefalas) > > 4. Re: Xastir weather alerts (David A Aitcheson) > > 5. Installation help with Xubuntu (Dominick Spina) > > 6. Re: Installation help with Xubuntu (Lee D Bengston) > > > > > > ---------------------------------------------------------------------- > > > > Message: 1 > > Date: Sun, 29 Dec 2019 12:17:05 -0700 > > From: Curt Mills <curt.w...@gmail.com> > > To: km5vy Tom Russo <ru...@bogodyn.org>, Xastir - APRS client > > software discussion <xastir@lists.xastir.org>, xas...@xastir.org > > Subject: Re: [Xastir] Xastir weather alerts > > Message-ID: > > < > > cakdpqxkog0ya+osfaa26gs+8ln_2pyhkrckevn7qk-pyfqt...@mail.gmail.com> > > Content-Type: text/plain; charset="UTF-8" > > > > Thanks Tom! > > > > On Sun, Dec 29, 2019, 11:35 AM Tom Russo <ru...@bogodyn.org> wrote: > > > > > On Sun, Dec 29, 2019 at 11:15:33AM -0700, we recorded a bogon-computron > > > collision of the <ru...@bogodyn.org> flavor, containing: > > > > It looks like some of the work cleaning up compiler warnings resulted > > in > > > > broken code to concatenate strings. > > > > > > > > I'm looking into it. It may take a while. > > > > > > Or not. Found the spot where things were being done wrong, and it was > > > indeed > > > the result of a broken cleanup of compiler warnings in the alerts code. > > > The > > > fix should be on github as of now. > > > > > > > On Sun, Dec 29, 2019 at 11:08:32AM -0700, we recorded a > bogon-computron > > > collision of the <ru...@bogodyn.org> flavor, containing: > > > > > In a recent message, Apostolos Kefalas asked: > > > > > > > > > > Hello all, > > > > > > > > > > > > > > > I am on Xastir v2.1.3 (6884c6f9) and now I have noticed that the > > > > > weather alert list (View -> Weather Alerts) is not showing all the > > > > > data. > > > > > > > > > > I remember in older versions of Xastir we could see the type of > > alert, > > > > > expiration time and area codes. > > > > > > > > > > Happy New Year to All > > > > > > > > > > Apostolos, SV1LJJ > > > > > > > > > > ---- > > > > > > > > > > It looks suspiciously like something has changed in the data coming > > in > > > related > > > > > to weather alerts, and xastir is improperly parsing it. > > > > > > > > > > For example, a quick view of my net feed shows this packet coming > in: > > > > > > > > > > UNRWSW>APRS,TCPIP,qAO,WE7U-WX::NWS-WARN > > > :300100z,WINTER_WEATHER,SDZ14-31-32-41>44 {THj1D > > > > > > > > > > But all that shows up in the weather alerts box is: > > > > > > > > > > UNRWSW THj1D NWS-WARN z > > > > > > > > > > Somehow that incoming data is not properly being parsed anymore. > > Most > > > of the > > > > > alerts I find in my wx alerts dialog look like this, with a few > extra > > > > > adornments, like: > > > > > > > > > > ABRWSW T3Y4B NWS-WARN 03 @z > > > > > > > > > > Very, very few have full data, but some do: > > > > > SGFFLS 10020 NWS_ADVIS 01 @0000z ==> 03 @0224z NI MO_C185 FLOOD > > > > > > > > > > Whether this is a change in the incoming data formatting or > something > > > broken > > > > > in Xastir's code is another question. Looks like we need a deep > dive > > > into > > > > > the alert parsing code to see if there are changes necessary. The > > > alert code > > > > > has not had meaningful changes in a very long time. There was some > > > effort > > > > > to eliminate compiler warnings in 2017 and again earlier this year, > > > but those > > > > > should not have changed functionality. > > > > > > > > > > However, Xastir does have an NWS-TEST.log file that we're supposed > to > > > be > > > > > able to read in and get alerts, and when I read it in it shows up > as > > > garbled > > > > > alerts just like the new ones have. > > > > > > > > > > Interestingly enough, though, when I read in NWS-TEST.log the > alerts > > > do show > > > > > up on the map. The data is just missing in the alert dialog box. > > > > > > > > > > So it looks like something got mangled in the code where data is > > > parsed out > > > > > for display in the dialog, but there is enough information getting > > > decoded to > > > > > display it on the map. > > > > > > > > > > > > > > > -- > > > > > Tom Russo KM5VY > > > > > Tijeras, NM > > > > > > > > > > echo "prpv_a'rfg_cnf_har_cvcr" | sed -e 's/_/ /g' | tr [a-m][n-z] > > > [n-z][a-m] > > > > > > > > > > _______________________________________________ > > > > > Xastir mailing list > > > > > Xastir@lists.xastir.org > > > > > http://xastir.org/mailman/listinfo/xastir > > > > > > > > -- > > > > Tom Russo KM5VY > > > > Tijeras, NM > > > > > > > > echo "prpv_a'rfg_cnf_har_cvcr" | sed -e 's/_/ /g' | tr [a-m][n-z] > > > [n-z][a-m] > > > > > > > > _______________________________________________ > > > > Xastir mailing list > > > > Xastir@lists.xastir.org > > > > http://xastir.org/mailman/listinfo/xastir > > > > > > -- > > > Tom Russo KM5VY > > > Tijeras, NM > > > > > > echo "prpv_a'rfg_cnf_har_cvcr" | sed -e 's/_/ /g' | tr [a-m][n-z] > > > [n-z][a-m] > > > > > > _______________________________________________ > > > Xastir mailing list > > > Xastir@lists.xastir.org > > > http://xastir.org/mailman/listinfo/xastir > > > > > > > > > ------------------------------ > > > > Message: 2 > > Date: Sun, 29 Dec 2019 21:37:20 +0200 > > From: Apostolos Kefalas <sv1...@raag.org> > > To: ru...@bogodyn.org, Xastir - APRS client software discussion > > <xastir@lists.xastir.org>, xas...@xastir.org > > Subject: Re: [Xastir] Xastir weather alerts > > Message-ID: <15cb9d1ce392e67db409f6ece97836ee6ca3c75e.ca...@raag.org> > > Content-Type: text/plain; charset="UTF-8" > > > > Works great. > > > > Thanks!!! > > > > On Sun, 2019-12-29 at 11:35 -0700, Tom Russo wrote: > > > On Sun, Dec 29, 2019 at 11:15:33AM -0700, we recorded a bogon- > > > computron collision of the <ru...@bogodyn.org> flavor, containing: > > > > It looks like some of the work cleaning up compiler warnings > > > > resulted in > > > > broken code to concatenate strings. > > > > > > > > I'm looking into it. It may take a while. > > > > > > Or not. Found the spot where things were being done wrong, and it > > > was indeed > > > the result of a broken cleanup of compiler warnings in the alerts > > > code. The > > > fix should be on github as of now. > > > > > > > On Sun, Dec 29, 2019 at 11:08:32AM -0700, we recorded a bogon- > > > > computron collision of the <ru...@bogodyn.org> flavor, containing: > > > > > In a recent message, Apostolos Kefalas asked: > > > > > > > > > > Hello all, > > > > > > > > > > > > > > > I am on Xastir v2.1.3 (6884c6f9) and now I have noticed that the > > > > > weather alert list (View -> Weather Alerts) is not showing all > > > > > the > > > > > data. > > > > > > > > > > I remember in older versions of Xastir we could see the type of > > > > > alert, > > > > > expiration time and area codes. > > > > > > > > > > Happy New Year to All > > > > > > > > > > Apostolos, SV1LJJ > > > > > > > > > > ---- > > > > > > > > > > It looks suspiciously like something has changed in the data > > > > > coming in related > > > > > to weather alerts, and xastir is improperly parsing it. > > > > > > > > > > For example, a quick view of my net feed shows this packet coming > > > > > in: > > > > > > > > > > UNRWSW>APRS,TCPIP,qAO,WE7U-WX::NWS-WARN > > > > > :300100z,WINTER_WEATHER,SDZ14-31-32-41>44 {THj1D > > > > > > > > > > But all that shows up in the weather alerts box is: > > > > > > > > > > UNRWSW THj1D NWS-WARN z > > > > > > > > > > Somehow that incoming data is not properly being parsed > > > > > anymore. Most of the > > > > > alerts I find in my wx alerts dialog look like this, with a few > > > > > extra > > > > > adornments, like: > > > > > > > > > > ABRWSW T3Y4B NWS-WARN 03 @z > > > > > > > > > > Very, very few have full data, but some do: > > > > > SGFFLS 10020 NWS_ADVIS 01 @0000z ==> 03 @0224z NI MO_C185 FLOOD > > > > > > > > > > Whether this is a change in the incoming data formatting or > > > > > something broken > > > > > in Xastir's code is another question. Looks like we need a deep > > > > > dive into > > > > > the alert parsing code to see if there are changes > > > > > necessary. The alert code > > > > > has not had meaningful changes in a very long time. There was > > > > > some effort > > > > > to eliminate compiler warnings in 2017 and again earlier this > > > > > year, but those > > > > > should not have changed functionality. > > > > > > > > > > However, Xastir does have an NWS-TEST.log file that we're > > > > > supposed to be > > > > > able to read in and get alerts, and when I read it in it shows up > > > > > as garbled > > > > > alerts just like the new ones have. > > > > > > > > > > Interestingly enough, though, when I read in NWS-TEST.log the > > > > > alerts do show > > > > > up on the map. The data is just missing in the alert dialog box. > > > > > > > > > > So it looks like something got mangled in the code where data is > > > > > parsed out > > > > > for display in the dialog, but there is enough information > > > > > getting decoded to > > > > > display it on the map. > > > > > > > > > > > > > > > -- > > > > > Tom Russo KM5VY > > > > > Tijeras, NM > > > > > > > > > > echo "prpv_a'rfg_cnf_har_cvcr" | sed -e 's/_/ /g' | tr [a-m][n- > > > > > z] [n-z][a-m] > > > > > > > > > > _______________________________________________ > > > > > Xastir mailing list > > > > > Xastir@lists.xastir.org > > > > > http://xastir.org/mailman/listinfo/xastir > > > > > > > > -- > > > > Tom Russo KM5VY > > > > Tijeras, NM > > > > > > > > echo "prpv_a'rfg_cnf_har_cvcr" | sed -e 's/_/ /g' | tr [a-m][n-z] > > > > [n-z][a-m] > > > > > > > > _______________________________________________ > > > > Xastir mailing list > > > > Xastir@lists.xastir.org > > > > http://xastir.org/mailman/listinfo/xastir > > > > > > > > > > > > ------------------------------ > > > > Message: 3 > > Date: Sun, 29 Dec 2019 21:37:20 +0200 > > From: Apostolos Kefalas <sv1...@raag.org> > > To: ru...@bogodyn.org, Xastir - APRS client software discussion > > <xastir@lists.xastir.org>, xas...@xastir.org > > Subject: Re: [Xastir] Xastir weather alerts > > Message-ID: <15cb9d1ce392e67db409f6ece97836ee6ca3c75e.ca...@raag.org> > > Content-Type: text/plain; charset="UTF-8" > > > > Works great. > > > > Thanks!!! > > > > On Sun, 2019-12-29 at 11:35 -0700, Tom Russo wrote: > > > On Sun, Dec 29, 2019 at 11:15:33AM -0700, we recorded a bogon- > > > computron collision of the <ru...@bogodyn.org> flavor, containing: > > > > It looks like some of the work cleaning up compiler warnings > > > > resulted in > > > > broken code to concatenate strings. > > > > > > > > I'm looking into it. It may take a while. > > > > > > Or not. Found the spot where things were being done wrong, and it > > > was indeed > > > the result of a broken cleanup of compiler warnings in the alerts > > > code. The > > > fix should be on github as of now. > > > > > > > On Sun, Dec 29, 2019 at 11:08:32AM -0700, we recorded a bogon- > > > > computron collision of the <ru...@bogodyn.org> flavor, containing: > > > > > In a recent message, Apostolos Kefalas asked: > > > > > > > > > > Hello all, > > > > > > > > > > > > > > > I am on Xastir v2.1.3 (6884c6f9) and now I have noticed that the > > > > > weather alert list (View -> Weather Alerts) is not showing all > > > > > the > > > > > data. > > > > > > > > > > I remember in older versions of Xastir we could see the type of > > > > > alert, > > > > > expiration time and area codes. > > > > > > > > > > Happy New Year to All > > > > > > > > > > Apostolos, SV1LJJ > > > > > > > > > > ---- > > > > > > > > > > It looks suspiciously like something has changed in the data > > > > > coming in related > > > > > to weather alerts, and xastir is improperly parsing it. > > > > > > > > > > For example, a quick view of my net feed shows this packet coming > > > > > in: > > > > > > > > > > UNRWSW>APRS,TCPIP,qAO,WE7U-WX::NWS-WARN > > > > > :300100z,WINTER_WEATHER,SDZ14-31-32-41>44 {THj1D > > > > > > > > > > But all that shows up in the weather alerts box is: > > > > > > > > > > UNRWSW THj1D NWS-WARN z > > > > > > > > > > Somehow that incoming data is not properly being parsed > > > > > anymore. Most of the > > > > > alerts I find in my wx alerts dialog look like this, with a few > > > > > extra > > > > > adornments, like: > > > > > > > > > > ABRWSW T3Y4B NWS-WARN 03 @z > > > > > > > > > > Very, very few have full data, but some do: > > > > > SGFFLS 10020 NWS_ADVIS 01 @0000z ==> 03 @0224z NI MO_C185 FLOOD > > > > > > > > > > Whether this is a change in the incoming data formatting or > > > > > something broken > > > > > in Xastir's code is another question. Looks like we need a deep > > > > > dive into > > > > > the alert parsing code to see if there are changes > > > > > necessary. The alert code > > > > > has not had meaningful changes in a very long time. There was > > > > > some effort > > > > > to eliminate compiler warnings in 2017 and again earlier this > > > > > year, but those > > > > > should not have changed functionality. > > > > > > > > > > However, Xastir does have an NWS-TEST.log file that we're > > > > > supposed to be > > > > > able to read in and get alerts, and when I read it in it shows up > > > > > as garbled > > > > > alerts just like the new ones have. > > > > > > > > > > Interestingly enough, though, when I read in NWS-TEST.log the > > > > > alerts do show > > > > > up on the map. The data is just missing in the alert dialog box. > > > > > > > > > > So it looks like something got mangled in the code where data is > > > > > parsed out > > > > > for display in the dialog, but there is enough information > > > > > getting decoded to > > > > > display it on the map. > > > > > > > > > > > > > > > -- > > > > > Tom Russo KM5VY > > > > > Tijeras, NM > > > > > > > > > > echo "prpv_a'rfg_cnf_har_cvcr" | sed -e 's/_/ /g' | tr [a-m][n- > > > > > z] [n-z][a-m] > > > > > > > > > > _______________________________________________ > > > > > Xastir mailing list > > > > > Xastir@lists.xastir.org > > > > > http://xastir.org/mailman/listinfo/xastir > > > > > > > > -- > > > > Tom Russo KM5VY > > > > Tijeras, NM > > > > > > > > echo "prpv_a'rfg_cnf_har_cvcr" | sed -e 's/_/ /g' | tr [a-m][n-z] > > > > [n-z][a-m] > > > > > > > > _______________________________________________ > > > > Xastir mailing list > > > > Xastir@lists.xastir.org > > > > http://xastir.org/mailman/listinfo/xastir > > > > > > > > > > > > ------------------------------ > > > > Message: 4 > > Date: Sun, 29 Dec 2019 15:41:11 -0500 > > From: David A Aitcheson <david.aitche...@gmail.com> > > To: xas...@xastir.org > > Subject: Re: [Xastir] Xastir weather alerts > > Message-ID: <e3bcf36e-d0fd-8639-9154-5a92775f5...@gmail.com> > > Content-Type: text/plain; charset=windows-1252 > > > > Confirming all is working correctly on Ubuntu 14.04-?-LTS > > > > Thank You Tom! > > > > 73 > > Dave > > KB3EFS > > > > > > On 12/29/19 1:35 PM, Tom Russo wrote: > > > On Sun, Dec 29, 2019 at 11:15:33AM -0700, we recorded a bogon-computron > > collision of the <ru...@bogodyn.org> flavor, containing: > > >> It looks like some of the work cleaning up compiler warnings resulted > in > > >> broken code to concatenate strings. > > >> > > >> I'm looking into it. It may take a while. > > > Or not. Found the spot where things were being done wrong, and it was > > indeed > > > the result of a broken cleanup of compiler warnings in the alerts code. > > The > > > fix should be on github as of now. > > > > > >> On Sun, Dec 29, 2019 at 11:08:32AM -0700, we recorded a > bogon-computron > > collision of the <ru...@bogodyn.org> flavor, containing: > > >>> In a recent message, Apostolos Kefalas asked: > > >>> > > >>> Hello all, > > >>> > > >>> > > >>> I am on Xastir v2.1.3 (6884c6f9) and now I have noticed that the > > >>> weather alert list (View -> Weather Alerts) is not showing all the > > >>> data. > > >>> > > >>> I remember in older versions of Xastir we could see the type of > alert, > > >>> expiration time and area codes. > > >>> > > >>> Happy New Year to All > > >>> > > >>> Apostolos, SV1LJJ > > >>> > > >>> ---- > > >>> > > >>> It looks suspiciously like something has changed in the data coming > in > > related > > >>> to weather alerts, and xastir is improperly parsing it. > > >>> > > >>> For example, a quick view of my net feed shows this packet coming in: > > >>> > > >>> UNRWSW>APRS,TCPIP,qAO,WE7U-WX::NWS-WARN > > :300100z,WINTER_WEATHER,SDZ14-31-32-41>44 {THj1D > > >>> > > >>> But all that shows up in the weather alerts box is: > > >>> > > >>> UNRWSW THj1D NWS-WARN z > > >>> > > >>> Somehow that incoming data is not properly being parsed anymore. > Most > > of the > > >>> alerts I find in my wx alerts dialog look like this, with a few extra > > >>> adornments, like: > > >>> > > >>> ABRWSW T3Y4B NWS-WARN 03 @z > > >>> > > >>> Very, very few have full data, but some do: > > >>> SGFFLS 10020 NWS_ADVIS 01 @0000z ==> 03 @0224z NI MO_C185 FLOOD > > >>> > > >>> Whether this is a change in the incoming data formatting or something > > broken > > >>> in Xastir's code is another question. Looks like we need a deep dive > > into > > >>> the alert parsing code to see if there are changes necessary. The > > alert code > > >>> has not had meaningful changes in a very long time. There was some > > effort > > >>> to eliminate compiler warnings in 2017 and again earlier this year, > > but those > > >>> should not have changed functionality. > > >>> > > >>> However, Xastir does have an NWS-TEST.log file that we're supposed to > > be > > >>> able to read in and get alerts, and when I read it in it shows up as > > garbled > > >>> alerts just like the new ones have. > > >>> > > >>> Interestingly enough, though, when I read in NWS-TEST.log the alerts > > do show > > >>> up on the map. The data is just missing in the alert dialog box. > > >>> > > >>> So it looks like something got mangled in the code where data is > > parsed out > > >>> for display in the dialog, but there is enough information getting > > decoded to > > >>> display it on the map. > > >>> > > >>> > > >>> -- > > >>> Tom Russo KM5VY > > >>> Tijeras, NM > > >>> > > >>> echo "prpv_a'rfg_cnf_har_cvcr" | sed -e 's/_/ /g' | tr [a-m][n-z] > > [n-z][a-m] > > >>> > > >>> _______________________________________________ > > >>> Xastir mailing list > > >>> Xastir@lists.xastir.org > > >>> http://xastir.org/mailman/listinfo/xastir > > >> -- > > >> Tom Russo KM5VY > > >> Tijeras, NM > > >> > > >> echo "prpv_a'rfg_cnf_har_cvcr" | sed -e 's/_/ /g' | tr [a-m][n-z] > > [n-z][a-m] > > >> > > >> _______________________________________________ > > >> Xastir mailing list > > >> Xastir@lists.xastir.org > > >> http://xastir.org/mailman/listinfo/xastir > > > > > > > > ------------------------------ > > > > Message: 5 > > Date: Sun, 5 Jan 2020 16:18:23 -0500 > > From: Dominick Spina <dom...@gmail.com> > > To: xastir@lists.xastir.org > > Subject: [Xastir] Installation help with Xubuntu > > Message-ID: > > <CAA4_0XEHc=fthiy+GWgxoKPMV1S3v0MeOJGRF3ms6NM= > > 6tc...@mail.gmail.com> > > Content-Type: text/plain; charset="UTF-8" > > > > Hello all, > > > > I am hitting a roadblock with a new installation of Xastir. > > > > The steps I am taking are: > > > > Download Xastir git file to /usr/local/bin > > Run bootstrap.sh > > mkdir -p build > > cd build > > ../configure > > > > When I enter ../configure in the build folder, I get a bash "no such file > > or directory". > > > > I am not an expert with Linux... am I doing something wrong? The OS is > > Xubuntu 18.04. I am using the instructions for Ubuntu 14.04-17.04 and the > > github install instructions page. > > > > Thank you, > > > > Dominick KB1WOH > > > > > > ------------------------------ > > > > Message: 6 > > Date: Sun, 5 Jan 2020 15:42:13 -0600 > > From: Lee D Bengston <kilo5...@gmail.com> > > To: Xastir - APRS client software discussion <xastir@lists.xastir.org> > > Subject: Re: [Xastir] Installation help with Xubuntu > > Message-ID: > > <CAPtjYAi+oQbrf56P52drXraxC82bhVRkAO7NC+ebueEeW= > > p...@mail.gmail.com> > > Content-Type: text/plain; charset="UTF-8" > > > > On Sun, Jan 5, 2020 at 3:18 PM Dominick Spina <dom...@gmail.com> wrote: > > > > > Hello all, > > > > > > I am hitting a roadblock with a new installation of Xastir. > > > > > > The steps I am taking are: > > > > > > Download Xastir git file to /usr/local/bin > > > > > Hello Dominick, you should download Xastir from Github into either your > > home directory or a directory that is underneath your home directory. > Then > > from there you want to make sure you are not executing any of the > commands > > as root, i.e. do not use sudo. Your user in Xubuntu cannot write to > > /usr/local/bin, so you do not want the source code downloaded there. > > > > > Run bootstrap.sh > > > mkdir -p build > > > cd build > > > ../configure > > > > > > > So I would pull the code (via git) from somewhere under your home > directory > > and retry the steps from there. When you get to the "sudo make install" > > step, that's when the xastir executable gets installed in /usr/local/bin, > > and in that case you are not specifying that directory - the script does > > that by default. > > > > 73, > > Lee K5DAT > > > > > > ------------------------------ > > > > Subject: Digest Footer > > > > _______________________________________________ > > Xastir mailing list > > Xastir@lists.xastir.org > > http://xastir.org/mailman/listinfo/xastir > > > > > > ------------------------------ > > > > End of Xastir Digest, Vol 689, Issue 1 > > ************************************** > > > > > ------------------------------ > > Message: 2 > Date: Sun, 5 Jan 2020 17:33:02 -0600 > From: Lee D Bengston <kilo5...@gmail.com> > To: Xastir - APRS client software discussion <xastir@lists.xastir.org> > Subject: Re: [Xastir] Xastir Digest, Vol 689, Issue 1 > Message-ID: > < > captjyai3mgsnfdz+4uf6czwsdyflztwaf3b14vnegfwt+up...@mail.gmail.com> > Content-Type: text/plain; charset="UTF-8" > > On Sun, Jan 5, 2020 at 4:58 PM Dominick Spina <dom...@gmail.com> wrote: > > > Lee, > > > > I have started a fresh install in my home directory without using sudo > > privileges as you recommended. I deleted the files from the previous > > install in the usr/local/bin directory. > > > > I am still getting the same problem with ../configure. I am not able to > > make it to the sudo make install step. > > > > I did try running ./update-xastir and received this output: > > > > dominick@dominick-AOA150:~/Xastir$ ./update-xastir > > > > Sun Jan 5 17:47:17 EST 2020 > > > > Already up to date. > > > > > > Sun Jan 5 17:47:18 EST 2020 > > > > 6) Removing autom4te.cache directory... > > > > 5) Running aclocal... > > > > ./bootstrap.sh: 15: ./bootstrap.sh: aclocal: not found > > > > 4) Running autoheader... > > > > ./bootstrap.sh: 18: ./bootstrap.sh: autoheader: not found > > > > 3) Running autoconf... > > > > ./bootstrap.sh: 21: ./bootstrap.sh: autoconf: not found > > > > 2) Running automake... > > > > ./bootstrap.sh: 25: ./bootstrap.sh: automake: not found > > > > 1) Generating derived language files..... > > > > Bootstrap complete. > > > > > > After running bootstrap.sh, a configure script file should end up in your > Xastir directory. I can't explain why it's not there. > > If all else fails you could download and run the build script that's shown > on the page with the instructions. It is up to date through version 18.04. > However If the bootstrap script is not resulting in the creation of the > configure script then the build script will bomb at the same place you are > with your manual effort. > > Regards, > Lee K5DAT > > > ------------------------------ > > Subject: Digest Footer > > _______________________________________________ > Xastir mailing list > Xastir@lists.xastir.org > http://xastir.org/mailman/listinfo/xastir > > > ------------------------------ > > End of Xastir Digest, Vol 689, Issue 2 > ************************************** > _______________________________________________ Xastir mailing list Xastir@lists.xastir.org http://xastir.org/mailman/listinfo/xastir