[wsjt-devel] WSJT-X 2.5.0-rc3 RST_RCVD logging issue

[jan0--- via wsjt-devel]

I had a 6m FT8 JA run using WSJT-X 2.5.0-rc3 today.  After the event, I
copied the wsjt_log.adi file and uploaded the copy to my logging program,
where I noticed a curious, deterministic pattern in the RST_RCVD column
[Capture.PNG attached].

 

These incorrect RST_RCVD values were also in the wsjt.log file:

 

2021-07-16,22:37:00,2021-07-16,22:38:30,JA1OVD,QM05,50.315630,FT8,-05,-12,,,
,

2021-07-16,22:38:45,2021-07-16,22:39:30,7K4DHB,,50.315630,FT8,-02,-12

2021-07-16,22:39:45,2021-07-16,22:40:30,JA0MVW,,50.315630,FT8,+01,-12

2021-07-16,22:40:45,2021-07-16,22:42:00,JR1BAS,,50.315630,FT8,-07,-12

2021-07-16,22:43:45,2021-07-16,22:45:00,JH1IIT,,50.315630,FT8,-08,-08

2021-07-16,22:45:15,2021-07-16,22:46:00,JA0DAI,,50.315630,FT8,-08,-08

2021-07-16,22:46:15,2021-07-16,22:47:00,JA7KPI,,50.315630,FT8,-05,-08

2021-07-16,22:47:15,2021-07-16,22:48:30,JH1PXH,,50.315630,FT8,-09,-08

2021-07-16,22:48:30,2021-07-16,22:50:30,JA9LJS,,50.315630,FT8,-08,-14

2021-07-16,22:50:45,2021-07-16,22:52:00,JI1RAK,,50.315630,FT8,-17,-14

2021-07-16,22:52:15,2021-07-16,22:53:00,JA9IPF,,50.315630,FT8,-08,-14

2021-07-16,22:53:15,2021-07-16,22:54:00,JF2WXS,,50.315630,FT8,-07,-14

2021-07-16,22:55:45,2021-07-16,22:56:00,JR7AIW,QM09,50.325630,FT8,-15,-12,,,
,

2021-07-16,22:56:15,2021-07-16,22:57:00,JA2CXH,,50.325630,FT8,-10,-12

2021-07-16,22:57:15,2021-07-16,22:58:00,JA5EXW,,50.325630,FT8,-17,-12

2021-07-16,22:58:15,2021-07-16,22:59:00,JH1TWT,,50.325630,FT8,-05,-12

2021-07-16,22:59:15,2021-07-16,23:00:00,JM1SZY,,50.325630,FT8,-01,-12

2021-07-16,23:00:15,2021-07-16,23:01:00,JI1FLB,,50.325630,FT8,-18,-12

2021-07-16,23:01:15,2021-07-16,23:02:00,JJ1VKF/P,,50.325630,FT8,-16,-12

2021-07-16,23:02:45,2021-07-16,23:03:30,JE7ETY,,50.325630,FT8,-08,-12

2021-07-16,23:03:45,2021-07-16,23:04:30,JL1OZI,,50.325630,FT8,-12,-12

2021-07-16,23:07:15,2021-07-16,23:08:00,JK1GKG,,50.315630,FT8,-11,-12

2021-07-16,23:08:15,2021-07-16,23:09:00,JK1SQI,,50.315630,FT8,-07,-12

2021-07-16,23:09:00,2021-07-16,23:11:30,JH1HRJ,,50.315630,FT8,-05,-17

2021-07-16,23:11:45,2021-07-16,23:12:30,JL1QOC,,50.315630,FT8,-15,-17

2021-07-16,23:13:15,2021-07-16,23:15:00,JO7WXN,,50.315630,FT8,-16,-17

2021-07-16,23:16:45,2021-07-16,23:17:30,JI1DMH,,50.315630,FT8,-12,-17

2021-07-16,23:17:45,2021-07-16,23:18:30,JH6ETS,,50.315630,FT8,-15,-17

