You must have old source code in your system somewhere and it's picking up and
old yaesu.h file.
That is defined in ft9000.c
Hamlib/rigs/yaesu# grep ft9000Old_caps *.c *.hft9000.c:struct rig_caps
ft9000Old_caps =yaesu.c: rig_register(&ft9000Old_caps);yaesu.h:extern struct
rig_caps ft9000Old_caps;
Mike W9MDB
On Wednesday, January 24, 2024 at 05:13:00 PM CST, Greg Cook via wsjt-devel
<[email protected]> wrote:
Different cmake error but still problems on Pi3. No problems with 2.6.1
Greg g4cui
Making all in tests
libtool: link: gcc -Wall -g -O2 -fPIC -fdata-sections -ffunction-sections
-Wl,--gc-sections -o rigctl rigctl-rigctl.o rigctl-rigctl_parse.o
rigctl-dumpcaps.o rigctl-dumpstate.o rigctl-rig_tests.o
../src/.libs/libhamlib.a -lusb-1.0 ../lib/.libs/libmisc.a -ldl -lm -pthread
../src/.libs/libhamlib.a(yaesu.o): In function `initrigs4_yaesu':
/home/pi/Downloads/hamlib-prefix/src/hamlib/rigs/yaesu/yaesu.c:127: undefined
reference to `ft9000Old_caps'
collect2: error: ld returned 1 exit status
Makefile:1118: recipe for target 'rigctl' failed
make[4]: *** [rigctl] Error 1
Makefile:632: recipe for target 'all-recursive' failed
make[3]: *** [all-recursive] Error 1
CMakeFiles/hamlib-install.dir/build.make:65: recipe for target
'hamlib-prefix/src/hamlib-stamp/hamlib-build' failed
make[2]: *** [hamlib-prefix/src/hamlib-stamp/hamlib-build] Error 2
CMakeFiles/Makefile2:195: recipe for target 'CMakeFiles/hamlib-install.dir/all'
failed
make[1]: *** [CMakeFiles/hamlib-install.dir/all] Error 2
Makefile:83: recipe for target 'all' failed
make: *** [all] Error 2
From: [email protected]
Sent: 24 January 2024 16:46
To: [email protected]
Subject: wsjt-devel Digest, Vol 119, Issue 42
Send wsjt-devel mailing list submissions to
[email protected]
To subscribe or unsubscribe via the World Wide Web, visit
https://lists.sourceforge.net/lists/listinfo/wsjt-devel
or, via email, send a message with subject or body 'help' to
[email protected]
You can reach the person managing the list at
[email protected]
When replying, please edit your Subject line so it is more specific
than "Re: Contents of wsjt-devel digest..."
Today's Topics:
1. Re: Making F/H idiot proof (Reino Talarmo)
2. Re: Making F/H idiot proof (Jeff Stillinger)
----------------------------------------------------------------------
Message: 1
Date: Wed, 24 Jan 2024 18:13:10 +0200
From: "Reino Talarmo" <[email protected]>
To: "'WSJT software development'" <[email protected]>
Subject: Re: [wsjt-devel] Making F/H idiot proof
Message-ID: <[email protected]>
Content-Type: text/plain; charset="utf-8"
Hi, I think that the Fox simply ignores the ?R+rpt? part of the message and
takes it to be a Tx1 message. So Fox sends a report. The Hound station autoseq
may not work correctly as it has not sent the Tx1 at all. A resending of the
?R+rpt? should be a correct message. The Hound station sends only Tx1 and Tx3
in the protocol. Fox should not response by RR73, if it has not sent a Tx2 and
received after that a R+rpt. No short-cuts allowed.
Well, it is another issue how to get operators to read user guides!
73, Reino OH3mA
From: Andy Durbin via wsjt-devel [mailto:[email protected]]
Sent: Wednesday, January 24, 2024 5:48 PM
To: Brian Moran <[email protected]>; WSJT software development
<[email protected]>
Cc: Andy Durbin <[email protected]>
Subject: Re: [wsjt-devel] Making F/H idiot proof
Hi Brian,
The screen shot and the discussion are in the Clipperton groups.io messages.
Clipperton is certainly using WSJT-X and operating as Fox. It appears the
"user" saw a TX5S CQ and replied with TX3. TX5S responded with TX2.
ref - https://groups.io/g/Clipperton-2024/message/388
You may need to sign up for the group to read messages. Private email if you
like me to send a copy of the screen shot. I don't think this "list" will
allow images.
73,
Andy, k3wyc
_____
From: Brian Moran <[email protected] <mailto:[email protected]> >
Sent: Wednesday, January 24, 2024 8:36 AM
To: WSJT software development <[email protected]
<mailto:[email protected]> >
Cc: Andy Durbin <[email protected] <mailto:[email protected]> >
Subject: Re: [wsjt-devel] Making F/H idiot proof
Hi Andy; can you please help me understand the circumstances better?
Under ?normal? f/h operation, the hound calls with a grid. WSJT-X in fox mode
can queue a caller with a grid. WSJT-X in fox mode doesn?t queue
non-grid-supplying callers.
If the ?fox? replied to a signal report message as the first call, perhaps the
fox wasn?t using f/h mode? Perhaps not using wsjt-x?
The calling operator could have used the manual message selection buttons to
change their message to the ?fox? reflecting the circumstances, and they could
have manually logged the station at the appropriate point in the sequence. It
seems they might have partially done that, since if I understand what you are
writing, they found and started with the TX3 message.
If you could point me to more information and the screenshot, I?d like to
follow up to understand this situation better.
Thanks,
-Brian N9ADG
Sent via iPhone
On Jan 24, 2024, at 7:16?AM, Andy Durbin via wsjt-devel
<[email protected] <mailto:[email protected]> >
wrote:
?
As implemented in WSJT-X ver 2.6.1 the hound is able to select TX3 as their
first transmission. One user has posted a screen shot showing that fox replied
with a signal report but the QSO could not be completed.
Since new WSJT-X ops seem reluctant to read the instructions would the
developers please consider making TX3 unselectable until a signal report has
been received.
Thanks and 73,
Andy, k3wyc
_______________________________________________
wsjt-devel mailing list
[email protected] <mailto:[email protected]>
https://lists.sourceforge.net/lists/listinfo/wsjt-devel
-------------- next part --------------
An HTML attachment was scrubbed...
------------------------------
Message: 2
Date: Wed, 24 Jan 2024 10:30:36 -0600
From: Jeff Stillinger <[email protected]>
To: [email protected]
Subject: Re: [wsjt-devel] Making F/H idiot proof
Message-ID: <[email protected]>
Content-Type: text/plain; charset="utf-8"; Format="flowed"
Having read and seen much of the same.?? I agree that F/H needs some
work.??? Andy is spot on about the user base not reading and following
instructions.?? Therefore, we do need forced compliance with the message
format.?? Of course there will be a lot of whining about it, but the
Clipperton DXE is a total mess right now.? There are WSJT-X operators
that only use WSJT-X for F/H mode and DXEs.?? They are not aware of the
most current news, information, and operational changes as they don't
participate with the group email lists on a daily basis.? The software
needs to help them out.
Honestly, even with daily FT8 operations between all of the short cuts
people are taking with the message format, combined with heavy
filtering, has FT8 a total mess.?? It's a wonder people get QSLs for
awards it's so messy.
On 1/24/24 09:07, Andy Durbin via wsjt-devel wrote:
> As implemented in WSJT-X ver 2.6.1 the hound is able to select TX3 as
> their first transmission.? One user has posted a screen shot showing
> that fox replied with a signal report but the QSO could not be completed.
>
> Since new WSJT-X ops seem reluctant to read the instructions would the
> developers please consider making TX3 unselectable until a signal
> report has been received.
>
> Thanks and 73,
> Andy, k3wyc
>
>
> _______________________________________________
> wsjt-devel mailing list
> [email protected]
> https://lists.sourceforge.net/lists/listinfo/wsjt-devel
--
Jeff Stillinger - KB6IBB
KB6IBB Laboratories, Wylie Tx
r/KB6IBBSWLLogger
http://kb6ibb-15.ham-radio-op.net/
-------------- next part --------------
An HTML attachment was scrubbed...
------------------------------
------------------------------
Subject: Digest Footer
_______________________________________________
wsjt-devel mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/wsjt-devel
------------------------------
End of wsjt-devel Digest, Vol 119, Issue 42
*******************************************
_______________________________________________
wsjt-devel mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/wsjt-devel
_______________________________________________
wsjt-devel mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/wsjt-devel
