Re: [wsjt-devel] WSJT-X 2.6.0 Error in Network Address

[Paul Bramscher via wsjt-devel]

I found this same pop-up message on 2.6.1 as well as 2.6.0 -- but never 
on previous versions.


However, I found the issue.  Namely, under Reporting -> UDP Server mine 
read "localhost" instead of an actual/numeric IP (like 127.0.0.1).


This warning pop-up appears whether or not you actually activate the UDP 
server.  So I set it to 127.0.0.1, even though I keep it toggled off, 
and the pop-up indicating an error in network address goes away.


73, KD0KZE / Paul

On 1/10/23 20:33, Paul Bramscher via wsjt-devel wrote:
A couple days ago I compiled WSJT-X 2.6.0 on Debian Linux 11 without 
issue, as per Bill's suggestions from a few years ago.  I've made 
several FT8 QSO's, no issues noted.


But I just stumbled on a weird bug:

When I click File:Settings and then cancel without making any changes 
there's a pop-up window.  It's entitled simply "WSJT-X" and contains the 
following text:



Error in Network Address
Error before first number


In case it matters:
* I've not previously run any of the RC versions on that PC.
* I've not made any config changes with 2.6.0 and clicked "save" yet.

So my config is a carry-over from 2.5.4.  Possibly an uninitialized 
variable?


73, KD0KZE / Paul


___
wsjt-devel mailing list
wsjt-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wsjt-devel



___
wsjt-devel mailing list
wsjt-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wsjt-devel

[wsjt-devel] WSJT-X 2.6.0 Error in Network Address

[Paul Bramscher via wsjt-devel]

A couple days ago I compiled WSJT-X 2.6.0 on Debian Linux 11 without 
issue, as per Bill's suggestions from a few years ago.  I've made 
several FT8 QSO's, no issues noted.


But I just stumbled on a weird bug:

When I click File:Settings and then cancel without making any changes 
there's a pop-up window.  It's entitled simply "WSJT-X" and contains the 
following text:



Error in Network Address
Error before first number


In case it matters:
* I've not previously run any of the RC versions on that PC.
* I've not made any config changes with 2.6.0 and clicked "save" yet.

So my config is a carry-over from 2.5.4.  Possibly an uninitialized 
variable?


73, KD0KZE / Paul


___
wsjt-devel mailing list
wsjt-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wsjt-devel

Re: [wsjt-devel] Are you building WSJT-X ?

[Paul Bramscher via wsjt-devel]

Hi Joe & group--

First of all, many thanks for this amazing software.  We are doing 
things that would have been considered science fiction at one time.


Using Bill's instructions with some minor tweaks and additions, I've 
been compiling on Debian Linux for several years.


I have a B.S. CSci, and have worked in IT for over 25 years.  Mainly 
programming web and database technologies (LAMP stack), and more 
recently Python, admin and security.


I make no changes to the source, mainly I just want the most current 
version on Debian, and the ability to test multiple versions.  I wish I 
had time to study the source more, since I did coursework in c/c++ (and 
even Fortran back in the day).


73, KD0KZE / Paul

On 4/25/22 10:29, Joe Taylor via wsjt-devel wrote:
When I started work on WSJT some 21 years ago, my principal goal was to 
help bring amateur weak-signal communication techniques into the 
twenty-first century -- and in doing so, to help spread knowledge of 
modern communication theory into the amateur radio community.


By 2005 WSJT was well established but mostly used for special purposes 
like meteor scatter and EME ("moonbounce").  A stable development path 
had been established: the program was fully Open Source, licensed under 
the GNU General Public License, and it could be built by anyone from 
source code using freely available compilers and development tools.  At 
this time WSJT was coded in a combination of Python, Fortran, and C.  A 
re-write in 2012 created the present program, WSJT-X, using the Qt 
platform and C++ language in addition to Fortran and C.


To help gauge the extent to which my original educational goals are 
being met, we in the core development team are interested to know how 
many WSJT-X users are currently building the program for themselves, 
from source code.  If you are doing so, we would appreciate an email 
response -- either publicly, to this list, or in a private email to me. 
All responses will be appreciated, but particular things you might want 
to mention in your message include these:


  - Building on what platform?  Windows, Linux, macOS, or other?

  - What are your particular programming skills and interests?

  - Are you making changes to the code?  If so, toward what end?

  - What portions of the code have you studied well enough to understand?

Many thanks -- I look forward to hearing from you!

 -- 73, Joe, K1JT


___
wsjt-devel mailing list
wsjt-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wsjt-devel



___
wsjt-devel mailing list
wsjt-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wsjt-devel

Re: [wsjt-devel] WSJT-X 2.5.4 GA Release

[Paul Bramscher via wsjt-devel]

Thanks Joe -- we appreciate the update.  Downloaded the source tarball 
from your Princeton site, compiled without issue on Debian 11.


Previously I was running 2.5.3 with a Kenwood TS-590S and it did crash a 
few times.  No such problems seen yet with 2.5.4.


73, KD0KZE / Paul

On 1/3/22 10:54, Joe Taylor via wsjt-devel wrote:
Please welcome two new members of the core WSJT Development group: Chet 
Fennell, KG4IYS, and Uwe Risse, DG2YCB.  Each brings important skills 
and experience to the project, after the loss of Bill Somerville, G4WJS.


The newly constituted group has been working to redefine standard 
operating procedures for new releases.  WSJT-X 2.5.4, a bug-fix release 
correcting these two flaws in release 2.5.3, is now available as a 
General Availability (GA) release.


Changes from v2.5.3 are:

WSJT-X: Repair a defect that caused occasional crashes when in QSO with
stations using nonstandard callsigns.

MAP65: Correct a bug that prevented "Best-fit Delta phi" solutions from 
  being displayed to the user.


Links to WSJT-X 2.5.4 installation packages for Windows and Linux are 
available here:

http://physics.princeton.edu/pulsar/k1jt/wsjtx.html

Thanks to John Nelson, G4KLA, the installation package for macOS will be 
added soon.


You can also download the packages from our SourceForge site:
https://sourceforge.net/projects/wsjt/files/
It may take a short time for the SourceForge site to be updated.

WSJT-X is licensed under the terms of Version 3 of the GNU General 
Public License (GPL).  Development of this software is a cooperative 
project to which many amateur radio operators have contributed.  If you 
use our code, please have the courtesy to let us know about it.  If you 
find bugs or make improvements to the code, please report them to us in 
a timely fashion.


The authors and Copyright holders of WSJT-X request that derivative 
works should not publish programs based on features in WSJT-X before 
those features are made available in a General Availability (GA) release 
of WSJT-X.  We will cease making public Release Candidate (RC) 
pre-releases for testing and user early access purposes if this request 
is ignored.


Bugs should be reported by following instructions found here in the User 
Guide:


https://www.physics.princeton.edu//pulsar/K1JT/wsjtx-doc/wsjtx-main-2.5.4.html#_bug_reports 



We hope you will enjoy using WSJT-X 2.5.4.

    -- 73 from Joe, K1JT; Steve, K9AN; Nico, IV3NWV; Chet, KG4IYS; and
    Uwe, DG3YCB.


___
wsjt-devel mailing list
wsjt-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wsjt-devel



___
wsjt-devel mailing list
wsjt-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wsjt-devel

Re: [wsjt-devel] WSJT-X 2.5.3 GA Release (Win64 only)

[Paul Bramscher via wsjt-devel]

I am very sorry to hear of Bill becoming SK.  He has helped me several 
times over the years compile WSJT-X from source on Linux, on this list 
and in e-mail.


Please don't hesitate to release the source, since Bill's instructions 
with a couple additional dependencies still work for me on the current 
Debian.  I can help out folks interested in Debian.


73, KD0KZE / Paul

On 12/8/21 12:25 PM, Joe Taylor via wsjt-devel wrote:

Dear WSJT-X Users:

As most of you know, we are mourning the recent death of our friend and 
colleague Bill Somerville, G4WJS, who since 2013 has contributed so much 
to the WSJT project.


One of Bill's many WSJT-related tasks was creating installation packages 
for Win32, Win64, Linux (Debian, Fedora, Raspberry Pi, ...), and macOS 
for each new program release.  At present we have a straightforward 
system for building the Win64 package -- the best choice for the 
majority of WSJT-X users -- but no systems in place for building Win32, 
Linux, and macOS packages.


WSJT-X 2.5.3 includes a feature of special interest to users who will 
enter the ARRL January VHF Contest (January 15-17, 2022).  For benefit 
of those users, we have decided to release WSJT-X version 2.5.3 for 
Win64 even though we have not yet made prebuilt packages for the other 
operating systems.


Differences between WSJT-X 2.5.2 and 2.5.3 are minimal and described in 
the Release Notes:

https://physics.princeton.edu//pulsar/k1jt/Release_Notes.txt

The new feature for the ARRL VHF contests is an enhanced macro facility 
for Tx messages, aimed at making it easier to ask another station to QSY 
to a new band.  The feature is described briefly here in the User Guide:
https://www.physics.princeton.edu/pulsar/K1JT/wsjtx-doc/wsjtx-main-2.5.3.html#TXMACROS 


Additional information will likely appear on VHF-contest-related forums.

A link for the Win64 installation package for WSJT-X 2.5.3 is now 
available on the WSJT-X web page:

https://physics.princeton.edu//pulsar/k1jt/wsjtx.html

Pre-built packages for Win32, Linux, and macOS will be added when we 
have created new means for creating them.


  -- 73 from Joe, K1JT; Steve, K9AN; and Nico, IV3NWV


___
wsjt-devel mailing list
wsjt-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wsjt-devel



___
wsjt-devel mailing list
wsjt-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wsjt-devel

Re: [wsjt-devel] WSJT-X 2.5.2 GA Release

[Paul Bramscher via wsjt-devel]

Compiled and working fine here on Debian 11 the past day or so.

73, KD0KZE / Paul

On 11/4/21 1:03 PM, Joe Taylor via wsjt-devel wrote:
We are pleased to announce the General Availability (GA) release of 
WSJT-X version 2.5.2.  This is mostly a bug-fix release.  A full list of 
changes can be found in the Release Notes:

https://physics.princeton.edu//pulsar/k1jt/Release_Notes.txt

IMPORTANT: If you expect to use the JT65 or Q65 modes to make 
weak-signal QSOs that involve a nonstandard callsign, be sure to upgrade 
to WSJT-X 2.5.2!


Links to WSJT-X 2.5.2 installation packages for Windows, Linux, and 
Macintosh are available here:

http://physics.princeton.edu/pulsar/k1jt/wsjtx.html

You can also download the packages from our SourceForge site:
https://sourceforge.net/projects/wsjt/files/
It may take a short time for the SourceForge site to be updated.

WSJT-X is licensed under the terms of Version 3 of the GNU General 
Public License (GPL).  Development of this software is a cooperative 
project to which many amateur radio operators have contributed.  If you 
use our code, please have the courtesy to let us know about it.  If you 
find bugs or make improvements to the code, please report them to us in 
a timely fashion.