2021-07-16,23:21:45,2021-07-16,23:22:30,JH4LRH,,50.315630,FT8,-02,-17

2021-07-16,23:25:45,2021-07-16,23:26:30,JA6WJL,,50.315617,FT8,-15,-17

2021-07-16,23:26:45,2021-07-16,23:27:30,JA6RJK,,50.315617,FT8,-11,-17

2021-07-16,23:29:45,2021-07-16,23:30:30,JE6HJT,,50.315617,FT8,-04,-17

2021-07-16,23:31:45,2021-07-16,23:32:30,JH4IUO,,50.315617,FT8,-08,-17

 

However, the values in the ALL.TXT file agree with the displayed values
decoded in real time - i.e., they are correct.  (I can, of course, send the
file if desired.)  

 

Also, and perhaps most strangely, QSOs before and after the JA run have the
correct RST_RCVD values logged.  

 

I could find no errors in the RST_SENT values before, during, or after the
JA run.

 

The radio is an IC-7610, feeding a Lenovo ThinkPad (i7-7500U CPU @ 2.70GHz,
2904 MHz, 2 Cores, 4 Logical Processors) running Windows 10 Pro version
10.0.19042 (x64).

 

Ed Callaway N4II.

 

 

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

Re: [wsjt-devel] WSJT-X and Omni-Rig: Failed to start Omni Rig COM server

[tom via wsjt-devel]

HiNo, I don't think I said this right.If you open omnirig while you monitor the 
serial port, the serial port opens, then there's a little activity and then the 
port closed. Omnirig remains open.Starting wsjt with omnirig open or closed 
produces the same result. Failed to start com server unless you run it as 
admin.TomSent from my Galaxy
 Original message From: Bill Somerville via wsjt-devel 
 Date: 2021-07-16  5:56 p.m.  (GMT-05:00) To: 
wsjt-devel@lists.sourceforge.net Cc: Bill Somerville  
Subject: Re: [wsjt-devel] WSJT-X and Omni-Rig: Failed to start Omni Rig COM 
server 
Hi Tom,


that's not how Omni-Rig behaves for me,
  if I start it manually the setup dialog stays open until it is
  cancelled or closed with the OK button. Starting WSJT-X to
  communicate with it doesn't change that. What version of Omni-Rig
  are you using?


73
  Bill
  G4WJS.


On 16/07/2021 22:49, Tom via wsjt-devel
  wrote:


  Hi
  Omni-rig
  connects just fine to the radio.  When you open it there is
  some initial comport activity then it closes.  All this is
  normal.
  It
  is completely reproducible on my system.  There is no issue
  with any other application that uses Omni-rig.
  On
  the groups.io list, there are people that have reported this
  in the past. 
  73
  Tom
   
   
  

  From: Bill Somerville via wsjt-devel
   
  Sent: Friday, July 16, 2021 4:03 PM
  To: wsjt-devel@lists.sourceforge.net
  Cc: Bill Somerville 
  Subject: Re: [wsjt-devel] WSJT-X and Omni-Rig:
  Failed to start Omni Rig COM server

  
   
  
Hi Tom,
  
  
 
  
  
OK, I've not see that behaviour. Are you
  able to reproduce it? If yes, then does starting Omni-Rig
  manually before starting WSJT-X work correctly?
  
  
 
  
  
73
  Bill
  G4WJS.
  
  
 
  
  
On 16/07/2021 20:59, tom via wsjt-devel
  wrote:
  
  

  Hi


  Actually no. When you start wsjt it
immediately gives an error saying failed to start omnirig
com server. If you monitor the serial port traffic, nothing
happens at all. No serial communications at all. 


  If you start wsjt as administrator it
works without an issue. This doesn't happen with any other
software that uses omnirig. It's strange because this always
worked in the past.


  73 Tom va2fsq


   


   


   


  
Sent from my Galaxy
  


   


   


  
 Original message 
  
  
From: Bill Somerville via wsjt-devel 

  
  
  
Date: 2021-07-16 3:36 p.m. (GMT-05:00)
  
  
  
