Hi, I recently managed to install EIBD on a Mac Mini running OSX 10.6 server, moving on to the installation of linknx.
So far EIBD works (connecting a linux box wiith linknx and knxweb is fine), when installing linknx (using pthsem 2.0.8 and argp-standalone-1.3), I can send commands via linknx/eibd to the bus but cannot sense the status.
Using linknx-cmd.php called from a web browser, I can see the XML incomming requests from the web browser, being understood and the proper answer is genererated within xmlserver, thus pth_write_ev is called with the answer message. BUT the message does not come out on the link (does not come back to the web browsert). When linknx is interrupted with Ctrl C (sigint), linknx terminates and the message is finally received by the web browser.
Has someone ever been able to run linknx on OSX 10.6 (I used the standard Apple development tools for the build) ?
Is there any issue with pthsem on OSX 10.6 ?
Any hint would be greatly appreciated.
JP.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Anonymous
-
2012-10-18
Found the reasong behind problem, some xml replies are ended with a \n some are not and that makes a difference with the OSX build. Added a bug and a resolution proposal.
I have now a fully (seemingly) functional OSX 10.6 knx suite (eibd - linknx -knxweb).
JP.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Hi, I recently managed to install EIBD on a Mac Mini running OSX 10.6 server, moving on to the installation of linknx.
So far EIBD works (connecting a linux box wiith linknx and knxweb is fine), when installing linknx (using pthsem 2.0.8 and argp-standalone-1.3), I can send commands via linknx/eibd to the bus but cannot sense the status.
Using linknx-cmd.php called from a web browser, I can see the XML incomming requests from the web browser, being understood and the proper answer is genererated within xmlserver, thus pth_write_ev is called with the answer message. BUT the message does not come out on the link (does not come back to the web browsert). When linknx is interrupted with Ctrl C (sigint), linknx terminates and the message is finally received by the web browser.
Has someone ever been able to run linknx on OSX 10.6 (I used the standard Apple development tools for the build) ?
Is there any issue with pthsem on OSX 10.6 ?
Any hint would be greatly appreciated.
JP.
Found the reasong behind problem, some xml replies are ended with a \n some are not and that makes a difference with the OSX build. Added a bug and a resolution proposal.
I have now a fully (seemingly) functional OSX 10.6 knx suite (eibd - linknx -knxweb).
JP.