The authors and Copyright holders of WSJT-X request that derivative 
works should not publish programs based on features in WSJT-X before 
those features are made available in a General Availability (GA) release 
of WSJT-X.  We will cease making public Release Candidate (RC) 
pre-releases for testing and user early access purposes if this request 
is ignored.


Bugs should be reported by following instructions found here in the User 
Guide:


https://www.physics.princeton.edu//pulsar/K1JT/wsjtx-doc/wsjtx-main-2.5.2.html#_bug_reports 



We hope you will enjoy using WSJT-X 2.5.2.

  -- 73 from Joe, K1JT; Bill, G4WJS; Steve, K9AN; and Nico, IV3NWV


___
wsjt-devel mailing list
wsjt-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wsjt-devel



___
wsjt-devel mailing list
wsjt-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wsjt-devel

Re: [wsjt-devel] WSJT-X 2.5.0 GA Release

[Paul Bramscher via wsjt-devel]

Thanks for the great work.  Compiled fine from source on Debian 11 
Linux, using my usual methodology.


I noted that the workable frequencies table got larger, but deleted the 
ones my rig is incapable of handling to avoid accidentally switching to 
one.  Good to see there's a simple way to restore to defaults (if I get 
another rig).


I didn't do any of the RC testing this go around, too busy with other 
things in life.  But will be using 2.5.0 now, looks great!


73, KD0KZE / Paul

On 9/27/2021 11:14 AM, Joe Taylor via wsjt-devel wrote:
We are pleased to announce the General Availability (GA) release of 
WSJT-X version 2.5.0.  New features are described in the WSJT-X User 
Guide here:


https://physics.princeton.edu//pulsar/k1jt/wsjtx-doc/wsjtx-main-2.5.0.html#NEW_FEATURES 



and also Release Notes:

https://physics.princeton.edu//pulsar/k1jt/Release_Notes.txt

On Windows platforms, WSJT-X 2.5 includes MAP65 3.0.0, a wideband 
polarization-matching tool intended for EME.


Links to WSJT-X 2.5.0 installation packages for Windows, Linux, and 
Macintosh are available here:

http://physics.princeton.edu/pulsar/k1jt/wsjtx.html

You can also download the packages from our SourceForge site:
https://sourceforge.net/projects/wsjt/files/
It may take a short time for the SourceForge site to be updated.

WSJT-X for Windows now ships with Hamlib built as a dynamic link library 
(DLL).  This change will allow Hamlib bug fixes to be resolved by 
replacing the DLL with an updated version.


WSJT-X is licensed under the terms of Version 3 of the GNU General 
Public License (GPL).  Development of this software is a cooperative 
project to which many amateur radio operators have contributed.  If you 
use our code, please have the courtesy to let us know about it.  If you 
find bugs or make improvements to the code, please report them to us in 
a timely fashion.


The authors and Copyright holders of WSJT-X request that derivative 
works should not publish programs based on features in WSJT-X before 
those features are made available in a General Availability (GA) release 
of WSJT-X.  We will cease making public Release Candidate (RC) 
pre-releases for testing and user early access purposes if this request 
is ignored.


Bugs should be reported by following instructions found here in the User 
Guide:


https://www.physics.princeton.edu//pulsar/K1JT/wsjtx-doc/wsjtx-main-2.5.0.html#_bug_reports 



We hope you will enjoy using WSJT-X 2.5.0.

  -- 73 from Joe, K1JT; Bill, G4WJS; Steve, K9AN; and Nico, IV3NWV


___
wsjt-devel mailing list
wsjt-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wsjt-devel




___
wsjt-devel mailing list
wsjt-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wsjt-devel

Re: [wsjt-devel] My problems while compiling from the source

[Paul Bramscher via wsjt-devel]

I have been compiling WSJT-X for a number of years now on Debian
(including Buster 10 now), occasionally with help from G4WJS, and have
had no troubles in a long while.

I don't download from the git repo, though, and instead just get the
current source .tgz from SourceForge.  Have you had success with that
method?

73, KD0KZE / Paul

On 7/16/2021 11:08 AM, Claude Frantz via wsjt-devel wrote:
> Hi Bill and all,
> 
> I'm trying to compile from the source from the git repo:
> 
> I'm here:
> 
> commit 7eac85560823e9c53ae5ed876861f73a1258c717 (HEAD -> master, tag:
> wsjtx-2.5.0-rc3, origin/master, origin/HEAD)
> Merge: df3da69d2 522f698c6
> Author: Bill Somerville 
> Date:   Mon Jul 5 20:58:15 2021 +0100
> 
>     Merge branch 'release-2.5.0'
> 
> commit 522f698c6300613532dd470f6de5f9c9ca986fbf
> Author: Bill Somerville 
> Date:   Mon Jul 5 20:48:05 2021 +0100
> 
>     Release note updates
> 
> commit f067d9472397539e9e1b9247a1d8155e7c768201
> Merge: a141b5af3 bada2dd82
> Author: Bill Somerville 
> Date:   Mon Jul 5 20:43:42 2021 +0100
> 
>     Merge branch 'release-2.5.0' of bitbucket.org:k1jt/wsjtx into
> release-2.5.0
> 
> ###
> 
> The compilation ended here:
> 
> Scanning dependencies of target message_aggregator
> [ 11%] Building CXX object
> CMakeFiles/message_aggregator.dir/UDPExamples/MessageAggregator.cpp.o
> [ 11%] Building CXX object
> CMakeFiles/message_aggregator.dir/UDPExamples/MessageAggregatorMainWindow.cpp.o
> 
> [ 11%] Building CXX object
> CMakeFiles/message_aggregator.dir/UDPExamples/DecodesModel.cpp.o
> [ 11%] Building CXX object
> CMakeFiles/message_aggregator.dir/UDPExamples/BeaconsModel.cpp.o
> [ 11%] Building CXX object
> CMakeFiles/message_aggregator.dir/UDPExamples/ClientWidget.cpp.o
> [ 11%] Building CXX object
> CMakeFiles/message_aggregator.dir/validators/MaidenheadLocatorValidator.cpp.o
> 
> [ 12%] Building CXX object
> CMakeFiles/message_aggregator.dir/qrc_message_aggregator.cpp.o
> [ 12%] Building CXX object
> CMakeFiles/message_aggregator.dir/qrc_style.cpp.o
> [ 12%] Building CXX object
> CMakeFiles/message_aggregator.dir/message_aggregator_autogen/mocs_compilation.cpp.o
> 
> [ 12%] Linking CXX executable message_aggregator
> /usr/bin/ld: /usr/lib/x86_64-linux-gnu/libthread_db.so: undefined
> reference to `ps_lsetregs'
> /usr/bin/ld: /usr/lib/x86_64-linux-gnu/libthread_db.so: undefined
> reference to `ps_pdread'
> /usr/bin/ld: /usr/lib/x86_64-linux-gnu/libthread_db.so: undefined
> reference to `ps_lsetfpregs'
> /usr/bin/ld: /usr/lib/x86_64-linux-gnu/libthread_db.so: undefined
> reference to `ps_getpid'
> /usr/bin/ld: /usr/lib/x86_64-linux-gnu/libthread_db.so: undefined
> reference to `ps_pdwrite'
> /usr/bin/ld: /usr/lib/x86_64-linux-gnu/libthread_db.so: undefined
> reference to `ps_lgetregs'
> /usr/bin/ld: /usr/lib/x86_64-linux-gnu/libthread_db.so: undefined
> reference to `ps_lgetfpregs'
> /usr/bin/ld: /usr/lib/x86_64-linux-gnu/libthread_db.so: undefined
> reference to `ps_pglobal_lookup'
> collect2: error: ld returned 1 exit status
> make[2]: *** [CMakeFiles/message_aggregator.dir/build.make:273:
> message_aggregator] Error 1
> make[1]: *** [CMakeFiles/Makefile2:140:
> CMakeFiles/message_aggregator.dir/all] Error 2
> make: *** [Makefile:152: all] Error 2
> 
> ###
> 
> What is missing or wrong ?
> 
> The system:
> Linux defi 4.19.0-17-amd64 #1 SMP Debian 4.19.194-2 (2021-06-21) x86_64
> GNU/Linux
> 
> Best wishes,
> Claude (DJ0OT)
> 
> 
> ___
> wsjt-devel mailing list
> wsjt-devel@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/wsjt-devel



___
wsjt-devel mailing list
wsjt-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wsjt-devel

[wsjt-devel] Possible feature request, time skew notification?

[Paul Bramscher via wsjt-devel]

I was at a monthly outdoor ham event in the greater St. Paul/Minneapolis
area that's drawn loyal attendance the past few years.  An operator
setup FT8 outdoors, but had some issues getting it to decode.  We could
tell it was getting sound from his port, but there was no decoding.

He was using Windows, whereas I'm Linux only so wasn't much help.
Another ham suggested he compare his system clock with his cellphone,
and that fixed it.  I believe he said he was off by 5+ seconds.

I'm wondering whether it might be possible, algorithmically to somehow
detect that a person's clock may be out of sync and present a
notification message.  Of course there's the DT/Time Delta column when
you are able to decode.  But, presumably, he had reached the point of no
return.

I don't know how this might be possible without an accurate reference
clock -- but possibly based on the average timing of heard signals, or
some sort of signature within them, to cause a message to the user that
s/he may want to check their clock's accuracy?

Just wondering what might be possible in this regard, and I suspect it
would help portable users, especially those who've been offline for a
number of days/etc. and their system clocks had degraded.

73, KD0KZE / Paul


___
wsjt-devel mailing list
wsjt-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wsjt-devel

Re: [wsjt-devel] WSJT-X 2.3.0-rc4

[Paul Bramscher]

I downloaded it quite shortly after it was posted on SourceForge.
Compiled fine on Debian 10 amd64, fully patched, no issues noted so far.

Keep up the great work.

73, KD0KZE / Paul

On 1/25/2021 8:45 AM, Joe Taylor wrote:
> The fourth public candidate release of WSJT-X 2.3.0 is now available for
> download and use by beta testers.  Changes from the third release
> candidate are minimal; they are described in the Release Notes here:
> 
> https://physics.princeton.edu//pulsar/k1jt/Release_Notes.txt
> 
> Links to installation packages for Windows, Linux, and Macintosh are
> available here:
> https://physics.princeton.edu/pulsar/k1jt/wsjtx.html
> 
> Scroll down to find "Candidate release:  WSJT-X 2.3.0-rc4".
> 
> You can also download the packages from our SourceForge site:
> https://sourceforge.net/projects/wsjt/files/
> It may take a short time for the SourceForge site to be updated.
> 
> We expect to make a General Availability (GA) release of WSJT-X 2.3.0
> very soon.
> 
> WSJT-X is licensed under the terms of Version 3 of the GNU General
> Public License (GPL).  Development of this software is a cooperative
> project to which many amateur radio operators have contributed.  If you
> use our code, please have the courtesy to let us know about it.  If you
> find bugs or make improvements to the code, please report them to us in
> a timely fashion.
> 
> We hope you will enjoy using this beta release of WSJT-X 2.3.0.  Please
> report bugs by following instructions found here in the User Guide:
> https://www.physics.princeton.edu/pulsar/K1JT/wsjtx-doc/wsjtx-main-2.3.0-rc4.html#_bug_reports
> 
> 
>  -- 73 from Joe, K1JT; Bill, G4WJS; Steve, K9AN; and Nico, IV3NWV
> 
> 
> ___
> wsjt-devel mailing list
> wsjt-devel@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/wsjt-devel



