Bug: raspberrypi-firmware-tools-20160703-1 [solved]

[graysky]

It seems as though raspberrypi-firmware-tools-20160703-1 does not provide libbcm_host.so that kodi-rbp-16.1-2 expects it. Kodi does not launch with it installed. Output from journalctl:
$this->bbcode_second_pass_code('', 'kodi-standalone[287]: /usr/lib/kodi/kodi.bin: error while loading shared libraries: libbcm_host.so: cannot open shared object file: No such file or directory')

Downgrading to 20160627-1 fixes the issue.

As an aside, is the forum still the best place to report bugs like this?

[modul]

Without touching the system as root with ldconfig you can do this:

$this->bbcode_second_pass_code('', '
export LD_LIBRARY_PATH=$LD_LIBRARY_PATH:/opt/vc/lib
kodi-standalone
')

[graysky]

$this->bbcode_second_pass_quote('modul', 'W')ithout touching the system as root with ldconfig you can do this:

$this->bbcode_second_pass_code('', '
export LD_LIBRARY_PATH=$LD_LIBRARY_PATH:/opt/vc/lib
kodi-standalone
')

[Superpiffer]

You can uncomment $this->bbcode_second_pass_code('', '/opt/vc/lib/GL') in /etc/ld.so.conf.d/00-raspberrypi-firmware.conf and run ldconfig, I think that is the right way to solve this.

[graysky]

$this->bbcode_second_pass_quote('Superpiffer', 'Y')ou can uncomment $this->bbcode_second_pass_code('', '/opt/vc/lib/GL') in /etc/ld.so.conf.d/00-raspberrypi-firmware.conf and run ldconfig, I think that is the right way to solve this.

[Superpiffer]

You're right! What I meant is that this modification was done by raspberry firmware group in the last two days due to incompatibilities with Mesa, I think that they will document at some point infact the libraries are saved in another folder and there is the commented line in 00-raspberrypi-firmware.conf file. Just saying...

[WarheadsSE]

The problem lies in the Pi Foundation only having to deal with one architecture's worth of binaries, and how they handle the userland of that. Anything outside of their expectations appears to be outside their consideration.

[graysky]

That's unfortunate. It seems as though 20160706-1 fixes the problem! Thanks to the dev team for all the work you guys do