<div dir="ltr"><div><div><div>Mhm. Es scheint noch zu früh für mich:<br><br>pi@NT-Meter ~/vzlogger $ export CXX=g++-4.8; sudo cmake .<br>Compiling for target ''<br>-- using gcc compiler GNU<br>-- checking if -Wno-ignored-qualifiers works<br>-- FindSml check<br>-- checking for module 'sml>=0.9'<br>-- package 'sml>=0.9' not found<br>-- SML_HOME env is not set, setting it to /usr/local<br>-- Looking for sml in /usr/local<br>-- FindMBus check<br>-- Looking for libmbus in /usr/local/include<br>libmbus found: '/usr/local/include'<br>-- FindMicrohttpd check<br>-- checking for module 'microhttpd>=0.9'<br>-- package 'microhttpd>=0.9' not found<br>-- MICROHTTPD_HOME env is not set, setting it to /usr/local<br>-- Looking for microhttpd in /usr/local<br>-- FindJson check<br>-- JSON_HOME env is not set, setting it to /usr/local<br>-- Looking for json in /usr/local<br>Json-c search: '/usr/local/include;/usr/local/include;/usr/local/include;/usr/include'<br>Json-c found: '/usr/local/include'<br>-- FindGnuTls check<br>-- ==> ''<br>-- GNUTLS_HOME env is not set, setting it to /usr/local<br>-- Looking for gnutls in /usr/local<br>==> GNUTLS_LIBRARIES='/usr/lib/arm-linux-gnueabihf/libgnutls.a;/lib/arm-linux-gnueabihf/libgcrypt.a;/usr/lib/arm-linux-gnueabihf/libgpg-error.a;/usr/lib/arm-linux-gnueabihf/libtasn1.a;/usr/lib/arm-linux-gnueabihf/libz.a;-lp11-kit;-lsasl2;/lib/arm-linux-gnueabihf/libgcrypt.a'<br>-- Could NOT find Subversion (missing: Subversion_SVN_EXECUTABLE)<br>CMake Warning at CMakeLists.txt:171 (message):<br> Disabled googlemock/-test tests due to GCC version < 4.8!<br><br><br><br> ***** Configuration parameters *****<br> prefix: /usr/local<br> json: -L/usr/local/lib/libjson-c.a;-lrt -I/usr/local/include<br> sml: -L/usr/lib/libsml.a;-lrt -I/usr/include<br> microhttpd: -L/usr/lib/arm-linux-gnueabihf/libmicrohttpd.a;-lrt -I/usr/include<br> libmbus: -L/usr/local/lib/libmbus.so;-lm -I/usr/local/include<br>-- Configuring done<br>-- Generating done<br>-- Build files have been written to: /home/pi/vzlogger<br><br>pi@NT-Meter ~/vzlogger $ make<br>/usr/bin/cmake -H/home/pi/vzlogger -B/home/pi/vzlogger --check-build-system CMakeFiles/Makefile.cmake 0<br>/usr/bin/cmake -E cmake_progress_start /home/pi/vzlogger/CMakeFiles /home/pi/vzlogger/CMakeFiles/progress.marks<br>make -f CMakeFiles/Makefile2 all<br>make[1]: Entering directory '/home/pi/vzlogger'<br>make -f src/CMakeFiles/vz.dir/build.make src/CMakeFiles/vz.dir/depend<br>make[2]: Entering directory '/home/pi/vzlogger'<br>cd /home/pi/vzlogger && /usr/bin/cmake -E cmake_depends "Unix Makefiles" /home/pi/vzlogger /home/pi/vzlogger/src /home/pi/vzlogger /home/pi/vzlogger/src /home/pi/vzlogger/src/CMakeFiles/vz.dir/DependInfo.cmake --color=<br>make[2]: Leaving directory '/home/pi/vzlogger'<br>make -f src/CMakeFiles/vz.dir/build.make src/CMakeFiles/vz.dir/build<br>make[2]: Entering directory '/home/pi/vzlogger'<br>make[2]: Nothing to be done for 'src/CMakeFiles/vz.dir/build'.<br>make[2]: Leaving directory '/home/pi/vzlogger'<br>/usr/bin/cmake -E cmake_progress_report /home/pi/vzlogger/CMakeFiles 10 11 12 13 14 15 16 17 18 19<br>[100%] Built target vz<br>make -f src/protocols/CMakeFiles/proto.dir/build.make src/protocols/CMakeFiles/proto.dir/depend<br>make[2]: Entering directory '/home/pi/vzlogger'<br>cd /home/pi/vzlogger && /usr/bin/cmake -E cmake_depends "Unix Makefiles" /home/pi/vzlogger /home/pi/vzlogger/src/protocols /home/pi/vzlogger /home/pi/vzlogger/src/protocols /home/pi/vzlogger/src/protocols/CMakeFiles/proto.dir/DependInfo.cmake --color=<br>make[2]: Leaving directory '/home/pi/vzlogger'<br>make -f src/protocols/CMakeFiles/proto.dir/build.make src/protocols/CMakeFiles/proto.dir/build<br>make[2]: Entering directory '/home/pi/vzlogger'<br>make[2]: Nothing to be done for 'src/protocols/CMakeFiles/proto.dir/build'.<br>make[2]: Leaving directory '/home/pi/vzlogger'<br>/usr/bin/cmake -E cmake_progress_report /home/pi/vzlogger/CMakeFiles 1 2 3 4 5 6 7 8 9<br>[100%] Built target proto<br>make -f src/api/CMakeFiles/vz-api.dir/build.make src/api/CMakeFiles/vz-api.dir/depend<br>make[2]: Entering directory '/home/pi/vzlogger'<br>cd /home/pi/vzlogger && /usr/bin/cmake -E cmake_depends "Unix Makefiles" /home/pi/vzlogger /home/pi/vzlogger/src/api /home/pi/vzlogger /home/pi/vzlogger/src/api /home/pi/vzlogger/src/api/CMakeFiles/vz-api.dir/DependInfo.cmake --color=<br>make[2]: Leaving directory '/home/pi/vzlogger'<br>make -f src/api/CMakeFiles/vz-api.dir/build.make src/api/CMakeFiles/vz-api.dir/build<br>make[2]: Entering directory '/home/pi/vzlogger'<br>make[2]: Nothing to be done for 'src/api/CMakeFiles/vz-api.dir/build'.<br>make[2]: Leaving directory '/home/pi/vzlogger'<br>/usr/bin/cmake -E cmake_progress_report /home/pi/vzlogger/CMakeFiles 20 21 22 23 24 25<br>[100%] Built target vz-api<br>make -f src/CMakeFiles/vzlogger.dir/build.make src/CMakeFiles/vzlogger.dir/depend<br>make[2]: Entering directory '/home/pi/vzlogger'<br>cd /home/pi/vzlogger && /usr/bin/cmake -E cmake_depends "Unix Makefiles" /home/pi/vzlogger /home/pi/vzlogger/src /home/pi/vzlogger /home/pi/vzlogger/src /home/pi/vzlogger/src/CMakeFiles/vzlogger.dir/DependInfo.cmake --color=<br>make[2]: Leaving directory '/home/pi/vzlogger'<br>make -f src/CMakeFiles/vzlogger.dir/build.make src/CMakeFiles/vzlogger.dir/build<br>make[2]: Entering directory '/home/pi/vzlogger'<br>Linking CXX executable vzlogger<br>cd /home/pi/vzlogger/src && /usr/bin/cmake -E cmake_link_script CMakeFiles/vzlogger.dir/link.txt --verbose=1<br>/usr/bin/c++ -W -Wall -Wextra -Werror -Wnon-virtual-dtor -Wno-system-headers -Winit-self -Wmissing-include-dirs -Wno-pragmas -Wredundant-decls -Wno-unused-parameter -std=c++11 -fpermissive -Wno-error=redundant-decls -Wno-ignored-qualifiers CMakeFiles/vzlogger.dir/vzlogger.cpp.o CMakeFiles/vzlogger.dir/ltqnorm.cpp.o CMakeFiles/vzlogger.dir/Meter.cpp.o CMakeFiles/vzlogger.dir/__/gitSha1.cpp.o CMakeFiles/vzlogger.dir/CurlSessionProvider.cpp.o CMakeFiles/vzlogger.dir/PushData.cpp.o -o vzlogger -rdynamic protocols/libproto.a libvz.a api/libvz-api.a /usr/local/lib/libjson-c.a -lrt -Wl,-Bstatic -lsml -Wl,-Bdynamic -lrt /usr/local/lib/libmbus.so -lm -Wl,-Bstatic -lmicrohttpd -Wl,-Bdynamic -lrt -lgcrypt -lpthread -lm -luuid -ldl -lcurl -Wl,-Bstatic -lgnutls -lgcrypt -lgpg-error -ltasn1 -lz -Wl,-Bdynamic -lp11-kit -lsasl2 -Wl,-Bstatic -lgcrypt -Wl,-Bdynamic -lssl -lcrypto -latomic -Wl,-Bstatic -lsml -Wl,-Bdynamic /usr/local/lib/libmbus.so -lm -Wl,-Bstatic -lmicrohttpd -Wl,-Bdynamic -lgcrypt -lpthread -lm -luuid -ldl -lcurl -Wl,-Bstatic -lgnutls -lgcrypt -lgpg-error -ltasn1 -lz -Wl,-Bdynamic -lp11-kit -lsasl2 -Wl,-Bstatic -lgcrypt -lgpg-error -ltasn1 -lz -Wl,-Bdynamic -lp11-kit -lsasl2 -lssl -lcrypto -latomic -Wl,-rpath,/usr/local/lib<br>/usr/bin/ld: cannot find -latomic<br>collect2: error: ld returned 1 exit status<br>src/CMakeFiles/vzlogger.dir/build.make:248: recipe for target 'src/vzlogger' failed<br>make[2]: *** [src/vzlogger] Error 1<br>make[2]: Leaving directory '/home/pi/vzlogger'<br>CMakeFiles/Makefile2:1021: recipe for target 'src/CMakeFiles/vzlogger.dir/all' failed<br>make[1]: *** [src/CMakeFiles/vzlogger.dir/all] Error 2<br>make[1]: Leaving directory '/home/pi/vzlogger'<br>Makefile:146: recipe for target 'all' failed<br>make: *** [all] Error 2<br><br></div>Irgendwie ist die 4.8 nicht aktiv trotz des exports. Gleicher Rechner wie von Matthias getestet.<br><br></div><div>Sollen wir die vzlogger Version aufgrund der anderen Build Umgebung evtl. auf 0.5 erhöhen?<br><br></div>Viele Grüße,<br></div>Andreas<br><br></div><div class="gmail_extra"><br><div class="gmail_quote">2015-11-02 22:44 GMT+01:00 Matthias Behr <span dir="ltr"><<a href="mailto:mbehr@mcbehr.de" target="_blank">mbehr@mcbehr.de</a>></span>:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div style="word-wrap:break-word">Hi,<div><br></div><div>nach:</div><div><div style="margin:0px;font-size:11px;line-height:normal;font-family:Menlo">git clone <a href="https://github.com/volkszaehler/vzlogger.git" target="_blank">https://github.com/volkszaehler/vzlogger.git</a></div></div><div>cd vzlogger</div><div>mkdir build</div><div>cd build</div><div><div style="margin:0px;font-size:11px;line-height:normal;font-family:Menlo">sudo apt-get install gcc-4.8 g++-4.8</div><div style="margin:0px;font-size:11px;line-height:normal;font-family:Menlo"><div style="margin:0px;line-height:normal">export CXX=g++-4.8; cmake ..</div><div style="margin:0px;line-height:normal">make</div><div style="margin:0px;line-height:normal"><div style="margin:0px;line-height:normal">src/vzlogger —version</div><div style="margin:0px;line-height:normal"><br></div><div style="margin:0px;line-height:normal">erscheint:</div><div style="margin:0px;line-height:normal">0.4.7</div><div style="margin:0px;line-height:normal"> based on git version: heads/master-0-gfb43c53abf</div><div style="margin:0px;line-height:normal"> last commit date: Sun, 1 Nov 2015 18:43:54 +0100</div><div style="margin:0px;line-height:normal"><br></div><div style="margin:0px;line-height:normal"><br></div><div style="margin:0px;line-height:normal">Aber bei dir war vorher ja schon gcc-4.7 installiert. Das habe ich nicht ganz verfolgt. Dabei kann auch per update alternatives gcc-4.8 als default gesetzt werden, das ist bei dir jetzt noch nicht der Fall. Daher ist das export CXX=… vor dem cmake notwendig. </div><div style="margin:0px;line-height:normal">Btw: die „out-of-source Builds“ wie oben in ein spez. Build Directory sind bei cmake vorzuziehen. Dann kann man schnell per rm -rf build einfach alles aufräumen ;-)</div><div style="margin:0px;line-height:normal"><br></div><div style="margin:0px;line-height:normal"> </div></div></div><div><div class="h5"><div><blockquote type="cite"><div>Am 02.11.2015 um 21:47 schrieb Andreas Goetz <<a href="mailto:cpuidle@gmail.com" target="_blank">cpuidle@gmail.com</a>>:</div><br><div><div dir="ltr">Hallöle,<br><div class="gmail_extra"><br><div class="gmail_quote">2015-11-02 20:07 GMT+01:00 Udo1 <span dir="ltr"><<a href="mailto:udo1@gmx.net" target="_blank">udo1@gmx.net</a>></span>:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">Mhhm, gerade festgestellt, dass ich ja das neue Image mit Debian-Jessi habe.<br>
Jetzt stellt sich aber mir die Frage, wieso sollen wir ein alte Debian-Wheezy-Image updaten?<br>
Wäre es nicht einfacher die Datenbank zu sichern, auf das neue Image upzudaten und die Datenbank wieder aufzuspielen?<br></blockquote><div><br></div><div>Hab Matthias eine upgegradete Wheezy geschickt- erstmal besser als nix.<br> <br></div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<br>
Gruß<br>
Udo</blockquote><div><br></div><div>Viele Grüße,<br></div><div>Andreas<br> <br></div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div><div><br>
<br>
Am 02.11.2015 um 19:29 schrieb Matthias Behr:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
gute Idee.<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
Am 02.11.2015 um 19:24 schrieb Udo1 <<a href="mailto:udo1@gmx.net" target="_blank">udo1@gmx.net</a>>:<br>
<br>
Am 02.11.2015 um 19:05 schrieb Andreas Götz:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
Ich schick Dir ssh auf Raspi per pm.<br>
</blockquote>
Wäre es nicht besser Matthias würde sich auf meinen Raspi einloggen? Dann kann ich hinterher ein neues Image erstellen.<br>
<br>
Gruß<br>
Udo<br>
</blockquote>
Gruß<br>
<br>
Matthias<br>
<br>
<br>
</blockquote>
<br>
</div></div></blockquote></div><br></div></div>
</div></blockquote></div><br></div></div><div>
<span style="border-collapse:separate;line-height:normal;border-spacing:0px"><div style="word-wrap:break-word"><div>Gruß</div><span class="HOEnZb"><font color="#888888"><div><br></div><div>Matthias</div></font></span></div></span>
</div>
<br></div></div></blockquote></div><br></div>