___
wsjt-devel mailing list
wsjt-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wsjt-devel

[wsjt-devel] WSJT-X 2.3.0-rc2 auto-stop TX not working?

[Paul Bramscher]

Greetings--  I may be imagining this (apologies if so), but there may be
a change of behavior between RC1 and RC2 or thereabouts with regard to
transmitting.  I'm running RC2 compiled on Debian Linux, Kenwood TS-590.

I seem to recall in the past that if:
Some station is calling CQ
You attempt to answer
They begin a QSO with some other station

Then WSJT-X's TX automatically disables, as a courtesy to the two
other stations beginning a QSO.

Seems it remains engaged now, and you need to manually turn off TX to
that station lest you step on their QSO.

Has this behavior changed, or am I imagining things?  I run only split
mode these days, if that has anything to do with it.

73, KD0KZE / Paul


___
wsjt-devel mailing list
wsjt-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wsjt-devel

Re: [wsjt-devel] WSJT-X 2.3.0-rc2 compile error w/Debian 10 Linux

[Paul Bramscher]

Hi Bill,

Thanks, this solved it.  I saw a thread on boost+MacOS but didn't connect the 
dots to Linux.  libboost-all-dev added about 554 MB to the dependency size, and 
it seemed the compile took longer than usual.  But it could be that there was 
some residual disk activity from bringing down these new dependencies and the 
next compile may go more swiftly.

At any rate, I'll test out rc2 now.

73, KD0KZE / Paul

> On 11/16/2020 8:42 AM Bill Somerville  wrote:
> 
> 
> On 16/11/2020 14:27, Paul Bramscher wrote:
> 
> > > I'm getting a compile error with Debian 10 Linux (amd64), 
> fully patched.  No trouble compiling 2.3.0-rc1.  But here is what fails on 
> rc2:
> > 
> > My cmake/compile commands:
> > cmake -DCMAKE_INSTALL_PREFIX=../../install/ -DWSJT_SKIP_MANPAGES=ON 
> > -DWSJT_GENERATE_DOCS=OFF ../wsjtx-2.3.0-rc2
> > cmake --build ~/wsjtx/wsjtx-2.3.0-rc2/build/wsjtx-2.3.0-rc2 
> > --target install -- -j
> > 
> > Failure points:
> > -- Performing Test COMPILER_HAS_HIDDEN_VISIBILITY
> > -- Performing Test COMPILER_HAS_HIDDEN_VISIBILITY - Success
> > -- Performing Test COMPILER_HAS_HIDDEN_INLINE_VISIBILITY
> > -- Performing Test COMPILER_HAS_HIDDEN_INLINE_VISIBILITY - Success
> > -- Performing Test COMPILER_HAS_DEPRECATED_ATTR
> > -- Performing Test COMPILER_HAS_DEPRECATED_ATTR - Failed
> > -- Performing Test COMPILER_HAS_DEPRECATED
> > -- Performing Test COMPILER_HAS_DEPRECATED - Failed
> > -- Configuring incomplete, errors occurred!
> > See also 
> > "/home/myuser/wsjtx/wsjtx-2.3.0-rc2/build/wsjtx-2.3.0-rc2/wsjtx-prefix/src/wsjtx-build/CMakeFiles/CMakeOutput.log".
> > See also 
> > "/home/myuser/wsjtx/wsjtx-2.3.0-rc2/build/wsjtx-2.3.0-rc2/wsjtx-prefix/src/wsjtx-build/CMakeFiles/CMakeError.log".
> > make[3]: *** [CMakeFiles/wsjtx-install.dir/build.make:73: 
> > wsjtx-prefix/src/wsjtx-stamp/wsjtx-configure] Error 1
> > make[2]: *** [CMakeFiles/Makefile2:361: 
> > CMakeFiles/wsjtx-install.dir/all] Error 2
> > make[1]: *** [CMakeFiles/Makefile2:432: 
> > CMakeFiles/install.dir/rule] Error 2
> > make: *** [Makefile:261: install] Error 2
> > 
> > 
> > > 
> Hi Paul,
> 
> there is a new dependency for WSJT-X v2.3.0 RC2.
> 
> sudo apt-get install libboost-all-dev
> 
> 73
> Bill
> G4WJS.
> 
> ___
> wsjt-devel mailing list
> wsjt-devel@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/wsjt-devel
> 
___
wsjt-devel mailing list
wsjt-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wsjt-devel

[wsjt-devel] WSJT-X 2.3.0-rc2 compile error w/Debian 10 Linux

[Paul Bramscher]

I'm getting a compile error with Debian 10 Linux (amd64), fully patched.  No 
trouble compiling 2.3.0-rc1.  But here is what fails on rc2:

My cmake/compile commands:
cmake -DCMAKE_INSTALL_PREFIX=../../install/ -DWSJT_SKIP_MANPAGES=ON 
-DWSJT_GENERATE_DOCS=OFF ../wsjtx-2.3.0-rc2
cmake --build ~/wsjtx/wsjtx-2.3.0-rc2/build/wsjtx-2.3.0-rc2 --target install -- 
-j

Failure points:
-- Performing Test COMPILER_HAS_HIDDEN_VISIBILITY
-- Performing Test COMPILER_HAS_HIDDEN_VISIBILITY - Success
-- Performing Test COMPILER_HAS_HIDDEN_INLINE_VISIBILITY
-- Performing Test COMPILER_HAS_HIDDEN_INLINE_VISIBILITY - Success
-- Performing Test COMPILER_HAS_DEPRECATED_ATTR
-- Performing Test COMPILER_HAS_DEPRECATED_ATTR - Failed
-- Performing Test COMPILER_HAS_DEPRECATED
-- Performing Test COMPILER_HAS_DEPRECATED - Failed
-- Configuring incomplete, errors occurred!
See also 
"/home/myuser/wsjtx/wsjtx-2.3.0-rc2/build/wsjtx-2.3.0-rc2/wsjtx-prefix/src/wsjtx-build/CMakeFiles/CMakeOutput.log".
See also 
"/home/myuser/wsjtx/wsjtx-2.3.0-rc2/build/wsjtx-2.3.0-rc2/wsjtx-prefix/src/wsjtx-build/CMakeFiles/CMakeError.log".
make[3]: *** [CMakeFiles/wsjtx-install.dir/build.make:73: 
wsjtx-prefix/src/wsjtx-stamp/wsjtx-configure] Error 1
make[2]: *** [CMakeFiles/Makefile2:361: CMakeFiles/wsjtx-install.dir/all] Error 
2
make[1]: *** [CMakeFiles/Makefile2:432: CMakeFiles/install.dir/rule] Error 2
make: *** [Makefile:261: install] Error 2


Snippets from CMakeError.log:

Performing C SOURCE FILE Test HAVE_MATH failed with the following output:
Change Dir: 
/home/myuser/wsjtx/wsjtx-2.3.0-rc2/build/wsjtx-2.3.0-rc2/wsjtx-prefix/src/wsjtx-build/CMakeFiles/CMakeTmp
Run Build Command:"/usr/bin/make" "cmTC_3bcda/fast"
make[4]: Entering directory 
'/home/myuser/wsjtx/wsjtx-2.3.0-rc2/build/wsjtx-2.3.0-rc2/wsjtx-prefix/src/wsjtx-build/CMakeFiles/CMakeTmp'
/usr/bin/make -f CMakeFiles/cmTC_3bcda.dir/build.make 
CMakeFiles/cmTC_3bcda.dir/build
make[5]: Entering directory 
'/home/myuser/wsjtx/wsjtx-2.3.0-rc2/build/wsjtx-2.3.0-rc2/wsjtx-prefix/src/wsjtx-build/CMakeFiles/CMakeTmp'
Building C object CMakeFiles/cmTC_3bcda.dir/src.c.o
/usr/bin/cc -DHAVE_MATH -o CMakeFiles/cmTC_3bcda.dir/src.c.o -c 
/home/myuser/wsjtx/wsjtx-2.3.0-rc2/build/wsjtx-2.3.0-rc2/wsjtx-prefix/src/wsjtx-build/CMakeFiles/CMakeTmp/src.c
Linking C executable cmTC_3bcda
/usr/bin/cmake -E cmake_link_script CMakeFiles/cmTC_3bcda.dir/link.txt 
--verbose=1
/usr/bin/cc -DHAVE_MATH CMakeFiles/cmTC_3bcda.dir/src.c.o -o cmTC_3bcda
/usr/bin/ld: CMakeFiles/cmTC_3bcda.dir/src.c.o: in function `main':
src.c:(.text+0x11): undefined reference to `sqrt'
collect2: error: ld returned 1 exit status
make[5]: *** [CMakeFiles/cmTC_3bcda.dir/build.make:87: cmTC_3bcda] Error 1
make[5]: Leaving directory 
'/home/myuser/wsjtx/wsjtx-2.3.0-rc2/build/wsjtx-2.3.0-rc2/wsjtx-prefix/src/wsjtx-build/CMakeFiles/CMakeTmp'
make[4]: *** [Makefile:121: cmTC_3bcda/fast] Error 2
make[4]: Leaving directory 
'/home/myuser/wsjtx/wsjtx-2.3.0-rc2/build/wsjtx-2.3.0-rc2/wsjtx-prefix/src/wsjtx-build/CMakeFiles/CMakeTmp'

Also:

Run Build Command:"/usr/bin/make" "cmTC_32eb3/fast"
make[4]: Entering directory 
'/home/myuser/wsjtx/wsjtx-2.3.0-rc2/build/wsjtx-2.3.0-rc2/wsjtx-prefix/src/wsjtx-build/CMakeFiles/CMakeTmp'
/usr/bin/make -f CMakeFiles/cmTC_32eb3.dir/build.make 
CMakeFiles/cmTC_32eb3.dir/build
make[5]: Entering directory 
'/home/myuser/wsjtx/wsjtx-2.3.0-rc2/build/wsjtx-2.3.0-rc2/wsjtx-prefix/src/wsjtx-build/CMakeFiles/CMakeTmp'
Building C object CMakeFiles/cmTC_32eb3.dir/HAMLIB_OLD_CACHING.c.o
/usr/bin/cc 
-I/home/myuser/wsjtx/wsjtx-2.3.0-rc2/build/wsjtx-2.3.0-rc2/hamlib-prefix/include
 -I/usr/include/libusb-1.0 -o CMakeFiles/cmTC_32eb3.dir/HAMLIB_OLD_CACHING.c.o 
-c /home/myuser/wsjt$
/home/myuser/wsjtx/wsjtx-2.3.0-rc2/build/wsjtx-2.3.0-rc2/wsjtx-prefix/src/wsjtx-build/CMakeFiles/CheckTypeSize/HAMLIB_OLD_CACHING.c:24:22:
 error: ‘CACHE_ALL’ undeclared here (not in a function); d$
