Awesome, thanks again for the tips Jeff,
I went ahead and de-installed WSJT-X updated my ports tree and rebuilt
it on my current 12 install, it does build fine and runs ok, even lets
me click on a few station calls to initiate contact then maybe the third
or fourth try I seem to always end up
One of the beautiful things about FreeBSD is building out of the ports
collection. Everything is built from source, so it should not matter if
you are on 11, 12 or 13. I would encourage an update to 13 if you have
a non-production machine, simply because that is where people seem to be
doing
Thanks Jeff.
I'm running 12.X currently but 2.5.4 seems to build fine for me at least
I could try to re-run the build and watch for any warnings or errors..
is it a matter of needing to jump to the 13.X version train? or should
it still work under 12.X?
Thanks again
Jason
On 1/7/22 09:50
That has been fixed and WSJT-X 2.5.4 builds out of the ports collection
on FreeBSD 13.
portsnap fetch update
make install clean
WSJT-X 2.5.4 builds and installs without error.
Oh, and thanks for the reminder to send Diane the request to add the
binary to the package collection.
On 1/6/2
Hi Jason,
I believe that the WSJT-X team said they were going to look at issues like this
as part of a larger clean-up to deal with ever-stricter fortran compilers.
You might need to wait until the next release for this to be fixed.
alex
K6LOT
> On Jan 6, 2022, at 5:16 PM, Jason Selwitz via wsj
OK so after jumping through hoops to get the FreeBSD ports system to
take a modified version of the WSJT-X source I was able to try to edit
the line..
character*22 msgsent
to..
character(len=*) :: msgsent
and tried to recompile, the program seems to have built fine but then
when you start i
Thanks Alex!
I tool a look at where it was failing and it appears to be coming from ..
/usr/ports/comms/wsjtx/work/.build/wsjtx-prefix/src/wsjtx/lib/gen65.f90
which looks like it contains the following..
Line 1: subroutine gen65(msg0,ichk,msgsent,itone,itype)
I did find something similar to w
Hi Jason,
I’ve seen this error with the Apple M1 port. It’s because the version of the
fortran compiler you are using is newer and treats this as an error instead of
a warning like the older fortran compiler. I’m not sure what the recommended
version is for WSJT-X but for Intel Macs it was 6.
Hi there,
I was wondering if anyone had seen the following error it usually
happens when I try to double click on another callsign to start
attempting to make a contact Ive tried removing and rebuilding the
configuration and tried changing a few settings in the software to try
to find a wor
