[wsjt-devel] trying to compile wsjtx revision 6713-dirty using 32 bit Fedora Linux 22
Hi ! Please note the following diagnostic messages I have observed: libwsjt_fort.a(jtmsk_decode.f90.o): In function `jtmsk_decode_': jtmsk_decode.f90:(.text+0x52b): undefined reference to `syncmsk144_' collect2: error: ld returned 1 exit status ### jtmsk_decode.f90:114:3: 900 continue 1 Warning: Label 900 at (1) defined but not used ### Best 88 de Claude -- What NetFlow Analyzer can do for you? Monitors network bandwidth and traffic patterns at an interface-level. Reveals which users, apps, and protocols are consuming the most bandwidth. Provides multi-vendor support for NetFlow, J-Flow, sFlow and other flows. Make informed decisions using capacity planning reports. https://ad.doubleclick.net/ddm/clk/305295220;132659582;e ___ wsjt-devel mailing list wsjt-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wsjt-devel
Re: [wsjt-devel] JTSDK-Win32 - Feature Requests ( User Input Requested ).
Hi Victor, Thanks got to Joe, Bill, Steve, Mike etc, they write all the application code. I do not do any of that work. Joe and Bill would mostly add those types of features / requests, and they read the list routinely. Just to be clean on your request, you should send an email to: wsjt-devel@lists.sourceforge.net with an appropriate subject line, and request those features / additions, just to make sure it doesn't get mixed in with other things. 73's Greg, KI7MT On 05/31/2016 08:25 PM, Victor Batchelor wrote: > Hi Greg, > Thank you for taking time to reply. > Sorry I get confused with the different versions. What I was referring to is > WSPR-2 mode in WSJT-X. > The decoder is certainly much improved, and I like many truly appreciate your > changes. > 73 > Victor > > > > Hi Victor, > > I don't think WSPR-X is under active development. Joe and the other > developers are mainly focusing on WSJT-X and the many sub-programs / > modes it provides. > > I would suggest trying WSJT-X >> WSPR Mode as it has a much improved > decoder over that which currently resides in either the original version > of WSPR or WSPR-X. > > 73's > Greg, KI7MT > > > On 05/25/2016 02:47 AM, Victor Batchelor wrote: >> Hi Greg, >> I would like the WSPR-X waterfall to show the real frequency rather than >> 1400 to 1600. >> As an alternative the option to click on the waterfall to show the real >> frequency would be fine but probably much more work. >> Thanks for all your great work >> 73 >> Victor >> >> >> Hello All, >> >> It's about time to start work on another major release of JTSDK Win32 >> (v2.1), primarily to update packages, libraries, consolidate scripts, >> reduce the overall foot print and number of installers. >> >> With that in mind, I'd like to hear from those of you that use JTSDK on >> Windows as what what sort of features you'd like to see added, things >> you like / dislike or would like to see cleaned up / changed. >> >> The following is a short list of things I currently have on the To-Do list: >> >> * Reduce installer packages back down to one Inno-Setup script >> * Consider using only Windows installers for periodic updates >> * Reduce the number of redundant tool sets (JTSDK-DOC / Cyg32 for >> example) Is anyone using this? >> * Update the Asciidoctor tool chain to allow building PDF files in >> addition to HTML documents >> * Move all the tool \ library folders into a central location >> C:\JTSDK\tools to clean up the cluttered root directory. >> * Eliminate Python27. Is there a reason to have both Python2 and Python3? >> * Eliminate AsciiDoc. Is there a need for both AsciiDoc and AsciiDoctor? >> * Minimize the number or redundant mingw32 tools chains (MSYS and Ruby >> DevKit both use the same tool chain, no need for both) >> * RapidEE - Is this being used by anyone? >> * Add more or reduce the number of generic GNU core-util aplications? >> * Investigate the use of SQLite for package and / or upgrade management. >> Are there other uses for SQLite? >> >> That's a good start in reducing redundancy and disk space, but what >> about new features and abilities? As it stands now, I personally do not >> have a great need for much above and beyond what is currently available >> one way or another, but others may have different needs. If you do, feel >> free to pass along the request(s). >> >> >> 73's >> Greg, KI7MT > > > > -- Launchpad: https://launchpad.net/~ki7mt Ubuntu Hams..: https://launchpad.net/~ubuntu-hams-devel Debian Hams..: https://alioth.debian.org/projects/pkg-hamradio/ JTSDK: https://sourceforge.net/projects/jtsdk/ OpenPGP..: C177 6630 7115 78FE 9A2B 9F7F 18C0 F6B7 0DA2 F991 -- What NetFlow Analyzer can do for you? Monitors network bandwidth and traffic patterns at an interface-level. Reveals which users, apps, and protocols are consuming the most bandwidth. Provides multi-vendor support for NetFlow, J-Flow, sFlow and other flows. Make informed decisions using capacity planning reports. https://ad.doubleclick.net/ddm/clk/305295220;132659582;e ___ wsjt-devel mailing list wsjt-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wsjt-devel
Re: [wsjt-devel] JTSDK-Win32 - Feature Requests ( User Input Requested ).
Hi Greg, Thank you for taking time to reply. Sorry I get confused with the different versions. What I was referring to is WSPR-2 mode in WSJT-X. The decoder is certainly much improved, and I like many truly appreciate your changes. 73 Victor Hi Victor, I don't think WSPR-X is under active development. Joe and the other developers are mainly focusing on WSJT-X and the many sub-programs / modes it provides. I would suggest trying WSJT-X >> WSPR Mode as it has a much improved decoder over that which currently resides in either the original version of WSPR or WSPR-X. 73's Greg, KI7MT On 05/25/2016 02:47 AM, Victor Batchelor wrote: > Hi Greg, > I would like the WSPR-X waterfall to show the real frequency rather than 1400 > to 1600. > As an alternative the option to click on the waterfall to show the real > frequency would be fine but probably much more work. > Thanks for all your great work > 73 > Victor > > > Hello All, > > It's about time to start work on another major release of JTSDK Win32 > (v2.1), primarily to update packages, libraries, consolidate scripts, > reduce the overall foot print and number of installers. > > With that in mind, I'd like to hear from those of you that use JTSDK on > Windows as what what sort of features you'd like to see added, things > you like / dislike or would like to see cleaned up / changed. > > The following is a short list of things I currently have on the To-Do list: > > * Reduce installer packages back down to one Inno-Setup script > * Consider using only Windows installers for periodic updates > * Reduce the number of redundant tool sets (JTSDK-DOC / Cyg32 for > example) Is anyone using this? > * Update the Asciidoctor tool chain to allow building PDF files in > addition to HTML documents > * Move all the tool \ library folders into a central location > C:\JTSDK\tools to clean up the cluttered root directory. > * Eliminate Python27. Is there a reason to have both Python2 and Python3? > * Eliminate AsciiDoc. Is there a need for both AsciiDoc and AsciiDoctor? > * Minimize the number or redundant mingw32 tools chains (MSYS and Ruby > DevKit both use the same tool chain, no need for both) > * RapidEE - Is this being used by anyone? > * Add more or reduce the number of generic GNU core-util aplications? > * Investigate the use of SQLite for package and / or upgrade management. > Are there other uses for SQLite? > > That's a good start in reducing redundancy and disk space, but what > about new features and abilities? As it stands now, I personally do not > have a great need for much above and beyond what is currently available > one way or another, but others may have different needs. If you do, feel > free to pass along the request(s). > > > 73's > Greg, KI7MT -- What NetFlow Analyzer can do for you? Monitors network bandwidth and traffic patterns at an interface-level. Reveals which users, apps, and protocols are consuming the most bandwidth. Provides multi-vendor support for NetFlow, J-Flow, sFlow and other flows. Make informed decisions using capacity planning reports. https://ad.doubleclick.net/ddm/clk/305295220;132659582;e___ wsjt-devel mailing list wsjt-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wsjt-devel
Re: [wsjt-devel] JTSDK-Win32 - Feature Requests ( User Input Requested )
Hi Victor, I don't think WSPR-X is under active development. Joe and the other developers are mainly focusing on WSJT-X and the many sub-programs / modes it provides. I would suggest trying WSJT-X >> WSPR Mode as it has a much improved decoder over that which currently resides in either the original version of WSPR or WSPR-X. 73's Greg, KI7MT On 05/25/2016 02:47 AM, Victor Batchelor wrote: > Hi Greg, > I would like the WSPR-X waterfall to show the real frequency rather than 1400 > to 1600. > As an alternative the option to click on the waterfall to show the real > frequency would be fine but probably much more work. > Thanks for all your great work > 73 > Victor > > > Hello All, > > It's about time to start work on another major release of JTSDK Win32 > (v2.1), primarily to update packages, libraries, consolidate scripts, > reduce the overall foot print and number of installers. > > With that in mind, I'd like to hear from those of you that use JTSDK on > Windows as what what sort of features you'd like to see added, things > you like / dislike or would like to see cleaned up / changed. > > The following is a short list of things I currently have on the To-Do list: > > * Reduce installer packages back down to one Inno-Setup script > * Consider using only Windows installers for periodic updates > * Reduce the number of redundant tool sets (JTSDK-DOC / Cyg32 for > example) Is anyone using this? > * Update the Asciidoctor tool chain to allow building PDF files in > addition to HTML documents > * Move all the tool \ library folders into a central location > C:\JTSDK\tools to clean up the cluttered root directory. > * Eliminate Python27. Is there a reason to have both Python2 and Python3? > * Eliminate AsciiDoc. Is there a need for both AsciiDoc and AsciiDoctor? > * Minimize the number or redundant mingw32 tools chains (MSYS and Ruby > DevKit both use the same tool chain, no need for both) > * RapidEE - Is this being used by anyone? > * Add more or reduce the number of generic GNU core-util aplications? > * Investigate the use of SQLite for package and / or upgrade management. > Are there other uses for SQLite? > > That's a good start in reducing redundancy and disk space, but what > about new features and abilities? As it stands now, I personally do not > have a great need for much above and beyond what is currently available > one way or another, but others may have different needs. If you do, feel > free to pass along the request(s). > > > 73's > Greg, KI7MT -- What NetFlow Analyzer can do for you? Monitors network bandwidth and traffic patterns at an interface-level. Reveals which users, apps, and protocols are consuming the most bandwidth. Provides multi-vendor support for NetFlow, J-Flow, sFlow and other flows. Make informed decisions using capacity planning reports. https://ad.doubleclick.net/ddm/clk/305295220;132659582;e ___ wsjt-devel mailing list wsjt-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wsjt-devel
Re: [wsjt-devel] wsjtx-1.6.0.r6263-1.21.x86_64 opensuse RX dies after TX,
Hallo, The same issue comes up on a Fedora 23 installation with KDE. After the first transmission pulseaudio is switching the input to the first audio device instead of the one selected by WSJT-X. This can easily be corrected with pavucontrol and all subsequent transmissions do not change the input anymore until the next stop and startup of WSJT-X. I made this test with the fedora_23 version from my repository http://download.opensuse.org/repositories/home:/dl8fcl:/test/ in a VirtualBox VM. For testing openSUSE_42.1 KDE in a VirtualBox VM you have to disable 3D-acceleration in the VirtualBox Manager. 73, Walter DL8FCL -- What NetFlow Analyzer can do for you? Monitors network bandwidth and traffic patterns at an interface-level. Reveals which users, apps, and protocols are consuming the most bandwidth. Provides multi-vendor support for NetFlow, J-Flow, sFlow and other flows. Make informed decisions using capacity planning reports. https://ad.doubleclick.net/ddm/clk/305295220;132659582;e ___ wsjt-devel mailing list wsjt-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wsjt-devel
Re: [wsjt-devel] WSJT-X r6707 Startup Problems
Hi Bill,
Had a problem with the cmake - one that had not happened when I built the
original executable here on the RPi.Please advise... :-)
[ 75%] Building CXX object CMakeFiles/wsjt_qt.dir/HamlibTransceiver.cpp.o
[ 75%] Building CXX object CMakeFiles/wsjt_qt.dir/HRDTransceiver.cpp.o
/home/pi/wsjtx-1.7.0/src/HamlibTransceiver.cpp: In member function ‘virtual int
HamlibTransceiver::do_start()’:
/home/pi/wsjtx-1.7.0/src/HamlibTransceiver.cpp:541:66: error:
‘RIG_PASSBAND_NOCHANGE’ was not declared in this scope
rig_set_mode (rig_.data (), RIG_VFO_CURR, dummy_mode_,
RIG_PASSBAND_NOCHANGE);
^
/home/pi/wsjtx-1.7.0/src/HamlibTransceiver.cpp: In member function ‘virtual
void HamlibTransceiver::do_frequency(Transceiver::Frequency, Transceiver::MODE,
bool)’:
/home/pi/wsjtx-1.7.0/src/HamlibTransceiver.cpp:653:80: error:
‘RIG_PASSBAND_NOCHANGE’ was not declared in this scope
error_check (rig_set_mode (rig_.data (), RIG_VFO_CURR, new_mode,
RIG_PASSBAND_NOCHANGE), tr ("setting current VFO mode"));
^
/home/pi/wsjtx-1.7.0/src/HamlibTransceiver.cpp: In member function ‘virtual
void HamlibTransceiver::do_tx_frequency(Transceiver::Frequency, bool)’:
/home/pi/wsjtx-1.7.0/src/HamlibTransceiver.cpp:731:88: error:
‘RIG_PASSBAND_NOCHANGE’ was not declared in this scope
error_check (rig_set_mode (rig_.data (), RIG_VFO_CURR,
new_mode, RIG_PASSBAND_NOCHANGE), tr ("setting current VFO mode"));
^
/home/pi/wsjtx-1.7.0/src/HamlibTransceiver.cpp:744:99: error:
‘RIG_PASSBAND_NOCHANGE’ was not declared in this scope
error_check (rig_set_split_freq_mode (rig_.data (),
RIG_VFO_CURR, tx, new_mode, RIG_PASSBAND_NOCHANGE), tr ("setting split TX
frequency and mode"));
^
/home/pi/wsjtx-1.7.0/src/HamlibTransceiver.cpp: In member function ‘virtual
void HamlibTransceiver::do_mode(Transceiver::MODE)’:
/home/pi/wsjtx-1.7.0/src/HamlibTransceiver.cpp:803:76: error:
‘RIG_PASSBAND_NOCHANGE’ was not declared in this scope
error_check (rig_set_mode (rig_.data (), RIG_VFO_CURR, new_mode,
RIG_PASSBAND_NOCHANGE), tr ("setting current VFO mode"));
^
/home/pi/wsjtx-1.7.0/src/HamlibTransceiver.cpp:816:76: error:
‘RIG_PASSBAND_NOCHANGE’ was not declared in this scope
error_check (rig_set_mode (rig_.data (), RIG_VFO_CURR, new_mode,
RIG_PASSBAND_NOCHANGE), tr ("setting current VFO mode"));
^
/home/pi/wsjtx-1.7.0/src/HamlibTransceiver.cpp:828:82: error:
‘RIG_PASSBAND_NOCHANGE’ was not declared in this scope
error_check (rig_set_split_mode (rig_.data (), RIG_VFO_CURR,
new_mode, RIG_PASSBAND_NOCHANGE), tr ("setting split TX VFO mode"));
^
CMakeFiles/wsjt_qt.dir/build.make:612: recipe for target
'CMakeFiles/wsjt_qt.dir/HamlibTransceiver.cpp.o' failed
make[2]: *** [CMakeFiles/wsjt_qt.dir/HamlibTransceiver.cpp.o] Error 1
make[2]: *** Waiting for unfinished jobs
Scanning dependencies of target wsjtx_udp-static
[ 75%] Building CXX object CMakeFiles/wsjtx_udp-static.dir/Radio.cpp.o
[ 75%] Building CXX object CMakeFiles/wsjtx_udp-static.dir/RadioMetaType.cpp.o
CMakeFiles/Makefile2:1209: recipe for target 'CMakeFiles/wsjt_qt.dir/all' failed
make[1]: *** [CMakeFiles/wsjt_qt.dir/all] Error 2
make[1]: *** Waiting for unfinished jobs
[ 75%] Building CXX object CMakeFiles/wsjtx_udp-static.dir/NetworkMessage.cpp.o
[ 75%] Building CXX object CMakeFiles/wsjtx_udp-static.dir/MessageServer.cpp.o
[ 76%] Building CXX object
CMakeFiles/wsjtx_udp-static.dir/wsjtx_udp-static_automoc.cpp.o
Linking CXX static library libwsjtx_udp.a
[ 76%] Built target wsjtx_udp-static
Makefile:137: recipe for target 'all' failed
make: *** [all] Error 2
pi@raspberrypi:~/wsjtx-1.7.0/build/debug $
On Monday, May 30, 2016 4:02 PM, Bill Somerville
wrote:
On 30/05/2016 19:03, Jim Bennett wrote:
> I probably mis-interpreted the output of the traceback; saw the memory
> access error and ässumed" it was what caused the program to not
> complete initialization. So, next steps?
Hi Jim,
let's try a debug build. To do that you are probably best to create a
second build tree and keep the release configuration tree for release
builds. So create a new build directory, something like:
mkdir ~/wsjtx-prefix/build/debug
then change working directory to it and configure the build. The
difference in the configure is that you must set CMAKE_BUILD_TYPE=Debug
and set a different
[wsjt-devel] PowerPC G5 iMac Update.
Afternoon, During the holiday weekend here in the UK I thought I would take the opportunity to download Lubuntu 16.04 and do a complete clean install of linux on my G5 iMac PowerPC. After that downloading JTSDK from Greg’s (KI7MT) PPA and all went well. Please to report that I’m successfully running WSJTX, v1.7.0 r6711 without any problems. Once again well done to all concerned and thank you for all of the hard work. Kind regards, Sean (G0OAN) -- What NetFlow Analyzer can do for you? Monitors network bandwidth and traffic patterns at an interface-level. Reveals which users, apps, and protocols are consuming the most bandwidth. Provides multi-vendor support for NetFlow, J-Flow, sFlow and other flows. Make informed decisions using capacity planning reports. https://ad.doubleclick.net/ddm/clk/305295220;132659582;e ___ wsjt-devel mailing list wsjt-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wsjt-devel
