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 with the same crash error, that
said.. WSJTX will run forever if I manually enter the Callsign and tell
it to generate standard messages, it works just not very convenient,
seems to be a similar issue as Alex mentioned earlier just initiating
from a different file, maybe upgrading to 13 will help, but seems like
if it built fine it "should" run fine but who knows..
Thanks
Jason
On 1/7/22 15:21, Jeff Stillinger via wsjt-devel wrote:
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 all the software building these days. Otherwise,
leave a production machine alone.
You will see warnings as WSJT-X compiles with several declared but
unused variables. This is true on all platforms. Joe assures us that
many of these warnings will be cleaned up soon. The warnings do not
effect the operation of WSJT-X or the build.
If you make the jump to 13. Install: GCC-10_4, QT5, Ruby and Gems
prior to starting your build. This will save time, dependencies will
be built from source if not installed. For example, if gcc is not
installed, it will be built from source. Which takes most of the day.
Yes, I found out from the school of hard knocks... :-) The other
minor dependencies like pulseaudio build quickly enough to not worry
about.
If your build on 12 falls over, please document it. I can forward it
upstream to the FreeBSD team to fix a broken port.
On 1/7/22 09:13, Jason Selwitz via wsjt-devel wrote:
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, Jeff Stillinger via wsjt-devel wrote:
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/22 16:22, Jason Selwitz via wsjt-devel wrote:
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 work around but so far no luck. if anyone has any
tip, suggestions, etc it would be much appreciated, if this is not
the right place I can always try to follow up with the FreeBSD
porters team.
Fortran runtime error: Actual string length is shorter than the
declared one for dummy argument 'msgsent' (-4294967274/22)
Thanks, again!
Jason
_______________________________________________
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 mailing list
wsjt-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wsjt-devel
