From: John J Foerch <jjfoerch@earthlink.net>
To: guix-devel@gnu.org
Subject: Re: [PATCH] gnu: Add ola.
Date: Mon, 22 Aug 2016 15:14:48 -0400 [thread overview]
Message-ID: <87r39gsjiv.fsf@hecubus.retroj.net> (raw)
In-Reply-To: 87oa505q4e.fsf@hecubus.retroj.net
John J Foerch <jjfoerch@earthlink.net> writes:
> rennes@openmailbox.org writes:
>
>> John,
>>
>>> Thank you so much for doing this. If 'make check' succeeds, those are
>>> the main tests, but to check installation, I would look for the
>>> following programs being installed:
>>>
>>> ola ola_e131 ola_plugin_state ola_rdm_set
>>> ola_set_priority ola_trigger ola_uni_name ola_artnet
>>> ola_dmxconsole ola_patch ola_rdm_discover
>>> ola_recorder
>>> ola_streaming_client ola_uni_info ola_uni_stats olad
>>> ola_dmxmonitor ola_plugin_info ola_rdm_get ola_set_dmx
>>> ola_timecode ola_uni_merge ola_usbpro
>>> ola_dev_info
>>>
>>
>> I see only the following programs:
>>
>> ola_artnet ola_plugin_state ola_set_priority
>> ola_uni_name
>> olad ola_rdm_discover ola_streaming_client
>> ola_uni_stats
>> ola_dev_info ola_rdm_get ola_timecode
>> ola_usbpro
>> ola_e131 ola_rdm_set ola_trigger
>> ola_patch ola_recorder ola_uni_info
>> ola_plugin_info ola_set_dmx ola_uni_merge
>>
>
> That seems fine. I don't know what every single one of them does, but
> all of the main ones are present.
>
>>
>>> These are the programs installed by the Debian ola package, and I don't
>>> know what packaging options might have affected which were installed,
>>> but the list should be more or less the same.
>>>
>>> To start the ola daemon and generate a config:
>>>
>>> olad -c ~/my-ola
>>
>> when the command is run, it displays message:
>>
>> $ olad -c ~/my-ola
>>
>> common/io/IOUtils.cpp:39: open(/dev/dmx0): No such file or directory
>> plugins/opendmx/OpenDmxPlugin.cpp:80: Could not open /dev/dmx0 No such
>> file or directory
>> common/network/IPV4Address.cpp:89: Could not convert address 677966233
>> common/io/IOUtils.cpp:39: open(/dev/kldmx0): No such file or directory
>> plugins/karate/KaratePlugin.cpp:79: Could not open /dev/kldmx0 No such
>> file or directory
>>
>
> The ones complaining about missing /dev entries are nothing to worry
> about - those are plugins just looking for hardware that isn't there.
> They can be disabled in files in ~/my-ola, but by default, it will
> search for every kind of device.
>
> The one that I don't know the meaning of is the IPV4Address.cpp:89
> error. I will ask about that.
>
>>
>>
>>> This should start a web service on port 9090, so you can point a web
>>> browser to localhost:9090 and see if anything comes up.
>>
>> the service is not responding. Any ideas?
>>
>> Thanks.
>
> According to this page, http support is an optional build option. I
> wasn't aware of that, but it would be convenient to enable.
>
> https://www.openlighting.org/ola/getting-started/using-ola/#How_to_setup_an_interface
>
> To enable it, it needs libmicrohttpd. It looks like guix has a package
> for that - nice!
>
> Thank you,
>
> --
> John Foerch
I found this to solve the memory issue, so I can build the package now:
https://github.com/OpenLightingProject/ola/issues/1103
Thank you for your help. I am now working on some other issues with the
package and hope to post a patch soon.
--
John Foerch
next prev parent reply other threads:[~2016-08-22 19:15 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <mailman.11647.1470832050.26855.guix-devel@gnu.org>
2016-08-10 14:05 ` [PATCH] gnu: Add ola rennes
2016-08-10 20:24 ` John J Foerch
2016-08-22 19:14 ` John J Foerch [this message]
2016-08-24 2:03 ` John J Foerch
2016-08-25 23:55 John J Foerch
2016-08-26 2:08 ` Alex Vong
2016-08-26 11:47 ` Marius Bakke
2016-08-28 20:01 ` Ludovic Courtès
2016-08-29 14:48 ` John J Foerch
2016-09-01 12:47 ` Ludovic Courtès
2016-09-02 17:56 ` John J Foerch
2016-09-05 8:54 ` Ludovic Courtès
2016-08-26 12:10 ` John J Foerch
[not found] <mailman.10291.1470243841.26857.guix-devel@gnu.org>
2016-08-04 3:26 ` rennes
2016-08-10 11:57 ` John J Foerch
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
List information: https://guix.gnu.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87r39gsjiv.fsf@hecubus.retroj.net \
--to=jjfoerch@earthlink.net \
--cc=guix-devel@gnu.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
Code repositories for project(s) associated with this public inbox
https://git.savannah.gnu.org/cgit/guix.git
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).