Il 06/09/20 11:44, Black Michael ha scritto: > Rename your hamlib source directory. > > The do the git clone over the same name...let's say your directory is > called "src". > mv src src.old > git clone https://github.com/Hamlib/Hamlib.git src > cd src > ./bootstrap > > Then you should be able to build as usual. > > Mike W9MDB > > > > > On Sunday, September 6, 2020, 09:38:42 AM CDT, Marco Calistri > <[email protected]> wrote: > > > Il 06/09/20 11:20, Black Michael ha scritto: >> 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] <mailto:[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 <mailto:marco@linux-turion64> >> <mailto:marco@linux-turion64 > <mailto: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 <mailto:marco@linux-turion64> >> <mailto:marco@linux-turion64 > <mailto: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 <mailto:marco@linux-turion64> >> <mailto:marco@linux-turion64 > <mailto: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) > Mike, > > The Hamlib source I use is getting downloaded by the WSJT-X itself > whenever I start the code compiling: > > /usr/bin/cmake -Dhamlib_INCLUDE_DIRS=/usr/include... > > Is there a way I can force the compiling to use a different Hamlib source? > > And another important detail I have to highlight is that such warnings I > posted are coming out from Linux journal at console window and not fromctory > WSJT-X: > > sudo journalctl -l -p err -S -f > > > -- > > 73 de Marco, PY1ZRJ (former IK5BCU)
Nothing to do Mike, same error! wsjtx[3852]: Hamlib: rig_set_ptt: PTT RTS set 06 12:54:08 wsjtx[3852]: Hamlib: rig_set_ptt: PTT RTS debug#1 set 06 12:54:08 wsjtx[3852]: Hamlib: rig_set_ptt: PTT RTS debug#2 There's something wrong in my build directory. wsjtx-2.2.2/src totale 22900 -rw-r--r-- 1 marco users 2185086 21 giu 20.52 hamlib-4.0~git.tar.gz -rw-r--r-- 1 marco users 72 21 giu 20.53 hamlib-4.0~git.tar.gz.md5sum -rw-r--r-- 1 marco users 21252512 21 giu 20.53 wsjtx.tgz -rw-r--r-- 1 marco users 60 21 giu 20.53 wsjtx.tgz.md5sum My compiling procedure starts from this first command, then it goes until the final binary and libs tar -xzvf /home/marco/Scaricati/wsjtx-2.2.2.tgz -C /home/marco/WSJT-X_build/build/ cd /home/marco/WSJT-X_build/build/wsjtx-2.2.2/ -- 73 de Marco, PY1ZRJ (former IK5BCU) _______________________________________________ wsjt-devel mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/wsjt-devel
