Forgot to mention this did the trick, but did it make it into wsjtx?
Thanks,
Richard
___
wsjt-devel mailing list
wsjt-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wsjt-devel
Add this line before that
parameter (NFFT=32768)
Seems to be missing from that file and I can't figure out how it even compiles
without NFFT being defined.
Mike W9MDB
On Thursday, May 30, 2024 at 07:59:20 PM CDT, Richard Shaw via wsjt-devel
wrote:
Doing some test builds of curr
Doing some test builds of current RC4 and seeing build failures:
/builddir/build/BUILD/wsjtx-2.7.0/wsjtx/qmap/libqmap/decode0.f90:6:28:
6 | real*4 dd(2,NSMAX),ss(400,NFFT),savg(NFFT)
|1
Error: Variable ‘nfft’ cannot appear in the expression at (1)
/build
I just wanted to give you guys a heads up that wsjtx will fail to compile
with gcc 10 due to a fortran issue.
Details here:
https://lists.fedoraproject.org/archives/list/de...@lists.fedoraproject.org/thread/GVGNKHJFMEZVEOQVTUSDYPEELJUULLTL/
Thanks,
Richard
KF5OIM
___
Bill & Joe,
Thanks for the assistance and the great software!
73!
Scott D. Hernalsteen/W8CQD
FCC Licensed Amateur Radio Operator
(Amateur Extra Class)
www.w8cqd.com
"To preserve liberty it is essential that the whole body of the people always
posses
Scott --
You're running test code. To do it from the standard location you will
need to comment out lines 150-153 in routine jt65a.f90:
write(79,3001) nutc,nint(sync1),nsnr,dtx-1.0,nfreq,ncandidates,&
nhard_min,ntotal_min,ntry,naggressive,nft,nqual,decoded
3001 format(i4.4,i3,i4,f
On 17/12/2015 20:02, Scott Hernalsteen wrote:
> The previous error I reported does appear to be fixed, however, I’m
> getting a new one in r6289.
>
Hi Scott,
unfortunately you are going to get that error due to some test code. All
I can suggest is to comment out some lines in .../lib/jt65a.f90.
Hi all,
The previous error I reported does appear to be fixed, however, I’m getting a
new one in r6289.
As before, this occurs on the first successful decode cycle - to be more
specific, on the first successful JT65 decode cycle.
I have run repair disk permissions on both drives in my system,
Ahhh...my world make sense again. I had looked at the diff and missed that
in my quick look.
RRR
Mike W9MDB
On Thu, Dec 17, 2015 at 8:45 AM, Joe Taylor wrote:
> Hi Mike,
>
> No, revision 6286 did not modify jt65.f90. A change was made in
> decoder.f90 to correct the arguments to jt65a() the se
Hi Mike,
No, revision 6286 did not modify jt65.f90. A change was made in
decoder.f90 to correct the arguments to jt65a() the second time it is
called.
-- Joe
On 12/17/2015 9:28 AM, Michael Black wrote:
> Yes...6286 patched jt65.f90 -- am I wrong that that file is NOT used for
>
On 17/12/2015 14:40, Michael Black wrote:
> I'm using JTSDK on Windows. I've been attaching to wsjtx with
> QTCreator and walking through code. Looks to me like it's building
> correctly.
Hi Mike,
it may be a Windows issue. I will check it out later. It certainly works
on Linux and Mac.
73
B
I'm using JTSDK on Windows. I've been attaching to wsjtx with QTCreator
and walking through code. Looks to me like it's building correctly.
RRR
Mike W9MDB
On Thu, Dec 17, 2015 at 8:31 AM, Bill Somerville
wrote:
> On 17/12/2015 14:28, Michael Black wrote:
> > I'm running the debug version now b
On 17/12/2015 14:28, Michael Black wrote:
> I'm running the debug version now but still not getting line #'s on
> the error messages. I used the other FORTRAN runtime error report to
> find the call mismatch.
Hi Mike,
did you make a new build tree? You cannot change the Release/Debug
configura
Yes...6286 patched jt65.f90 -- am I wrong that that file is NOT used for
WSJT-X but just for a standlone test program? If so, how would it fix
WSJT-X?
I'm running the debug version now but still not getting line #'s on the
error messages. I used the other FORTRAN runtime error report to find the
What was "just for testing"? What error seems random???
The error you reported yesterday was fixed with r6286.
-- Joe
On 12/17/2015 8:29 AM, Michael Black wrote:
> You know I thought it looked like that was just for testingso it really
> shouldn't have any bearing on the error we've
On 17/12/2015 13:29, Michael Black wrote:
> so it really shouldn't have any bearing on the error we've been
> seeing, right?
> The error seems random.
There are a couple of yet to be resolved issues with the new decoder
parameters. I will check in some more changes soon when I have finished
tes
You know I thought it looked like that was just for testingso it really
shouldn't have any bearing on the error we've been seeing, right?
The error seems random.
73
Mike W9MDB
On Thu, Dec 17, 2015 at 4:44 AM, Bill Somerville
wrote:
> On 17/12/2015 05:27, Michael Black wrote:
> > jt65.f90 ha
Compiled ok and running without any immediate apparent issues.
73, Edson PY2SDR
---
- We humans have the capability to do amazing things if we work together.
- Nós seres humanos temos a capacidade de fazer coisas incríveis se
trabalharmos juntos.
On Thu, Dec 17, 2015 at 8:44 AM, Bill Somerville
On 17/12/2015 05:27, Michael Black wrote:
> jt65.f90 has the wrong# of arguments to jt65a
> It's missing mycall, hiscall, hisgrid
>
> So I think the attached patch fixes it.
Hi Mike & Scott,
Joe fixed the issues earlier for the main application. I have just
committed a change for the standalone j
jt65.f90 has the wrong# of arguments to jt65a
It's missing mycall, hiscall, hisgrid
So I think the attached patch fixes it.
73
Mike W9MDB
On Wed, Dec 16, 2015 at 5:58 PM, Scott Hernalsteen wrote:
> Hi all,
>
> I’m getting the attached error on the first successful decode cycle after
> starting
Hi all,
I’m getting the attached error on the first successful decode cycle after
starting the program. Dismissing the error dialog leaves the “DECODE” button
illuminated, however, no decoding is ever done.
I have a wave file from one of the time periods, however, the wav file
processes succe
Hi all,
I’m getting the attached error on the first successful decode cycle after
starting the program. Dismissing the error dialog leaves the “DECODE” button
illuminated, however, no decoding is ever done.
I have a wave file from one of the time periods, however, the wav file
processes succe
This morning I did a debug build of R6033, ran it for 25 minutes with no
errors, lots of decodes (some from Europe with a -24 & -25), and made
one QSO in the US. Built an rinstall version, and currently running it
with no problems, regularly seeing -26 decodes on JT9.
The Fortran error may ha
A few weeks ago I mentioned a Fortran error box that popped up when
running v.1.6.1.
The error's still occurring on the last build I did on Wednesday. I
haven't tried building anything new, as I had a death in the family, and
had to head to New Jersey. I'll try again tomorrow and build a dbug
24 matches
Mail list logo