#define SIZE (sizeof(CACHE_ALL))
^
/home/myuser/wsjtx/wsjtx-2.3.0-rc2/build/wsjtx-2.3.0-rc2/wsjtx-prefix/src/wsjtx-build/CMakeFiles/CheckTypeSize/HAMLIB_OLD_CACHING.c:26:12:
 note: in expansion of macro ‘SIZE’
('0' + ((SIZE / 1)%10)),
^~~~
make[5]: *** [CMakeFiles/cmTC_32eb3.dir/build.make:66: 
CMakeFiles/cmTC_32eb3.dir/HAMLIB_OLD_CACHING.c.o] Error 1
make[5]: Leaving directory 
'/home/myuser/wsjtx/wsjtx-2.3.0-rc2/build/wsjtx-2.3.0-rc2/wsjtx-prefix/src/wsjtx-build/CMakeFiles/CMakeTmp'
make[4]: *** [Makefile:121: cmTC_32eb3/fast] Error 2
make[4]: Leaving directory 
'/home/myuser/wsjtx/wsjtx-2.3.0-rc2/build/wsjtx-2.3.0-rc2/wsjtx-prefix/src/wsjtx-build/CMakeFiles/CMakeTmp'
/home/myuser/wsjtx/wsjtx-2.3.0-rc2/build/wsjtx-2.3.0-rc2/wsjtx-prefix/src/wsjtx-build/CMakeFiles/CheckTypeSize/HAMLIB_OLD_CACHING.c:


73, KD0KZE / Paul___
wsjt-devel mailing list
wsjt-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wsjt-devel

Re: [wsjt-devel] compilation using Debian Stable

[Paul Bramscher]

On 10/24/2020 12:03 PM, Christoph Berg wrote:
> Am 24. Oktober 2020 16:05:19 MESZ schrieb Claude Frantz
> :
> 
> Hello all,
> 
> which problems do I have to expect when trying to compile the source 
> code from the git repo using Debian STABLE ? Which are the solutions 
> available ?
> 
> Best wishes,
> Claude (DJ0OT)
> 
> wsjt-devel mailing list
> wsjt-devel@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/wsjt-devel 
> 
> 
> 
> I've recently added wsjtx 2.2.2 to buster-backports. So you can just
> install from there, or "apt build-dep wsjtx".

I've compiled WSJT-X for a number of years now on Debian without
significant issues.  I was able to resolve all dependencies from within
the regular repo.

Currently running Debian 10 Buster, fully patched to the current
version.  If you search the forum archives for my callsign you should be
able to see a couple related discussion threads with specific information.

Yesterday I compiled 2.3.0-rc1 on my Debian 10 machine that runs WSJT-X
2.2.2 and encountered no new dependency issues.  So once you get the
initial dependencies met, it becomes smoother sailing.

I am currently working 30M FT8 with a Kenwood TS-590.  No issues
encountered yet.

73, KD0KZE / Paul



___
wsjt-devel mailing list
wsjt-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wsjt-devel

Re: [wsjt-devel] WSJT-X 2.2.0 GA release

[Paul Bramscher]

Greetings--

Compiled from source on a fully patched Linux Debian 10, Kenwood
TS-590S, running for a few hours today, no bugs noted (for me).  No new
dependencies needed for the compile since the last version.

A big thank you to the team for continuing to develop this great program!

73, KD0KZE / Paul Bramscher

