Hi Bill,
Had a problem with the cmake - one that had not happened when I built the
original executable here on the RPi.Please advise... :-)
[ 75%] Building CXX object CMakeFiles/wsjt_qt.dir/HamlibTransceiver.cpp.o
[ 75%] Building CXX object CMakeFiles/wsjt_qt.dir/HRDTransceiver.cpp.o
/home/pi/wsjtx-1.7.0/src/HamlibTransceiver.cpp: In member function ‘virtual int
HamlibTransceiver::do_start()’:
/home/pi/wsjtx-1.7.0/src/HamlibTransceiver.cpp:541:66: error:
‘RIG_PASSBAND_NOCHANGE’ was not declared in this scope
rig_set_mode (rig_.data (), RIG_VFO_CURR, dummy_mode_,
RIG_PASSBAND_NOCHANGE);
^
/home/pi/wsjtx-1.7.0/src/HamlibTransceiver.cpp: In member function ‘virtual
void HamlibTransceiver::do_frequency(Transceiver::Frequency, Transceiver::MODE,
bool)’:
/home/pi/wsjtx-1.7.0/src/HamlibTransceiver.cpp:653:80: error:
‘RIG_PASSBAND_NOCHANGE’ was not declared in this scope
error_check (rig_set_mode (rig_.data (), RIG_VFO_CURR, new_mode,
RIG_PASSBAND_NOCHANGE), tr ("setting current VFO mode"));
^
/home/pi/wsjtx-1.7.0/src/HamlibTransceiver.cpp: In member function ‘virtual
void HamlibTransceiver::do_tx_frequency(Transceiver::Frequency, bool)’:
/home/pi/wsjtx-1.7.0/src/HamlibTransceiver.cpp:731:88: error:
‘RIG_PASSBAND_NOCHANGE’ was not declared in this scope
error_check (rig_set_mode (rig_.data (), RIG_VFO_CURR,
new_mode, RIG_PASSBAND_NOCHANGE), tr ("setting current VFO mode"));
^
/home/pi/wsjtx-1.7.0/src/HamlibTransceiver.cpp:744:99: error:
‘RIG_PASSBAND_NOCHANGE’ was not declared in this scope
error_check (rig_set_split_freq_mode (rig_.data (),
RIG_VFO_CURR, tx, new_mode, RIG_PASSBAND_NOCHANGE), tr ("setting split TX
frequency and mode"));
^
/home/pi/wsjtx-1.7.0/src/HamlibTransceiver.cpp: In member function ‘virtual
void HamlibTransceiver::do_mode(Transceiver::MODE)’:
/home/pi/wsjtx-1.7.0/src/HamlibTransceiver.cpp:803:76: error:
‘RIG_PASSBAND_NOCHANGE’ was not declared in this scope
error_check (rig_set_mode (rig_.data (), RIG_VFO_CURR, new_mode,
RIG_PASSBAND_NOCHANGE), tr ("setting current VFO mode"));
^
/home/pi/wsjtx-1.7.0/src/HamlibTransceiver.cpp:816:76: error:
‘RIG_PASSBAND_NOCHANGE’ was not declared in this scope
error_check (rig_set_mode (rig_.data (), RIG_VFO_CURR, new_mode,
RIG_PASSBAND_NOCHANGE), tr ("setting current VFO mode"));
^
/home/pi/wsjtx-1.7.0/src/HamlibTransceiver.cpp:828:82: error:
‘RIG_PASSBAND_NOCHANGE’ was not declared in this scope
error_check (rig_set_split_mode (rig_.data (), RIG_VFO_CURR,
new_mode, RIG_PASSBAND_NOCHANGE), tr ("setting split TX VFO mode"));
^
CMakeFiles/wsjt_qt.dir/build.make:612: recipe for target
'CMakeFiles/wsjt_qt.dir/HamlibTransceiver.cpp.o' failed
make[2]: *** [CMakeFiles/wsjt_qt.dir/HamlibTransceiver.cpp.o] Error 1
make[2]: *** Waiting for unfinished jobs....
Scanning dependencies of target wsjtx_udp-static
[ 75%] Building CXX object CMakeFiles/wsjtx_udp-static.dir/Radio.cpp.o
[ 75%] Building CXX object CMakeFiles/wsjtx_udp-static.dir/RadioMetaType.cpp.o
CMakeFiles/Makefile2:1209: recipe for target 'CMakeFiles/wsjt_qt.dir/all' failed
make[1]: *** [CMakeFiles/wsjt_qt.dir/all] Error 2
make[1]: *** Waiting for unfinished jobs....
[ 75%] Building CXX object CMakeFiles/wsjtx_udp-static.dir/NetworkMessage.cpp.o
[ 75%] Building CXX object CMakeFiles/wsjtx_udp-static.dir/MessageServer.cpp.o
[ 76%] Building CXX object
CMakeFiles/wsjtx_udp-static.dir/wsjtx_udp-static_automoc.cpp.o
Linking CXX static library libwsjtx_udp.a
[ 76%] Built target wsjtx_udp-static
Makefile:137: recipe for target 'all' failed
make: *** [all] Error 2
pi@raspberrypi:~/wsjtx-1.7.0/build/debug $
On Monday, May 30, 2016 4:02 PM, Bill Somerville <[email protected]>
wrote:
On 30/05/2016 19:03, Jim Bennett wrote:
> I probably mis-interpreted the output of the traceback; saw the memory
> access error and ässumed" it was what caused the program to not
> complete initialization. So, next steps?
Hi Jim,
let's try a debug build. To do that you are probably best to create a
second build tree and keep the release configuration tree for release
builds. So create a new build directory, something like:
mkdir ~/wsjtx-prefix/build/debug
then change working directory to it and configure the build. The
difference in the configure is that you must set CMAKE_BUILD_TYPE=Debug
and set a different CMAKE_INSTALL_PREFIX so that the Debug build gets
installed in a different place from the release configuration install.
Something like:
cd ~/wsjtx-prefix/build/debug
cmake -D CMAKE_BUILD_TYPE=Debug \
-D CMAKE_INSTALL_PREFIX=~/wsjtx-prefix/debug \
-D CMAKE_PREFIX_PATH=~/hamlib-prefix \
-D WSJT_GENERATE_DOCS=OFF \
~/wsjtx-prefix/src
cmake --build . --target install -- -j2
Adjust paths above to suit your installation. Once the build is complete
you can test the debug build like:
~/wsjtx-prefix/debug/bin/wsjtx
If it hangs in the same way try running it under gdb and using CTRL+C to
break in, then interrogate the threads and current thread back trace as
before:
gdb ~/wsjtx-prefix/debug/bin/wsjtx
(gdb) r
... program hangs ...
^C
(gdb) info threads
... prints threads ...
(gdb) bt
... prints current thread stack back trace ...
(gdb) q
There should be much more information in the stack back trace from the
debug configuration build.
73
Bill
G4WJS.
------------------------------------------------------------------------------
What NetFlow Analyzer can do for you? Monitors network bandwidth and traffic
patterns at an interface-level. Reveals which users, apps, and protocols are
consuming the most bandwidth. Provides multi-vendor support for NetFlow,
J-Flow, sFlow and other flows. Make informed decisions using capacity
planning reports. https://ad.doubleclick.net/ddm/clk/305295220;132659582;e
_______________________________________________
wsjt-devel mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/wsjt-devel
------------------------------------------------------------------------------
What NetFlow Analyzer can do for you? Monitors network bandwidth and traffic
patterns at an interface-level. Reveals which users, apps, and protocols are
consuming the most bandwidth. Provides multi-vendor support for NetFlow,
J-Flow, sFlow and other flows. Make informed decisions using capacity
planning reports. https://ad.doubleclick.net/ddm/clk/305295220;132659582;e
_______________________________________________
wsjt-devel mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/wsjt-devel