To: wsjt-devel@lists.sourceforge.net
  
  
  
Cc: Bill Somerville 
  
  
  
Subject: Re: [wsjt-devel] WSJT-X and
  Omni-Rig: Failed to start Omni Rig COM server 
  
  
 
  

On 16/07/2021 20:10, Tom via wsjt-devel
  wrote:
  > I am the author of Win4IcomSuite and have started getting
  reports of WSJT
  > failing to start the Omni-rig COM server.  This does not
  happen on all
  > computers. In addition, it starts happening when no
  changes have been made
  > to Omni-rig and WSJT.  Installing the latest versions
  does not correct the
  > issue.
  > To reproduce:
  > Reboot your computer and make sure there are no other
  applications using
  > omni-rig.
  > Use Omni-rig definition for your Icom radio;. Start
  WSJT.  You receive the
  > above error.
  > Run WSJT as Administrator and it works.
  >
  > All other applications using Omni-rig work without
  putting them in
  > administrator mode.  No other related software is
  running.  This is with a
  > direct connection to the radio.
  >
  > Details, version 2.4.0 (happens on previous version as
  well).
  > Windows 10, version 19041.1083
  > 73 Tom va2fsq
  
  Tom,
  
  I am looking into this issue, you don't need to keep repeating
  your query.
  
  So 

Re: [wsjt-devel] WSJT-X and Omni-Rig: Failed to start Omni Rig COM server

[Bill Somerville via wsjt-devel]

Hi Tom,

that's not how Omni-Rig behaves for me, if I start it manually the setup 
dialog stays open until it is cancelled or closed with the OK button. 
Starting WSJT-X to communicate with it doesn't change that. What version 
of Omni-Rig are you using?


73
Bill
G4WJS.

On 16/07/2021 22:49, Tom via wsjt-devel wrote:


Hi

Omni-rig connects just fine to the radio.  When you open it there is 
some initial comport activity then it closes.  All this is normal.


It is completely reproducible on my system.  There is no issue with 
any other application that uses Omni-rig.


On the groups.io list, there are people that have reported this in the 
past.


73 Tom

*From:*Bill Somerville via wsjt-devel 
*Sent:* Friday, July 16, 2021 4:03 PM
*To:* wsjt-devel@lists.sourceforge.net
*Cc:* Bill Somerville 
*Subject:* Re: [wsjt-devel] WSJT-X and Omni-Rig: Failed to start Omni 
Rig COM server


Hi Tom,

OK, I've not see that behaviour. Are you able to reproduce it? If yes, 
then does starting Omni-Rig manually before starting WSJT-X work 
correctly?


73
Bill
G4WJS.

On 16/07/2021 20:59, tom via wsjt-devel wrote:

Hi

Actually no. When you start wsjt it immediately gives an error
saying failed to start omnirig com server. If you monitor the
serial port traffic, nothing happens at all. No serial
communications at all.

If you start wsjt as administrator it works without an issue. This
doesn't happen with any other software that uses omnirig. It's
strange because this always worked in the past.

73 Tom va2fsq

Sent from my Galaxy

 Original message 

From: Bill Somerville via wsjt-devel



Date: 2021-07-16 3:36 p.m. (GMT-05:00)

To: wsjt-devel@lists.sourceforge.net


Cc: Bill Somerville 


Subject: Re: [wsjt-devel] WSJT-X and Omni-Rig: Failed to start
Omni Rig COM server

On 16/07/2021 20:10, Tom via wsjt-devel wrote:
> I am the author of Win4IcomSuite and have started getting
reports of WSJT
> failing to start the Omni-rig COM server.  This does not happen
on all
> computers. In addition, it starts happening when no changes have
been made
> to Omni-rig and WSJT.  Installing the latest versions does not
correct the
> issue.
> To reproduce:
> Reboot your computer and make sure there are no other
applications using
> omni-rig.
> Use Omni-rig definition for your Icom radio;. Start WSJT.  You
receive the
> above error.
> Run WSJT as Administrator and it works.
>
> All other applications using Omni-rig work without putting them in
> administrator mode.  No other related software is running.  This
is with a
> direct connection to the radio.
>
> Details, version 2.4.0 (happens on previous version as well).
> Windows 10, version 19041.1083
> 73 Tom va2fsq