On 6/2/2020 8:53 AM, Joe Taylor wrote:
> The WSJT Development Group is pleased to announce the general
> availability (GA) release of WSJT-X Version 2.2.0.  A brief summary of
> new features is provided here; for further details see the Release Notes:
> 
> http://physics.princeton.edu/pulsar/k1jt/Release_Notes.txt
> 
> ... and of course the updated WSJT-X 2.2 User Guide:
> 
> http://www.physics.princeton.edu/pulsar/K1JT/wsjtx-doc/wsjtx-main-2.2.0.html#NEW_FEATURES
> 
> 
> New Features in WSJT-X 2.2.0:
> 
>  - Significant improvements to the decoders for FT4, FT8, JT4, JT65,
>    and WSPR.
> 
>  - New format for "EU VHF Contest" Tx2 and Tx3 messages
> 
>    When "EU VHF Contest" is selected, the Tx2 and Tx3 messages (those
>    conveying signal report, serial number, and 6-character locator)
>    now use hashcodes for both callsigns.  This change is NOT backward
>    compatible with earlier versions of _WSJT-X_, so all users of EU
>    VHF Contest messages should be sure to upgrade to version 2.2.0.
> 
>  - Accessibility
> 
>    Keyboard shortcuts have been added as an aid to accessibility:
>    Alt+R sets Tx4 message to RR73, Ctrl+R sets it to RRR.
> 
>    As an aid for partial color-blindness, the "inverted goal posts"
>    marking Rx frequency on the Wide Graph's frequency scale are now
>    rendered in a darker shade of green.
> 
>  - User Interface Translations have been enabled.  Translations are
>    now available for Catalan, Spanish, Japanese, Chinese, and Hong
>    Kong Chinese.  Additiional languages will follow, when available.
> 
>    Note that UI translation is automatic, based on your system primary
>    language. If you do not want the WSJT-X UI translated to your local
>    language then start WSJT-X with the '--language=en' command line
>    option:
> 
>    wsjtx --language=en
> 
>    If you wish to contribute by authoring WSJT-X UI translations
>    please join the new discussion group wsjtx-l...@groups.io
>    (https://groups.io/g/wsjtx-l10n), where help from other translation
>    authors and coordination with the development team is available.
> 
>  - Minor enhancements and bug fixes
> 
>    "Save None" now writes no .wav files to disk, even temporarily.
> 
>    An explicit entry for "WW Digi Contest" has been added to
>    "Special operating activities" on the "Settings | Advanced" tab.
> 
>    Contest mode FT4 now always uses RR73 for the Tx4 message.
> 
>    The Status bar now displays the number of decodes found in the
>    most recent Rx sequence.
> 
>    The "Highlight Callsign" UDP message has been enhanced to allow
>    clearing of old highlighting for a specified callsign. Please note
>    a recommended restriction on the use of this message in the
>    documentation here: https://tinyurl.com/y85nc3tg
> 
>  - Hamlib - this library which we use for direct rig control has had
>    many defect repairs and enhancements, we thank the contributors to
>    that project for their work.
> 
> Upgrading from earlier versions of WSJT-X should be seamless.  There is
> no need to uninstall a previous version or move any files.
> 
> Please do not continue to use any release candidate -- that is, any beta
> release with "-rc#" in the version name.
> 
> Links to installation packages for Windows, Linux, and Macintosh are
> available here:
> http://physics.princeton.edu/pulsar/k1jt/wsjtx.html
> 
> You can also download the packages from our SourceForge site:
> https://sourceforge.net/projects/wsjt/files/
> It may take a short time for the SourceForge site to be updated.
> 
> WSJT-X is licensed under the terms of Version 3 of the GNU General
> Public License (GPL).  Development of this software is a cooperative
> project to which many amateur radio operators have contributed.  If you
> use our code, please have the courtesy to let us know about it.  If you
> find bugs or make improvements to the code, please report them to us in
> a timely fashion.
> 
> We hope you will enjoy using WSJT-X Version 2.2.0.
> 
>  -- 73 from Joe, K1JT, Steve, K9AN, and Bill, G4WJS,
>  for the entire WSJT Development Group
> 
> 
> ___
> wsjt-devel mailing list
> wsjt-devel@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/wsjt-devel



___
wsjt-devel mailing list
wsjt-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wsjt-devel

Re: [wsjt-devel] exporting from adi

[Paul Bramscher]

Hi Claude,

Thanks, I'll take a look at that script.  Of course I locally keep and
backup all logs that I've ever generated.  If this tool automates these
kinds of merging issues, I'll certainly experiment with it.

73, KD0KZE / Paul

On 5/22/2020 1:06 PM, Claude Frantz wrote:
> On 5/22/20 7:22 PM, Paul Bramscher wrote:
> 
> Hi Paul & all,
> 
>> What I've done is maintain two local logs: WSJT-X's native log and XLog
>> for everything else.  fldigi will auto-ingest into XLog, and I can
>> easily enough create Phone and other entries manually in XLog.
> 
> Please note that fldigi is able to change entries in its log.
> Unfortunately such updates are not passed to Xlog.
> 
>> I periodically use TQSL to upload WSJT-X contacts to Logbook of the
>> World.  To make this more efficient, I examine my past activity date on
>> LoTW's interface and use my last upload date as the cut-off date for new
>> QSO's to upload.
> 
>> I also upload XLog logs there, so LoTW is the place where they all get
>> combined.  Then I occasionally export those and upload them into QRZ for
>> good measure.
> 
> adifmerg is an excellent program to merge ADIF log files.
> 
> Unfortunately, LoTW is not a good place to combine logs files because
> only a limited number of ADIF fields are maintained. Please remember
> that paper QSL exist too and many other things which are ignored by
> LoTW. Finally, only a locally maintained ADIF file can help to maintain
> all the information. And adifmerg can help you to do it. This is the way
> I'm going. With the optional addition of few user defined fields, such a
> locally stored ADIF file can be the base from which one an appropriate
> program can automatically generate detailed paper QSL cards. Of course,
> received QSL cards have to be mentioned in the appropriate records of
> the ADIF file.
> 
> Best wishes,
> Claude (DJ0OT)
> 
> 
> ___
> wsjt-devel mailing list
> wsjt-devel@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/wsjt-devel



___
wsjt-devel mailing list
wsjt-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wsjt-devel

Re: [wsjt-devel] exporting from adi

[Paul Bramscher]

What I've done is maintain two local logs: WSJT-X's native log and XLog
for everything else.  fldigi will auto-ingest into XLog, and I can
easily enough create Phone and other entries manually in XLog.

I periodically use TQSL to upload WSJT-X contacts to Logbook of the
World.  To make this more efficient, I examine my past activity date on
LoTW's interface and use my last upload date as the cut-off date for new
QSO's to upload.

I also upload XLog logs there, so LoTW is the place where they all get
combined.  Then I occasionally export those and upload them into QRZ for
good measure.

73, KD0KZE / Paul

On 5/20/2020 8:17 PM, Michelle Sack via wsjt-devel wrote:
> I'm new to FT8 and WSJT software. Is a way to export from the log only
> the recent contacts? This way I don't make duplicates in my logging
> programs but still keep contacts in the WSJT log for notifications of
> new (preventing duplicate contacts in FT8). 
> Thanks
> Michelle N3YRZ
> 
> 
> ___
> wsjt-devel mailing list
> wsjt-devel@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/wsjt-devel
> 



___
wsjt-devel mailing list
wsjt-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wsjt-devel

Re: [wsjt-devel] WSJT-X 2.1.1 GA release

[Paul Bramscher]

Bummer about Icom bug.  For what it's worth, I compiled it fine just now on 
Debian Linux 10.x + Kenwood TS-590, split mode.  No additional dependencies 
were needed since 2.1.0.  Haven't tested much yet, but haven't seen any issues 
so far.

73, KD0KZE / Paul

> On November 25, 2019 at 6:15 PM Bill Somerville  wrote:
> 
> 
> On 25/11/2019 18:40, Joe Taylor wrote:
> > The WSJT Development Group is pleased to announce the general 
> > availability (GA) release of WSJT-X Version 2.1.1. 
> 
> Hi all WSJT-X users,
> 
> thanks for the issue reports from Icom users who have not been able to 
> use WSJT_X v2.1.1. We will get a fixed version out ASAP.
> 
> If you are experiencing an issue with a rig control error:
> 
> "Hamlib error: Command rejected by the rig while getting current 
> frequency."
> 
> with your Icom rig then for now you should revert to WSJT-X v2.1.0 
> (v2.0.1 for macOS Catalina users) which can be found here:
> 
> https://sourceforge.net/projects/wsjt/files/wsjtx-2.1.0/
> 
> (https://sourceforge.net/projects/wsjt/files/wsjtx-2.0.1/)
> 
> Apologies for the inconvenience
> 73
> Bill
> G4WJS.
> 
> 
> 
> ___
> wsjt-devel mailing list
> wsjt-devel@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/wsjt-devel


___
wsjt-devel mailing list
wsjt-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wsjt-devel

[wsjt-devel] Debian 10 Linux WSJT-X Compile + CMake Policy Warning

[Paul Bramscher]

I've finally upgraded my last Linux PC to Debian 10, the most complex in
my shack (compiled executables for fldigi, flrig, TQSL, and of course
WSJT-X among several other apps and stacks).

Overall the process went smoothly, since I've heavily documented what
I've done previously.

Apologies if this has been mentioned in a thread already -- I did a
cursory search and found only a passing reference to it on the list.
But I noticed this warning message regarding policy settings for CMake.
Debian 10 is using cmake version 3.13.4.

Ultimately I ignored the message and it seems to have compiled perfectly
fine, but possibly the WSJT-X developers may keep an eye out on the
add_custom_target commands -- since future cmake versions might not
merely throw a warning:

cmake -DCMAKE_INSTALL_PREFIX=../../install/ -DWSJT_SKIP_MANPAGES=ON
-DWSJT_GENERATE_DOCS=OFF ../wsjtx-2.1.0

-- The C compiler identification is GNU 8.3.0
-- The CXX compiler identification is GNU 8.3.0
-- Check for working C compiler: /usr/bin/cc
-- Check for working C compiler: /usr/bin/cc -- works
-- Detecting C compiler ABI info
-- Detecting C compiler ABI info - done
-- Detecting C compile features
-- Detecting C compile features - done
-- Check for working CXX compiler: /usr/bin/c++
-- Check for working CXX compiler: /usr/bin/c++ -- works
-- Detecting CXX compiler ABI info
-- Detecting CXX compiler ABI info - done
-- Detecting CXX compile features
-- Detecting CXX compile features - done
-- Found Git: /usr/bin/git (found version "2.20.1")
CMake Warning (dev) at CMakeLists.txt:165 (add_custom_target):
  Policy CMP0037 is not set: Target names should not be reserved and should
  match a validity pattern.  Run "cmake --help-policy CMP0037" for policy
  details.  Use the cmake_policy command to set the policy and suppress this
  warning.

  The target name "install" is reserved or not valid for certain CMake
  features, such as generator expressions, and may result in undefined
  behavior.
This warning is for project developers.  Use -Wno-dev to suppress it.



73, KD0KZE / Paul



___
wsjt-devel mailing list
wsjt-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wsjt-devel

Re: [wsjt-devel] Moving WSJT-X from Debian 9 to 10

[Paul Bramscher]

Hi Bill,

I save everything, and will restore probably 99%.  One area where I give a 
little more scrutiny is for apps that I've compiled (against older libraries).  
I'm happy to let the newly-compiled application repopulate as much as possible 
-- so long as I can avoid re-tweaking my settings.  Also, there could be 
old/obsolete files in settings-related directories that no longer apply to 
modern versions of things.

My ALL.TXT is now 1.3 GB, going back to May 2015.  Space is no issue, and I'm 
happy to preserve that for posterity.  :-)

73, KD0KZE / Paul

> On July 30, 2019 at 2:28 PM Bill Somerville  wrote:
> 
> 
> On 30/07/2019 20:21, Paul Bramscher wrote:
> > But I've got a general question with ~/.local/share/WSJT-X.  What are 
> > the minimally useful files to copy over, to preserve settings and 
> > logs?  The entire directory (except the contents of 'save') -- or is 
> > there a smaller subset?
> 
> Hi Paul,
> 
> I would transfer the whole directory and it's contents. You will also 
> want to copy the settings file which is in ~/.config/ .It will not 
> amount to a great deal of space. If you have a lot of saved .WAV files 
> you might deleted them with the "Menu->File->Delete all *.wav and *.c2 
> files in SaveDir" button before archiving the log files directory.
> 
> I don't understand why you would not simply backup and restore to the 
> new system your entire /home directory, what do you hope to gain by 
> scrapping all user files?
> 
> 73
> Bill
> G4WJS.
> 
> 
> 
> ___
> wsjt-devel mailing list
> wsjt-devel@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/wsjt-devel


___
wsjt-devel mailing list
wsjt-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wsjt-devel

[wsjt-devel] Moving WSJT-X from Debian 9 to 10

[Paul Bramscher]

I'll soon be upgrading my Debian 9.x to 10.0 Buster.  And while it's possible 
to perform an in-place upgrade I usually take the opportunity to replace the 
hard drive and do a fresh install entirely.  I've been compiling WSJT-X for 
awhile now and have had no problems doing so.


But I've got a general question with ~/.local/share/WSJT-X.  What are the 
minimally useful files to copy over, to preserve settings and logs?  The entire 
directory (except the contents of 'save') -- or is there a smaller subset?


73, KD0KZE / Paul
___
wsjt-devel mailing list
wsjt-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wsjt-devel

Re: [wsjt-devel] New library required for building: qt5-linguist

[Paul Bramscher]

I successfully compiled the newest WSJT-X 2.1.0 on Debian 9.9 this morning, and 
qttools5-dev-tools was indeed the new package dependency.  In the next couple 
weeks I'll be upgrading the shack to Debian 10.

As a side note, I should really check the Debian site more often.  The first 
inkling I got that Debian 10 Buster was released was from a thread a few days 
ago in this very list.

73, KD0KZE / Paul

> On July 15, 2019 at 3:50 PM Bill Somerville  wrote:
> 
> 
> On 15/07/2019 21:39, Dave Slotter, W3DJS wrote:
> > There appears to be a new requirement to build under Ubuntu 16.xx. 
> > CMake seems to now require Qt5LinguistTools in order to build, whereas 
> > that was not required in earlier release candidate builds of 2.1.0.
> >
> > Where do I get this library to satisfy CMake? (Thanks in advance.)
> >
> Hi Dave,
> 
> I believe the required package is qttools5-dev-tools .
> 
> Apologies for the INSTALL file not being updated to reflect that new 
> requirement, it will be corrected for the next release.
> 
> 73
> Bill
> G4WJS.
> 
> 
> 
> ___
> wsjt-devel mailing list
> wsjt-devel@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/wsjt-devel


___
wsjt-devel mailing list
wsjt-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wsjt-devel

Re: [wsjt-devel] installing v. 2.0.0 on Debian stretch

[Paul Bramscher]

> On December 18, 2018 at 7:14 PM Paul Bramscher  wrote:
> 
> 
> On 12/18/2018 10:21 AM, Rich Griffiths wrote:
> > I'd like to chat with someone who has a working install of version 2.0.0
> > on Debian stretch.  If you're interested, please contact me off-list at
> > rich-at-w2rg-dot-net.
> > 
> > 73
> > 
> > ... Rich   W2RG
> > 
> 
> Here's what I've been doing with WSJT-X 2.0.0 on Debian stretch.  These
> steps assume you'll not be compiling with local/integrated
> documentation.  That entails numerous extra dependencies (though I have
> waded through it) and more disk space.  I just use the online docs.
> 
> It also suggests a directory structure similar to what Greg's JTSDK
> employed, so you can have multiple instances for different future minor
> dot releases.  Optional, and the directory names can be changed to
> something appropriate.  The names "build" and "install" for
> subdirectories work for me.
> 
> $HOME/
>   wsjtx/
>   wsjtx-2.0.0/
>   build/
>   wsjtx-2.0.0/ (source)
>   install/ (compiled executables)
> 
> 1) Install dependencies
> 
> sudo apt install build-essential git cmake gfortran libfftw3-dev \
> qtbase5-dev libqt5serialport5-dev libqt5multimedia5-plugins \
> libqt5sql5-sqlite autoconf automake libtool texinfo libusb-1.0-0-dev \
> libudev-dev qtmultimedia5-dev
> 
> 2) Download the source .tgz file from SourceForge or the project's main
> site (my browser puts it into ~/Downloads by default).  Setup the
> directory structure, copy the source and unpack it (change for
> different/future versions as needed):
> 
> mkdir -p ~/wsjtx/wsjtx-2.0.0/build
> mkdir -p ~/wsjtx/wsjtx-2.0.0/install
> 
> cd ~/wsjtx/wsjtx-2.0.0/build
> cp ~/Downloads/wsjtx-2.0.0.tgz .
> tar xf wsjtx-2.0.0.tgz
> 
> 3) Configure the package:
> 
> cd ~/wsjtx/wsjtx-2.0.0/build/wsjtx-2.0.0
> 
> cmake -DCMAKE_INSTALL_PREFIX=../../install/ -DWSJT_SKIP_MANPAGES=ON
> -DWSJT_GENERATE_DOCS=OFF ../wsjtx-2.0.0
> 
> 4) Compile the package:
> 
> cmake --build ~/wsjtx/wsjtx-2.0.0/build/wsjtx-2.0.0 --target install -- -j
> 
> 5) Execute:
> 
> cd  ~/wsjtx/wsjtx-2.0.0/bin
> ./wsjtx

Slight correction -- it should read like this:

cd  ~/wsjtx/wsjtx-2.0.0/install/bin
./wsjtx


___
wsjt-devel mailing list
wsjt-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wsjt-devel

Re: [wsjt-devel] installing v. 2.0.0 on Debian stretch

[Paul Bramscher]

On 12/18/2018 10:21 AM, Rich Griffiths wrote:
> I'd like to chat with someone who has a working install of version 2.0.0
> on Debian stretch.  If you're interested, please contact me off-list at
> rich-at-w2rg-dot-net.
> 
> 73
> 
> ... Rich   W2RG
> 

Here's what I've been doing with WSJT-X 2.0.0 on Debian stretch.  These
steps assume you'll not be compiling with local/integrated
documentation.  That entails numerous extra dependencies (though I have
waded through it) and more disk space.  I just use the online docs.

It also suggests a directory structure similar to what Greg's JTSDK
employed, so you can have multiple instances for different future minor
dot releases.  Optional, and the directory names can be changed to
something appropriate.  The names "build" and "install" for
subdirectories work for me.

$HOME/
wsjtx/
wsjtx-2.0.0/
build/
wsjtx-2.0.0/ (source)
install/ (compiled executables)

