Quantcast
Channel: SBFspot Issue Tracker Rss Feed
Viewing all articles
Browse latest Browse all 360

Commented Unassigned: Can not get SMAspot running on my Synology [92]

$
0
0
System Data:
Synology Typ: DS212j
DSM Version: DSM 5.1-5021 Update 2
SMAspot Version: SBFspot_SRC_303_Linux_Win32.tar.gz

Dear SMAspot team,

I try to get SMAspot running on my Synology.
But the make process is terminated with the following error message:

_make release
test -d bin/Release || mkdir -p bin/Release
test -d obj/Release || mkdir -p obj/Release
g++ -Wall -O2 -c boost_ext.cpp -o obj/Release/boost_ext.o
g++ -Wall -O2 -c misc.cpp -o obj/Release/misc.o
g++ -Wall -O2 -c strptime.cpp -o obj/Release/strptime.o
g++ -Wall -O2 -c sunrise_sunset.cpp -o obj/Release/sunrise_sunset.o
g++ -Wall -O2 -c SBFNet.cpp -o obj/Release/SBFNet.o
In file included from SBFNet.h:39,
from SBFNet.cpp:36:
bluetooth.h:67:33: error: bluetooth/bluetooth.h: No such file or directory
bluetooth.h:68:30: error: bluetooth/rfcomm.h: No such file or directory
make: *** [obj/Release/SBFNet.o] Error 1_

Bluetooth is already running on my system (see below):

_BusyBox v1.16.1 (2014-12-13 05:30:51 CST) built-in shell (ash)
Enter 'help' for a list of built-in commands.

DiskStation> hcitool scan
Scanning ...
00:80:25:21:DE:43 SMA001d SN: 2110249103 SN2110249103
DiskStation>_

Please can you help me to get the SMAspot running on my system.

Thanks,
Volker
Comments: Dear SMAspot team, my SMAspot was running without faults for 2 years now. After updating my synology to DSM 6.0 the SMAspot keeps running like before. After installing IO::Socket:: SSL with the command "cpan -i IO::Socket::SSL" the SMAspot stops working. root@DiskStation:/home/pi/smaspot/SBFspot# /home/pi/smaspot/SBFspot/bin/Release/SBFspot -nocsv -v Segmentation fault (core dumped) root@DiskStation:/home/pi/smaspot/SBFspot# Each call of my SMA leads to "Segmentation fault (core dumped)" (see above) I loaded the latest version of SMAspot "SBFspot_SRC_331_Linux_Win32.tar.gz" I modified the LDFFLAGS line in the makefile as follows LDFLAGS = -L/usr/lib -Wl,-rpath=/usr/lib The "make release" command was executed as follows: root@DiskStation:/home/pi/smaspot/SBFspot# make release test -d bin/Release || mkdir -p bin/Release test -d obj/Release || mkdir -p obj/Release g++ -Wall -O2 -c boost_ext.cpp -o obj/Release/boost_ext.o g++ -Wall -O2 -c misc.cpp -o obj/Release/misc.o g++ -Wall -O2 -c strptime.cpp -o obj/Release/strptime.o g++ -Wall -O2 -c sunrise_sunset.cpp -o obj/Release/sunrise_sunset.o g++ -Wall -O2 -c SBFNet.cpp -o obj/Release/SBFNet.o g++ -Wall -O2 -c Bluetooth.cpp -o obj/Release/Bluetooth.o g++ -Wall -O2 -c CSVexport.cpp -o obj/Release/CSVexport.o g++ -Wall -O2 -c Ethernet.cpp -o obj/Release/Ethernet.o g++ -Wall -O2 -c EventData.cpp -o obj/Release/EventData.o g++ -Wall -O2 -c ArchData.cpp -o obj/Release/ArchData.o g++ -Wall -O2 -c SBFspot.cpp -o obj/Release/SBFspot.o g++ -Wall -O2 -c TagDefs.cpp -o obj/Release/TagDefs.o g++ -o bin/Release/SBFspot obj/Release/boost_ext.o obj/Release/misc.o obj/Release/strptime.o obj/Release/sunrise_sunset.o obj/Release/SBFNet.o obj/Release/Bluetooth.o obj/Release/CSVexport.o obj/Release/Ethernet.o obj/Release/EventData.o obj/Release/ArchData.o obj/Release/SBFspot.o obj/Release/TagDefs.o -L/usr/lib -Wl,-rpath=/usr/lib -s -lbluetooth -lboost_date_time -lboost_system -lpthread /opt/bin/ld: warning: libc.so.6, needed by /usr/lib/libbluetooth.so, may conflict with libc.so.1 /opt/bin/ld: warning: libm.so.6, needed by /usr/lib/libboost_date_time.so, may conflict with libm.so.1 /opt/bin/ld: warning: libpthread.so.0, needed by /usr/lib/libboost_date_time.so, may conflict with libpthread.so.1 cp TagList*.txt bin/Release cp date_time_zonespec.csv bin/Release root@DiskStation:/home/pi/smaspot/SBFspot# The "make release" was executed without faults (only some warnings), so I tried to call my SMA again. The fault "Segmentation fault (core dumped)" is still there. Do you have any idea to solve this issue?

Viewing all articles
Browse latest Browse all 360

Trending Articles



<script src="https://jsc.adskeeper.com/r/s/rssing.com.1596347.js" async> </script>