Tom,

I am looking into this issue, you don't need to keep repeating
your query.

So far I see one problem with startup when there is a fault condition
like the rig not being accessible, or if WSJT-X is closed down
before it
has completed all the retries it attempts before reporting an error
(that takes up to 10 seconds). Is that consistent with what you are
reporting? If so, then if WSJT-X is left for 20 seconds or so to
do its
own thing does an error get reported?

73
Bill
G4WJS.



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

Re: [wsjt-devel] WSJT-X and Omni-Rig: Failed to start Omni Rig COM server

[Tom via wsjt-devel]

Hi

Omni-rig connects just fine to the radio.  When you open it there is some 
initial comport activity then it closes.  All this is normal.

It is completely reproducible on my system.  There is no issue with any other 
application that uses Omni-rig.

On the groups.io list, there are people that have reported this in the past.

73 Tom





From: Bill Somerville via wsjt-devel 
Sent: Friday, July 16, 2021 4:03 PM
To: wsjt-devel@lists.sourceforge.net
Cc: Bill Somerville 
Subject: Re: [wsjt-devel] WSJT-X and Omni-Rig: Failed to start Omni Rig COM 
server



Hi Tom,



OK, I've not see that behaviour. Are you able to reproduce it? If yes, then 
does starting Omni-Rig manually before starting WSJT-X work correctly?



73
Bill
G4WJS.



On 16/07/2021 20:59, tom via wsjt-devel wrote:

Hi

Actually no. When you start wsjt it immediately gives an error saying failed to 
start omnirig com server. If you monitor the serial port traffic, nothing 
happens at all. No serial communications at all.

If you start wsjt as administrator it works without an issue. This doesn't 
happen with any other software that uses omnirig. It's strange because this 
always worked in the past.

73 Tom va2fsq







Sent from my Galaxy





 Original message 

From: Bill Somerville via wsjt-devel   


Date: 2021-07-16 3:36 p.m. (GMT-05:00)

To: wsjt-devel@lists.sourceforge.net 

Cc: Bill Somerville   

Subject: Re: [wsjt-devel] WSJT-X and Omni-Rig: Failed to start Omni Rig COM 
server



On 16/07/2021 20:10, Tom via wsjt-devel wrote:
> I am the author of Win4IcomSuite and have started getting reports of WSJT
> failing to start the Omni-rig COM server.  This does not happen on all
> computers. In addition, it starts happening when no changes have been made
> to Omni-rig and WSJT.  Installing the latest versions does not correct the
> issue.
> To reproduce:
> Reboot your computer and make sure there are no other applications using
> omni-rig.
> Use Omni-rig definition for your Icom radio;. Start WSJT.  You receive the
> above error.
> Run WSJT as Administrator and it works.
>
> All other applications using Omni-rig work without putting them in
> administrator mode.  No other related software is running.  This is with a
> direct connection to the radio.
>
> Details, version 2.4.0 (happens on previous version as well).
> Windows 10, version 19041.1083
> 73 Tom va2fsq

Tom,

I am looking into this issue, you don't need to keep repeating your query.

So far I see one problem with startup when there is a fault condition
like the rig not being accessible, or if WSJT-X is closed down before it
has completed all the retries it attempts before reporting an error
(that takes up to 10 seconds). Is that consistent with what you are
reporting? If so, then if WSJT-X is left for 20 seconds or so to do its
own thing does an error get reported?

73
Bill
G4WJS.





--
This email has been checked for viruses by Avast antivirus software.
https://www.avast.com/antivirus
___
wsjt-devel mailing list
wsjt-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wsjt-devel

Re: [wsjt-devel] WSJT-X and Omni-Rig: Failed to start Omni Rig COM server

[Bill Somerville via wsjt-devel]

Hi Tom,