1) Install dependencies

sudo apt install build-essential git cmake gfortran libfftw3-dev \
qtbase5-dev libqt5serialport5-dev libqt5multimedia5-plugins \
libqt5sql5-sqlite autoconf automake libtool texinfo libusb-1.0-0-dev \
libudev-dev qtmultimedia5-dev

2) Download the source .tgz file from SourceForge or the project's main
site (my browser puts it into ~/Downloads by default).  Setup the
directory structure, copy the source and unpack it (change for
different/future versions as needed):

mkdir -p ~/wsjtx/wsjtx-2.0.0/build
mkdir -p ~/wsjtx/wsjtx-2.0.0/install

cd ~/wsjtx/wsjtx-2.0.0/build
cp ~/Downloads/wsjtx-2.0.0.tgz .
tar xf wsjtx-2.0.0.tgz

3) Configure the package:

cd ~/wsjtx/wsjtx-2.0.0/build/wsjtx-2.0.0

cmake -DCMAKE_INSTALL_PREFIX=../../install/ -DWSJT_SKIP_MANPAGES=ON
-DWSJT_GENERATE_DOCS=OFF ../wsjtx-2.0.0

4) Compile the package:

cmake --build ~/wsjtx/wsjtx-2.0.0/build/wsjtx-2.0.0 --target install -- -j

5) Execute:

cd  ~/wsjtx/wsjtx-2.0.0/bin
./wsjtx

Optional:
I use the MATE desktop and create a launcher icon for each version that
I've compiled under ~/wsjtx/wsjtx-2.x.x/.  I just reference the wsjtx
executable (in install/bin) and pixmap icon for each version (in
install/share/pixmaps).

I've thought about tossing these steps into a script to minimize typing,
and changing the directories names a bit, but so far it works for me.
Maybe others can chime in with additional suggestions?

73, KD0KZE / Paul


___
wsjt-devel mailing list
wsjt-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wsjt-devel

Re: [wsjt-devel] installing v. 2.0.0 on Debian stretch

[Paul Bramscher]

Hi Rich,

I've compiled all WSJT-X 2.0.0 RC's and the general release without a hitch -- 
and confirmed the process on a couple fresh Debian stretch machines also.  
Works great.

What kind of issues are you running into?

73, KD0KZE / Paul


> On December 18, 2018 at 10:21 AM Rich Griffiths  wrote:
> 
> 
> I'd like to chat with someone who has a working install of version 2.0.0 
> on Debian stretch.  If you're interested, please contact me off-list at 
> rich-at-w2rg-dot-net.
> 
> 73
> 
> ... Rich   W2RG
> 
> -- 
> 
> Rich ... W2RG
> 
> Sent by Debian Linux - Microsoft free since 2003
> 
> 
> 
> ___
> wsjt-devel mailing list
> wsjt-devel@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/wsjt-devel


___
wsjt-devel mailing list
wsjt-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wsjt-devel

Re: [wsjt-devel] WSJT-X versions distribution as per: https://pskreporter.info/cgi-bin/pskstats.pl

[Paul Bramscher]

> On December 13, 2018 at 12:53 PM Bill Somerville  
> wrote:
> 
> On 13/12/2018 18:38, Paul Bramscher wrote:
> 
> > > 
> > Is it possible to infer operating system from the version 
> > "signature" as reported on pskreporter?  I see that the heaviest example of 
> > 2.0.0 usage is "WSJT-X v2.0.0 784f75".  Judging from the file download 
> > stats on SourceForge, I would presume that to be the Windows build/release?
> > 
> > 
> > Only a few dozen of us are showing up concisely as "WSJT-X v2.0.0". 
> >  Again judging from the download activity (and my own case) I would presume 
> > these are folks who built from source?
> > 
> > 
> > > 
> Hi Paul,
> 
> we do not distinguish by platform in spotted data, why should we the 
> application is the same on all platforms. We do have a rough feel for 
> distribution across platforms from the SourceForge download stats. Although 
> many download from the project web site where stats are not kept and those 
> with RPM type Linux distributions may get their fresh versions from COPR and 
> soon from the official repos.
> 
> the version tag is just that, it is the git SHA of the tag that defines 
> the version's sources in the repository:
> 
> https://sourceforge.net/p/wsjt/wsjtx/ci/wsjtx-2.0.0/tree/
> 
> Its there in the Tree address at the top. Again it is the same for all 
> platforms as they are built from the same tag.
> 
> You are correct about builds from the source tarball, the tag is not 
> included, mainly because it may have been patched since we have no control on 
> exactly what is built in that case.
> 
> 73
> Bill
> G4WJS.
> 

Hi Bill,


I'm just generally interested in Linux adoption in amateur radio for 
casual/selfish reasons.  More useful operating information (to me) passed to 
pskreporter is when people take the trouble to describe antennas in WSJT.  But 
that free text field can't be easily normalized for any sort of broad 
statistical use -- such as influencing one's next purchase or installation 
decision.  Mainly I'm just very grateful that you can tell at a glance whether 
a band is open.


73, KD0KZE / Paul
___
wsjt-devel mailing list
wsjt-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wsjt-devel

Re: [wsjt-devel] WSJT-X versions distribution as per: https://pskreporter.info/cgi-bin/pskstats.pl

[Paul Bramscher]

> On 13/12/2018 15:07, Marco Calistri wrote:
> 
> > > 
> > Interesting result (in the attached file)
> > 
> > -- 73 de Marco, PY1ZRJ
> > 
> > > 
> Hi Marco,
> 
> I assume that is derived from the stats page of PSKReporter.info, you 
> should be aware that there are some skews in that data source. It tends to 
> double report for a while after a station switches versions, I assume because 
> records sent by users of old versions are kept for a while and still count 
> even after they have upgraded. There are also an unknown number of users who 
> may never have enabled PSKReporter spotting (only the spotting station record 
> has version used data) and others may switch it off or not have Internet 
> connectivity.
> 
> Thanks for the data.
> 
> 73
> Bill
> G4WJS.
> 


Is it possible to infer operating system from the version "signature" as 
reported on pskreporter?  I see that the heaviest example of 2.0.0 usage is 
"WSJT-X v2.0.0 784f75".  Judging from the file download stats on SourceForge, I 
would presume that to be the Windows build/release?


Only a few dozen of us are showing up concisely as "WSJT-X v2.0.0".  Again 
judging from the download activity (and my own case) I would presume these are 
folks who built from source?


Thanks again, Bill, for the e-mail exchanges a few weeks ago re:Debian.  I've 
successfully built all the RC's and now the final release, for Debian 9.6 
"stretch" (the current version) without trouble.  I sort of emulated the old 
JTSDK's directory layout, and can have multiple versions compiled, making 
allowance for future minor dot releases.  This way I can revert back to an 
older 2.x if I encounter future issues without having to rebuild anything.


73, KD0KZE / Paul
___
wsjt-devel mailing list
wsjt-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wsjt-devel

[wsjt-devel] Issues getting RC4 to work with Debian 9.6

[Paul Bramscher]

I've been having some issues both in compiling and attempting to install the 
Debian AMD64 .deb package.  I'm running Debian 9.6, fully patched.  When I 
attempt to install the supplied .deb, it responds as follows.  I checked a few 
and at least some dependencies may not be met in current Stretch repos.


Selecting previously unselected package wsjtx.
(Reading database ... 234387 files and directories currently installed.)
Preparing to unpack wsjtx_2.0.0-rc4_amd64.deb ...
Unpacking wsjtx (2.0.0-rc4) ...
dpkg: dependency problems prevent configuration of wsjtx:
wsjtx depends on libc6 (>= 2.27); however:
Version of libc6:amd64 on system is 2.24-11+deb9u3.
wsjtx depends on libgfortran4 (>= 7); however:
Package libgfortran4 is not installed.
wsjtx depends on libqt5gui5 (>= 5.8.0); however:
Version of libqt5gui5:amd64 on system is 5.7.1+dfsg-3+b1.
wsjtx depends on libstdc++6 (>= 7); however:
Version of libstdc++6:amd64 on system is 6.3.0-18+deb9u1.

dpkg: error processing package wsjtx (--install):
dependency problems - leaving unconfigured
Processing triggers for desktop-file-utils (0.23-1) ...
Processing triggers for mime-support (3.60) ...
Processing triggers for man-db (2.7.6.1-2) ...
Errors were encountered while processing:
wsjtx


When I attempted to compile from source, I had to first run this:


autoreconf --install


Then I compiled hamlib, then I had to instruct wsjt-x where to find hamlib (I'm 
guessing at the flag name):


cmake -D CMAKE_CXX_COMPILER="/usr/bin/g++" -D 
CMAKE_Fortran_COMPILER="/usr/bin/gfortran-6" -D 
hamlib_LIBRARY_DIRS="/usr/local/lib" -D 
CMAKE_INSTALL_PREFIX=~/.local/wsjt-x-2.0.0-rc4 .


cmake --build . --target install


And it ultimately failed with this:


[ 49%] Linking CXX executable wsjtx
libwsjt_qt.a(HamlibTransceiver.cpp.o): In function 
`HamlibTransceiver::do_tx_frequency(unsigned long long, Transceiver::MODE, 
bool)':
HamlibTransceiver.cpp:(.text._ZN17HamlibTransceiver15do_tx_frequencyEyN11Transceiver4MODEEb+0x3e9):
 undefined reference to `rig_set_split_freq_mode'
collect2: error: ld returned 1 exit status
CMakeFiles/wsjtx.dir/build.make:1057: recipe for target 'wsjtx' failed
make[2]: *** [wsjtx] Error 1
CMakeFiles/Makefile2:182: recipe for target 'CMakeFiles/wsjtx.dir/all' failed
make[1]: *** [CMakeFiles/wsjtx.dir/all] Error 2
Makefile:149: recipe for target 'all' failed
make: *** [all] Error 2


Has anyone gotten RC4 working on Debian 9?  Whether compiled or just using a 
pre-built package.  Thanks!


73, KD0KZE / Paui

___
wsjt-devel mailing list
wsjt-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wsjt-devel

Re: [wsjt-devel] WSJT-X & JTSDK future?

[Paul Bramscher]

Hi folks--

Thanks for the additional tips -- my earlier notes were from a rather hasty 
real-time effort.  I'll combine the additional commentary, clean up the notes, 
and try it again to validate.

I forget why I issued cmake as sudo.  Probably a perms issue at one point, most 
certainly my fault since I was also installing the additional packages ad hoc.  
Best to do that in a separate window or as a separate pre-build step.  I've got 
a better grasp on it at this point.  It would be easy enough to simply install 
the .deb, but it's gratifying (and a good learning exercise) to compile one's 
amateur radio apps from source also.

73, KD0KZE / Paul

