Package Details: domoticz-git r8875-1

Git Clone URL: (read-only, click to copy)
Package Base: domoticz-git
Description: Web based home automation
Upstream URL:
Keywords: domoticz openzwave
Licenses: GPL
Conflicts: domoticz-svn
Submitter: IanDury
Maintainer: melvinvermeeren
Last Packager: melvinvermeeren
Votes: 8
Popularity: 0.000000
First Submitted: 2015-08-23 18:43
Last Updated: 2018-02-03 10:27

Latest Comments

1 2 3 4 5 6 Next › Last »

k96hkh commented on 2019-10-19 20:35

It's compiling AND linking fine now. I don't why but maybe it had something to do with that changes to PluginManager.cpp got committed a few days ago.


k96hkh commented on 2019-10-08 05:55


After a general arch linux update about a week ago I no longer can get domoticz to compile. I get undefined reference in PluginManager, see below. Openzwave is up to date.

Help Obi Wan Kenobi, you are my only hope.

[ 3%] Linking CXX executable domoticz /usr/bin/ld: CMakeFiles/domoticz.dir/hardware/plugins/PluginManager.cpp.o: in function http::server::CWebServer::PluginList(Json::Value&)': PluginManager.cpp:(.text+0x3dd2): undefined reference toJson::Value::operator=(Json::Value&&)' /usr/bin/ld: PluginManager.cpp:(.text+0x3e12): undefined reference to Json::Value::operator=(Json::Value&&)' /usr/bin/ld: PluginManager.cpp:(.text+0x3e63): undefined reference toJson::Value::operator=(Json::Value&&)' /usr/bin/ld: PluginManager.cpp:(.text+0x3eaa): undefined reference to Json::Value::operator=(Json::Value&&)' /usr/bin/ld: PluginManager.cpp:(.text+0x3efb): undefined reference toJson::Value::operator=(Json::Value&&)' /usr/bin/ld: CMakeFiles/domoticz.dir/hardware/plugins/PluginManager.cpp.o:PluginManager.cpp:(.text+0x3f42): more undefined references to `Json::Value::operator=(Json::Value&&)' follow collect2: fel: ld returnerade avslutningsstatus 1 make[2]: [CMakeFiles/domoticz.dir/build.make:3652: domoticz] Fel 1 make[1]: [CMakeFiles/Makefile2:81: CMakeFiles/domoticz.dir/all] Fel 2 make: *** [Makefile:152: all] Fel 2 ==> FEL: Ett fel uppstod i package(). Avbryter...

melvinvermeeren commented on 2018-02-03 10:30

ncom511 looks like upstream fixed boost 1.66 compilation, so the patch conflicted. Should work now.

ncom511 commented on 2018-02-03 07:02

Build fails. no matter if I answer Y/N.

==> Starting build()... patching file webserver/proxyclient.cpp Hunk #1 FAILED at 770. 1 out of 1 hunk FAILED -- saving rejects to file webserver/proxyclient.cpp.rej patching file webserver/server.cpp Reversed (or previously applied) patch detected! Assume -R? [n] n Apply anyway? [n] n Skipping patch. 2 out of 2 hunks ignored -- saving rejects to file webserver/server.cpp.rej ==> ERROR: A failure occurred in build(). Aborting...

melvinvermeeren commented on 2018-01-07 18:37

Compilation with boost 1.66 fixed, didn't test runtime.

melvinvermeeren commented on 2018-01-07 17:34

Just pushed update that disables all static linking and disables all built-in libs. This means this will pull in some additional packages now but also reduce this pkg's size and compilation time. Let me know if there are runtime issues as I don't have hardware with me to test a deployment right now.

This also fixes the OpenSSL issue, for some reason domoticz defaults to only looking for static linking and Arch doesn't ship static libs in the regular pkgs.

Also boost changed their API in 1.66 without marking the old API as deprecated first[1], breaking domoticz[2] and probably many other applications. I will see if it is a quick fix, otherwise stay on 1.65 until it is fixed in upstream.



bmd_online commented on 2018-01-07 15:29

Right option is : -DOPENSSL_CRYPTO_LIBRARY=/usr/lib/ -DOPENSSL_SSL_LIBRARY=/usr/lib/

IanDury commented on 2017-02-03 20:47

@fxeon It looks like the upstream open-zwave needs to update the openzwave.spec file. The Changelog shows version 1.5 whereas the spec file still has version 1.4

fxeon commented on 2017-02-02 17:50

@IanDury hello why is openzwave reported as:
Version: 1.4-2382-g450c4a50-dirty
in domoticz-git, when to my understanding current openzwave is 1.5-1? thx for the great work

ImNtReal commented on 2016-10-02 22:52

@IanDury, maybe, but it builds, and runs fine against stable. It would be nice to give the user the choice since depending on openzwave would allow it to build against openzwave or openzwave-git since openzwave-git provides openzwave.