OK, I've not see that behaviour. Are you able to reproduce it? If yes, 
then does starting Omni-Rig manually before starting WSJT-X work correctly?


73
Bill
G4WJS.

On 16/07/2021 20:59, tom via wsjt-devel wrote:

Hi
Actually no. When you start wsjt it immediately gives an error saying 
failed to start omnirig com server. If you monitor the serial port 
traffic, nothing happens at all. No serial communications at all.
If you start wsjt as administrator it works without an issue. This 
doesn't happen with any other software that uses omnirig. It's strange 
because this always worked in the past.

73 Tom va2fsq



Sent from my Galaxy


 Original message 
From: Bill Somerville via wsjt-devel 
Date: 2021-07-16 3:36 p.m. (GMT-05:00)
To: wsjt-devel@lists.sourceforge.net
Cc: Bill Somerville 
Subject: Re: [wsjt-devel] WSJT-X and Omni-Rig: Failed to start Omni 
Rig COM server


On 16/07/2021 20:10, Tom via wsjt-devel wrote:
> I am the author of Win4IcomSuite and have started getting reports of 
WSJT

> failing to start the Omni-rig COM server.  This does not happen on all
> computers. In addition, it starts happening when no changes have 
been made
> to Omni-rig and WSJT.  Installing the latest versions does not 
correct the

> issue.
> To reproduce:
> Reboot your computer and make sure there are no other applications using
> omni-rig.
> Use Omni-rig definition for your Icom radio;. Start WSJT. You 
receive the

> above error.
> Run WSJT as Administrator and it works.
>
> All other applications using Omni-rig work without putting them in
> administrator mode.  No other related software is running. This is 
with a

> direct connection to the radio.
>
> Details, version 2.4.0 (happens on previous version as well).
> Windows 10, version 19041.1083
> 73 Tom va2fsq

Tom,

I am looking into this issue, you don't need to keep repeating your query.

So far I see one problem with startup when there is a fault condition
like the rig not being accessible, or if WSJT-X is closed down before it
has completed all the retries it attempts before reporting an error
(that takes up to 10 seconds). Is that consistent with what you are
reporting? If so, then if WSJT-X is left for 20 seconds or so to do its
own thing does an error get reported?

73
Bill
G4WJS.



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

Re: [wsjt-devel] WSJT-X and Omni-Rig: Failed to start Omni Rig COM server

[tom via wsjt-devel]

HiActually no. When you start wsjt it immediately gives an error saying failed 
to start omnirig com server. If you monitor the serial port traffic, nothing 
happens at all. No serial communications at all. If you start wsjt as 
administrator it works without an issue. This doesn't happen with any other 
software that uses omnirig. It's strange because this always worked in the 
past.73 Tom va2fsqSent from my Galaxy
 Original message From: Bill Somerville via wsjt-devel 
 Date: 2021-07-16  3:36 p.m.  (GMT-05:00) To: 
wsjt-devel@lists.sourceforge.net Cc: Bill Somerville  
Subject: Re: [wsjt-devel] WSJT-X and Omni-Rig: Failed to start Omni Rig COM 
server On 16/07/2021 20:10, Tom via wsjt-devel wrote:> I am the author of 
Win4IcomSuite and have started getting reports of WSJT> failing to start the 
Omni-rig COM server.  This does not happen on all> computers. In addition, it 
starts happening when no changes have been made> to Omni-rig and WSJT.  
Installing the latest versions does not correct the> issue.> To reproduce:> 
Reboot your computer and make sure there are no other applications using> 
omni-rig.> Use Omni-rig definition for your Icom radio;. Start WSJT.  You 
receive the> above error.> Run WSJT as Administrator and it works.>> All other 
applications using Omni-rig work without putting them in> administrator mode.  
No other related software is running.  This is with a> direct connection to the 
radio.>> Details, version 2.4.0 (happens on previous version as well).> Windows 
10, version 19041.1083> 73 Tom va2fsqTom,I am looking into this issue, you 
don't need to keep repeating your query.So far I see one problem with startup 
when there is a fault condition like the rig not being accessible, or if WSJT-X 
is closed down before it has completed all the retries it attempts before 
reporting an error (that takes up to 10 seconds). Is that consistent with what 
you are reporting? If so, then if WSJT-X is left for 20 seconds or so to do its 
own thing does an error get 
reported?73BillG4WJS.___wsjt-devel 
mailing 
listwsjt-devel@lists.sourceforge.nethttps://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 and Omni-Rig: Failed to start Omni Rig COM server