> On October 21, 2018 at 3:03 AM Bill Somerville  wrote:
> 
> 
> On 21/10/2018 04:01, Paul Bramscher wrote:
> > These appeared to be necessary dependencies:
> > g++
> > gfortran-6
> > libfftw3-dev
> > libqt5x11extras5-dev
> > lib-qt5serialport
> > lib-qt5serialport-dev
> > libtool
> > libudev-dev
> > libusb-1.0.0-dev
> > python-pkgconfig
> > python-pyqt5
> > qtmultimedia5-dev
> > texinfo
> >
> > sudo cmake -D CMAKE_CXX_COMPILER="/usr/bin/g++" -D
> > CMAKE_Fortran_COMPILER="/usr/bin/gfortran-6" -D
> > CMAKE_INSTALL_PREFIX=~/.local .
> >
> > sudo cmake --build . --target install
> >
> > Possibly necessary also:
> >
> > python-pyqt5.qtmultimedia
> >
> Hi Paul,
> 
> you may find these comments helpful.
> 
> 1) there are no Python dependencies for WSJT-X,
> 2) there should be no need to install both a -dev and run tie version of 
> a package, installing the -dev package alone will also install the run 
> time components,
> 3) you can avoid having to install the large texinfo package by 
> configuring the WSJT-X build to skip the build of the manpages (-D 
> WSJT_SKIP_MANPAGES),
> 4) never run a CMake configuration with root privileges, also in your 
> case as your install prefix is in your home directory you so you do not 
> need root privileges for the CMake build command either,
> 5) CMake should discover the compilers it needs by itself,
> 6) you should create a build directory and run your CMake commands with 
> that as the current working directory, building in the source tree is 
> strongly discouraged. Simply select the source tree root in the CMake 
> configuration command by specifying it as the last parameter instead of 
> '.' as you have above.
> 
> 73
> Bill
> G4WJS.
> 
> 
> 
> ___
> wsjt-devel mailing list
> wsjt-devel@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/wsjt-devel


___
wsjt-devel mailing list
wsjt-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wsjt-devel

Re: [wsjt-devel] WSJT-X & JTSDK future?

[Paul Bramscher]

Hi Adam--

I compiled it yesterday, but these notes are not guaranteed to be 100%.
This was done to a Debian 9 machine, fully patched, which had previously
used the JTSDK to build WSJT-X 1.9.1.  I took the latest source snapshot
for 2.0.0 RC3.  These are new dependencies and musings/considerations
(written for myself):

Create a jtsource directory and decompress the source there.
Decide on a destination executable directory and create that also.
For example .local and/or a version-specific directory name.  And that
should be indicated in the later cmake command (example below is only
.local):

These appeared to be necessary dependencies:
g++
gfortran-6
libfftw3-dev
libqt5x11extras5-dev
lib-qt5serialport
lib-qt5serialport-dev
libtool
libudev-dev
libusb-1.0.0-dev
python-pkgconfig
python-pyqt5
qtmultimedia5-dev
texinfo

sudo cmake -D CMAKE_CXX_COMPILER="/usr/bin/g++" -D
CMAKE_Fortran_COMPILER="/usr/bin/gfortran-6" -D
CMAKE_INSTALL_PREFIX=~/.local .

sudo cmake --build . --target install

Possibly necessary also:

python-pyqt5.qtmultimedia

I'm not sure this helps anyone, but it compiled on Debian for me -- and
something similar should work for most Debian-based distros.

73, KD0KZE / Paul


On 10/20/2018 1:56 PM, Adam Schaible wrote:
> Paul - 
> 
> Totally new to this list (in fact this is my first post here) but I've
> also been compiling the 2.0.0 RC releases from source for Linux, not by
> choice but by necessity (my current desktop distro of choice uses
> neither .deb nor .rpm installers) and have run into the usual dependency
> wackiness at build time. I decided early on to ignore JTSDK as the new
> version doesn't support Linux and the older version is several years old.
> 
> I've powered through the error messages line by line, installing all the
> needed dependencies one by one and WSJT-X is now usable but a bit buggy,
> was planning a side-by-side test with the latest RC3 .rpm on my Fedora
> box some time in the next couple days. Not sure how much the rest of
> this list (as majority non-Linux users) is interested in our adventures,
> but I'd be interested in sharing build notes with you either here or
> outside the list if you're game.
> 
> 73 de Adam KB3ZUV
> 
> 
> 
> On Sat, Oct 20, 2018, at 11:13 AM, Paul Bramscher wrote:
>>
>> Great to hear about the upcoming 2.0.0 major release of WSJT-X.  I've
>> been compiling my own versions of WSJT-X with the JTSDK for the past
>> few years (Debian Linux, AMD64).  Will that project on SourceForge be
>> updated when the new general release becomes available?  The JTSDK
>> is/was a really handy tool for keeping things (incl. hamlib) up to date.
>>
>>
>> I was able to compile 2.0.0 RC3 manually from source yesterday, but it
>> was a bit tedious (and some guesswork) to chase down all necessary
>> dependencies. 
>>
>>
>> Thanks,
>>
>> 73, KD0KZE / Paul
>>
>>  
>> _
>> wsjt-devel mailing list
>> wsjt-devel@lists.sourceforge.net <mailto:wsjt-devel@lists.sourceforge.net>
>> https://lists.sourceforge.net/lists/listinfo/wsjt-devel
> 
> 
> 
> 
> 
> ___
> wsjt-devel mailing list
> wsjt-devel@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/wsjt-devel
> 



___
wsjt-devel mailing list
wsjt-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wsjt-devel

[wsjt-devel] WSJT-X & JTSDK future?

[Paul Bramscher]

Great to hear about the upcoming 2.0.0 major release of WSJT-X.  I've been 
compiling my own versions of WSJT-X with the JTSDK for the past few years 
(Debian Linux, AMD64).  Will that project on SourceForge be updated when the 
new general release becomes available?  The JTSDK is/was a really handy tool 
for keeping things (incl. hamlib) up to date.


I was able to compile 2.0.0 RC3 manually from source yesterday, but it was a 
bit tedious (and some guesswork) to chase down all necessary dependencies. 


Thanks,

73, KD0KZE / Paul
___
wsjt-devel mailing list
wsjt-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wsjt-devel

[wsjt-devel] Possible bug (?) 1.9.1 with numeric msg

[Paul Bramscher]

Running WSJT-X 1.9.1 r8747 compiled on Debian (AMD64) Linux.   A couple days 
ago an operator on 20M FT8 was calling CQ 052 {his call | his grid}.  Out of 
curiosity I clicked his message in the band activity pane.  My radio then 
switched to 14.052 MHz and the freq. pane turned red (indicating a non-standard 
FT8 freq.) .  In the Rx Frequency pane, I got purple messages stating "QSY 
14.052".


Is this a bug or a feature that I've not seen yet?


Regards,

73, KD0KZE / Paul
___
wsjt-devel mailing list
wsjt-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wsjt-devel

Re: [wsjt-devel] Build wsjt-x on Debian

[Paul Bramscher]

