You're not using the most recent source.
https://github.com/Hamlib/Hamlib
And no...you don't change the debug level during compiling. It's a run-time
setting and I do believe WSJT-X shows WARN and higher so that's why you see it
right now and that has been fixed now.
Mike W9MDB
On Sunday, September 6, 2020, 09:15:21 AM CDT, Marco Calistri
<[email protected]> wrote:
Il 06/09/20 00:14, Black Michael ha scritto:
> find . -name "*.c" -exec grep "PTT RTS" {} \; -print
> rig_debug(RIG_DEBUG_TRACE, "%s: PTT RTS debug#1\n", __func__);
> ./src/rig.c
Hi Mike,
This is what I get, there is a syntax error in the code near
RIG_DEBUG_TRACE. It sounds strange since I'm using standard WSJT-X source:
marco@linux-turion64:~/WSJT-X_build/build/wsjtx-2.2.2> find . -name
"*.c" -exec grep "PTT RTS" {} \; -print
rig_debug(RIG_DEBUG_ERR, "%s: PTT RTS\n", __func__);
rig_debug(RIG_DEBUG_ERR, "%s: PTT RTS debug#1\n", __func__);
rig_debug(RIG_DEBUG_ERR, "%s: PTT RTS debug#2\n", __func__);
./hamlib-prefix/src/hamlib/src/rig.c
marco@linux-turion64:~/WSJT-X_build/build/wsjtx-2.2.2>
rig_debug(RIG_DEBUG_TRACE, "%s: PTT RTS debug#1\n", __func__);
bash: errore di sintassi vicino al token non atteso "RIG_DEBUG_TRACE,"
marco@linux-turion64:~/WSJT-X_build/build/wsjtx-2.2.2> ./src/rig.c
Us there a way to set log level during compilation of the code?
Thanks!
--
73 de Marco, PY1ZRJ (former IK5BCU)
_______________________________________________
wsjt-devel mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/wsjt-devel