[Bill Somerville via wsjt-devel]

On 16/07/2021 20:10, Tom via wsjt-devel wrote:

I am the author of Win4IcomSuite and have started getting reports of WSJT
failing to start the Omni-rig COM server.  This does not happen on all
computers. In addition, it starts happening when no changes have been made
to Omni-rig and WSJT.  Installing the latest versions does not correct the
issue.
To reproduce:
Reboot your computer and make sure there are no other applications using
omni-rig.
Use Omni-rig definition for your Icom radio;. Start WSJT.  You receive the
above error.
Run WSJT as Administrator and it works.

All other applications using Omni-rig work without putting them in
administrator mode.  No other related software is running.  This is with a
direct connection to the radio.

Details, version 2.4.0 (happens on previous version as well).
Windows 10, version 19041.1083
73 Tom va2fsq


Tom,

I am looking into this issue, you don't need to keep repeating your query.

So far I see one problem with startup when there is a fault condition 
like the rig not being accessible, or if WSJT-X is closed down before it 
has completed all the retries it attempts before reporting an error 
(that takes up to 10 seconds). Is that consistent with what you are 
reporting? If so, then if WSJT-X is left for 20 seconds or so to do its 
own thing does an error get reported?


73
Bill
G4WJS.



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

[wsjt-devel] WSJT-X and Omni-Rig: Failed to start Omni Rig COM server

[Tom via wsjt-devel]

I am the author of Win4IcomSuite and have started getting reports of WSJT
failing to start the Omni-rig COM server.  This does not happen on all
computers. In addition, it starts happening when no changes have been made
to Omni-rig and WSJT.  Installing the latest versions does not correct the
issue.
To reproduce:
Reboot your computer and make sure there are no other applications using
omni-rig.
Use Omni-rig definition for your Icom radio;. Start WSJT.  You receive the
above error.
Run WSJT as Administrator and it works.

All other applications using Omni-rig work without putting them in
administrator mode.  No other related software is running.  This is with a
direct connection to the radio.

Details, version 2.4.0 (happens on previous version as well).
Windows 10, version 19041.1083
73 Tom va2fsq


-- 
This email has been checked for viruses by Avast antivirus software.
https://www.avast.com/antivirus



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

[wsjt-devel] WSJT-X and Omni-Rig: Failed to start Omni Rig COM server

[Tom via wsjt-devel]

I am the author of Win4IcomSuite and have started getting reports of WSJT
failing to start the Omni-rig COM server.  This does not happen on all
computers. In addition, it starts happening when no changes have been made
to Omni-rig and WSJT.  Installing the latest versions does not correct the
issue.
To reproduce:
Reboot your computer and make sure there are no other applications using
omni-rig.
Use Omni-rig definition for your Icom radio;. Start WSJT.  You receive the
above error.
Run WSJT as Administrator and it works.

All other applications using Omni-rig work without putting them in
administrator mode.

Details, version 2.4.0 (happens on previous version as well).
Windows 10, version 19041.1083
73 Tom va2fsq


-- 
This email has been checked for viruses by Avast antivirus software.
https://www.avast.com/antivirus



___
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

[Bill Somerville via wsjt-devel]

On 16/07/2021 17:08, 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) 


Hi Claude,

I'm not sure why you are getting that error. The libthread_db library is 
used by debuggers to access thread information so I am surprised it is 
being referenced. Is this a debug configuration build?


73
Bill
G4WJS.



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

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

[Claude Frantz via wsjt-devel]

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] My problems while compiling from the source

[Claude Frantz via wsjt-devel]

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