UART DMX plugin on Bullseye not showing

[pete111]

Hi, I found this topic #1760 but I found out that UART native DMX option is not showing on latest Raspberry pi OS Bullseye again. :(
How can I please try to compile version of OLA, which should work? (step by step please as am not very eperienced)

many thanks

P.S. I istalled sudo apt-get install ola - but i installed version0.10.8 and not 0.10.9 (where should it be fixed already)

[DaAwesomeP]

Hi @pete111,

It seems that 10.9 did not make it into Bullseye but did make it into Bookworm. @yoe manages the packages in the Debian repo.

We have started running builds in this repo (to have downloadable *.deb packages), but unfortunately they are only for amd64 at this point and not yet armhf or arm64.

Building OLA shouldn't be too difficult! There are some steps here: https://github.com/OpenLightingProject/ola/blob/master/README.debian Give these a try and let us know where you land!

[pete111]

hi @DaAwesomeP,
thanks fr your quick reply.

I went through:
./configure --enable-rdm-tests
make
make check
sudo make install
sudo ldconfig

Seems something is compiled.
But when I try in command line "olad -v" it returns "-bash: /usr/bin/olad: No such file or directory"
I am missing some point, I think

Any idea please?

[peternewman]

What happens if you run:

sudo apt-get install locate
sudo updatedb
locate olad

What did the end of the sudo make install look like? Is there an olad in olad/olad where you compiled it?

[DaAwesomeP]

But when I try in command line "olad -v" it returns "-bash: /usr/bin/olad: No such file or directory"

@pete111 just to be safe, fully remove the OLA installed via APT: apt-get purge ola && apt-get autoremove.

When running executables/applications from a local folder you need to prepend the command with a . or / to signify you are referencing an exact path to a program and not a program installed system-wide. For example:

./path/to/olad -v
/home/myuser/path/to/olad -v

So look for the olad binary (if you use ls it might show up in green) and try running it with the relative path from the folder your shell/terminal is in.

[peternewman]

When running executables/applications from a local folder you need to prepend the command with a . or / to signify you are referencing an exact path to a program and not a program installed system-wide.

Very sensible troubleshooting @DaAwesomeP although obviously the make install should have resulted in a system-wide binary being available (although possibly in /usr/local/bin by default thinking about it, but I'd expect that to still be in the path (I think).

[DaAwesomeP]

although obviously the make install should have resulted in a system-wide binary being available

Ah, you're right! I totally missed the sudo make install there.