I'm building on Debian 9.4 and ran into some dependency issues also. I have 
this saved in my notes, though I'm not 100% sure the first two were required 
(it's been a couple months since I first did this):

libusb-ocaml
libusb-ocaml-dev
libudev-dev

Would be nice to have the Debian stuff up-to-date, since many distros/projects 
are based on it.

73, KD0KZE / Paul

> On May 25, 2018 at 4:42 AM F6BHK  wrote:
>
>
> Hi there,
>
> I successfully built wsjt-x on Debian Stretch yesterday. The existing INSTALL 
> file is not up-to-date. You guys might be interested by the steps I had to go 
> through in order to build wsjt-x.
>
> Starting from a fresh Stretch install (Debian 9.4): (apt-get update + upgrade 
> + dist-upgrade Stretch)
>
> I could not find build-essentials in the repo (I seem to remember that name 
> but that was a very long time ago), so I had to:
> apt-get install gcc g++ fortran cmake (lowercase; CMake does not exist) 
> texinfo libtool automake (autoreconf is not a package)
> apt-get install git subversion (svn is not a package) asciidoc asciidocto 
> pkg-config
> apt-get install qt5.7 qt5libmultimedia-dev qt5widgets qt5base5-dev 
> qtmultimedia5-dev libqtseriqlport5 lib5qt5serialport5-dev
> apt-get libudev-dev libusb-1.0-0-dev fftw3-3-dev libfftw3-dev
>
> default versions of gcc/g++ is gcc6.
>
> When you local repo is updated, then (as detailed in the INSTALL)
> get source: wget —no-ckeck-certificates 
> https://physics/wsjtx-1.9.0-rc4.tgz and untar in your 
> build: cmake —build 
> install cmake —build  —target install
>
> et hop !
>
> done (it took a night to a "VIA Epia" cell with 1Gb mem and 500Gb disk to 
> complete)
>
> There is a big load of warnings when compiling the fortran source files but I 
> saw something about that on the reflector some days ago.
>
> Cheers
> Serge
>
>
> --
> Check out the vibrant tech community on one of the world's most
> engaging tech sites, Slashdot.org! http://sdm.link/slashdot
> ___
> wsjt-devel mailing list
> wsjt-devel@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/wsjt-devel
--
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot___
wsjt-devel mailing list
wsjt-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wsjt-devel

Re: [wsjt-devel] JTSDK Win32 and Nix Upgrade Available

[Paul Bramscher]

Hi Greg--

Thanks for the update, it compiled fine on my Debian 9.4 PC -- and it built 
WSJT-X rc4 8702 without trouble.

On SourceForge it was a simple matter to visually inspect which tar/gz was the 
most current version and to download it. What's the best way to visually 
inspect the most recently tagged/version on github?

e.g. click 'Clone or Download' and then 'Download Zip'? I see in your docs that 
you have a link here: https://github.com/KI7MT/jtsdk-nix/tree/jtsdk-nix-2.0.25

Just wondering if there's a handy visual cue somewhere that I might check every 
so often to see whether you've made a new release. Since I'm not an active 
contributor on it, I don't benefit much from a command-line git checkout -- 
downloading a single zip/tar is fine for my purposes.

Thanks again,
73, KD0KZE / Paul

> On May 25, 2018 at 3:59 AM Greg Beam  wrote:
>
>
> Hello All,
>
> Just a quick follow up.
>
> I pushed JTSDK-Nix v2.0.25 to Gitbub. Tested builds on WSL (18.04), VM
> (16.04 | 18.04), Native (14.04) for wsjtx-1.9.0-rc4. All passed.
>
> Attached is a couple of screen-shots from the Windows Subsystem Linux (WSL -
> Ubuntu 18.04) build. Using Xming, one could probably run WSJT-X from the WSL
> instance for testing. I'm not sure about the interoperability layer for
> com-devices, but, the UI should at least fire up.
>
> 73's
> Greg, KI7MT
>
> -Original Message-
> From: Greg Beam [mailto:ki7m...@gmail.com]
> Sent: Thursday, May 24, 2018 11:02 PM
> To: 'WSJT software development' 
> Subject: RE: [wsjt-devel] JTSDK Win32 and Nix Upgrade Available
>
> Hi Paul, Bill,
>
> I didn't re-work any of the WSJT-X build scripts, so obviously the URL's
> would be wrong. As I understand it:
>
> ^wsjt/wsjt/branches/wsjtx => is still the current dev branch "I think "
> ^/wsjtx/branches/x.y.z => are historical dev branches =< 1.8 and Joe's test
> branches ^/wsjtx/tags => contain all the previous tagged branches
>
> So rc5, or whatever the future tag will be called, is living in
> ^/branches/wsjtx at present.
>
> I'm not sure I want to restructure several scripts to accommodate a
> temporary location for the current WSJT-X development branch. Fixing
> ^/wsjtx/branches and ^/wsjtx/tags is just a matter of changing two URL's in
> one script; that's already done, I just need to tag it and push it to the
> Github repo. As a result, 2/3 (for an easy description) of the WSJT-X code
> has been migrated to the new structure (^/wsjtx/branches and ^/wsjtx/tags),
> and the remaining 1/3 (for lack of a better designation) is left as was in
> ^/branches/wsjtx.
>
> I've updated the docs on SF and for Github. When the push to Github happens
> (2.0.25), that should help clear up the previous version confusion. I built
> wsjtx-1.9.0-rc4 without any trouble on my local machine. I think that is
> working as expected after the URL change for ^/wsjtx/tags.
>
> 73's
> Greg, KI7MT
>
> On 24/05/2018 13:32, Paul Bramscher wrote:
> > Thanks for the links -- I've got 2.0.24 installed using that source
> > zip, but it reports this if I try to build rc candidate
> > wsjtx-1.9.0-rc4 (and a few others that I tried):
> >
> > The following build will be run:
> >
> > * Branch ..: ^/tags
> > * Name : wsjtx-1.9.0-rc4
> > * Type : Release
> > * Target ..: install
> >
> >
> > -
> > SVN UPDATE
> > -
> >
> > Checking Out New Version of wsjtx-1.9.0-rc4
> > svn: E17: URL
> > 'https://svn.code.sf.net/p/wsjt/wsjt/tags/wsjtx-1.9.0-rc4' doesn't
> > exist
> >
> > Thanks,
> > 73, KD0KZE / Paul
>
> Hi Paul,
>
> that URL is wrong, it should be
> 'https://svn.code.sf.net/p/wsjt/wsjt/wsjtx/tags/wsjtx-1.9.0-rc4'.
>
> 73
> Bill
> G4WJS.
>
>
> 
> --
> Check out the vibrant tech community on one of the world's most engaging
> tech sites, Slashdot.org! http://sdm.link/slashdot
> ___
> wsjt-devel mailing list
> wsjt-devel@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/wsjt-devel
>
> --
> Check out the vibrant tech community on one of the world's most
> engaging tech sites, Slashdot.org! 
> http://sdm.link/slashdot___
> wsjt-devel mailing list
> wsjt-devel@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/wsjt-devel
--
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot___
wsjt-devel mailing list
wsjt-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wsjt-devel

Re: [wsjt-devel] JTSDK Win32 and Nix Upgrade Available

[Paul Bramscher]

Hi Greg,

Thanks for the links -- I've got 2.0.24 installed using that source zip, but it 
reports this if I try to build rc candidate wsjtx-1.9.0-rc4 (and a few others 
that I tried):

The following build will be run:

* Branch ..: ^/tags
* Name : wsjtx-1.9.0-rc4
* Type : Release
* Target ..: install


-
SVN UPDATE
-

Checking Out New Version of wsjtx-1.9.0-rc4
svn: E17: URL 'https://svn.code.sf.net/p/wsjt/wsjt/tags/wsjtx-1.9.0-rc4' 
doesn't exist

Thanks,
73, KD0KZE / Paul


> On May 23, 2018 at 11:23 PM Greg Beam  wrote:
> 
> 
> Hi Paul,
> 
>  
> 
> Source Code - Github : 
> https://github.com/KI7MT/jtsdk-nix/archive/jtsdk-nix-2.0.24.zip
> 
>  
> 
> Prebuilt Packages - Launchpad: 
> https://launchpad.net/~ki7mt/+archive/ubuntu/jtsdk
> 
>  
> 
> I don’t follow Debian much anymore, so I’ve no idea which versions of 
> Ubuntu correlate with Debian. And yes, the docs need some attention for sure.
> 
>  
> 
> 73’s
> 
> Greg, KI7MT
> 
>  
> 
> From: Paul Bramscher [mailto:pfb...@comcast.net]
> Sent: Wednesday, May 23, 2018 8:30 PM
> To: Greg Beam ki7m...@gmail.com mailto:ki7m...@gmail.com
> 
> ; wsjtgr...@yahoogroups.com; WSJT software development 
> 
> Subject: Re: [wsjt-devel] JTSDK Win32 and Nix Upgrade Available
> 
>  
> 
> Greetings--
> 
>  
> 
> I'm running Debian 9.x and the most recent version of JTSDK on 
> SourceForge (2.0.22) that I see.  I get this error when launching it now:
> 
>  
> 
> svn: warning: W160013: URL 'http://svn.code.sf.net/p/wsjt/wsjt/tags' 
> http://svn.code.sf.net/p/wsjt/wsjt/tags%27 non-existent in revision 8722
> svn: E29: Could not list all targets because some targets don't exist
> 
>  
> 
> The docs on the github site suggest this first:
> 
> "Download jtsdk-nix-2.0.21.tar.gz" (Then extract, build, etc.).  This has 
> been the method I've used all along, I prefer not to add a PPA.  Is there a 
> 2.0.23 or somesuch available yet on the SourceForge site that contains these 
> changes?
> 
>  
> 
> 73, KD0KZE / Paul
> 
> > > 
> > On May 23, 2018 at 8:35 PM Greg Beam  > mailto:ki7m...@gmail.com > wrote:
> > 
> > Hello All,
> > 
> >  
> > 
> > The WSJT application layout was restructured today, and now lives 
> > in ^/wsjt/{trunk, branches, tags}. I have updated both JTSDK-Win32 and 
> > JTSDK-Nix to accommodate the new layout. When the WSJT-X is relocated (no 
> > target date for that move yet), that will trigger another round of updates.
> > 
> >  
> > 
> > JTSDK-Win32 Upgrade (to => v2.0.6 Release 718):
> > 
> > * Open JTSDK-Maint
> > * Update
> > * Upgrade
> > * That should be all that is needed.
> > * Check out and build commands have not changed
> > 
> >  
> > 
> > JTSDK-Nix Upgrade (to => 2.0.24-1):
> > 
> > * I’ve pushed the updates to my JTSDK PPA on Launchpad
> > * sudo apt-get update && sudo apt-get upgrade
> > * That should bring you up to date.
> > * Source Code Available @ git://github.com/KI7MT/jtsdk-nix.git
> > 
> >  
> > 
> > If you run into problems with either platform, please report them 
> > to jt...@groups.io mailto:jt...@groups.io
> > 
> >  
> > 
> > 73’s
> > 
> > Greg, KI7MT
> > 
> > > 
> 
>  
> 
> > > 
> > 
> > --
> > Check out the vibrant tech community on one of the world's most
> > engaging tech sites, Slashdot.org! 
> > http://sdm.link/slashdot___
> > wsjt-devel mailing list
> > wsjt-devel@lists.sourceforge.net 
> > mailto:wsjt-devel@lists.sourceforge.net
> > https://lists.sourceforge.net/lists/listinfo/wsjt-devel
> > 
> > > 
 
--
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot___
wsjt-devel mailing list
wsjt-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wsjt-devel

Re: [wsjt-devel] JTSDK Win32 and Nix Upgrade Available

[Paul Bramscher]

Greetings--


I'm running Debian 9.x and the most recent version of JTSDK on SourceForge 
(2.0.22) that I see.  I get this error when launching it now:


svn: warning: W160013: URL 'http://svn.code.sf.net/p/wsjt/wsjt/tags' 
http://svn.code.sf.net/p/wsjt/wsjt/tags%27 non-existent in revision 8722
svn: E29: Could not list all targets because some targets don't exist


The docs on the github site suggest this first:

"Download jtsdk-nix-2.0.21.tar.gz" (Then extract, build, etc.).  This has been 
the method I've used all along, I prefer not to add a PPA.  Is there a 2.0.23 
or somesuch available yet on the SourceForge site that contains these changes?


73, KD0KZE / Paul

> On May 23, 2018 at 8:35 PM Greg Beam  wrote:
> 
> 
> Hello All,
> 
>  
> 
> The WSJT application layout was restructured today, and now lives in 
> ^/wsjt/{trunk, branches, tags}. I have updated both JTSDK-Win32 and JTSDK-Nix 
> to accommodate the new layout. When the WSJT-X is relocated (no target date 
> for that move yet), that will trigger another round of updates.
> 
>  
> 
> JTSDK-Win32 Upgrade (to => v2.0.6 Release 718):
> 
> * Open JTSDK-Maint
> * Update
> * Upgrade
> * That should be all that is needed.
> * Check out and build commands have not changed
> 
>  
> 
> JTSDK-Nix Upgrade (to => 2.0.24-1):
> 
> * I’ve pushed the updates to my JTSDK PPA on Launchpad
> * sudo apt-get update && sudo apt-get upgrade
> * That should bring you up to date.
> * Source Code Available @ git://github.com/KI7MT/jtsdk-nix.git
> 
>  
> 
> If you run into problems with either platform, please report them to 
> jt...@groups.io
> 
>  
> 
> 73’s
> 
> Greg, KI7MT
> 


 


Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! 
http://sdm.link/slashdot___
wsjt-devel mailing list
wsjt-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wsjt-devel

--
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot___
wsjt-devel mailing list
wsjt-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wsjt-devel

[wsjt-devel] wsjt-x connectivity with Kenwood TM-V71 + RC-D710

[Paul Bramscher]

Greetings--

I'm trying to get wjjt-x working on an old Windows XP box and my Kenwood
TM-V71 (+ RC-D710 upgrade) and having some issues.  On the Windows PC, I
have a USB-to-serial cable with the Prolific driver, and I know it
works, since I successfully run APRSISCE/32.

The RC-D710 purportedly gives all the same functionality as the TM-D710,
but I'm wondering whether there might be a subtle data port difference.
 On my rig, there's a data port on the back of the TM-V71, and another
on the back of the D710 control head.

What I've found is that the Kenwood memory programming software only
works if I use the data port on the back of the TM-V71.  But APRSISCE/32
works if I use the data port on the back of the D710 control head.

Now for WSJT-X -- I basically get no response if I use the data port on
the back of the control head.  But if I use the data port on the back of
the TM-V71 base unit, WSJT-X (when testing) can trigger the TX of the
radio, but doesn't appear to do anything else.

Is there a special driver needed for the RC-D710 port setup?  A bug in
the software?  Or should I be thinking about upgrading to the TM-D710?

Or perhaps I've set up something wrong -- should the rig be in Packet
mode or not?

73, KD0KZE
Paul Bramscher

--
Meet PCI DSS 3.0 Compliance Requirements with EventLog Analyzer
Achieve PCI DSS 3.0 Compliant Status with Out-of-the-box PCI DSS Reports
Are you Audit-Ready for PCI DSS 3.0 Compliance? Download White paper
Comply to PCI DSS 3.0 Requirement 10 and 11.5 with EventLog Analyzer
http://pubads.g.doubleclick.net/gampad/clk?id=154622311&iu=/4140/ostg.clktrk
___
wsjt-devel mailing list
wsjt-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wsjt-devel