Skip to content


Subversion checkout URL

You can clone with HTTPS or Subversion.

Download ZIP


checking sym-links against firmware toolset, like raspistill #109

sentfanwyaerda opened this Issue · 5 comments

3 participants


To start: I don't know "who" is "responsible", but it could be a feature of rpi-update to check against existing symlinks to the programs provided by RPi firmware. If already, then it did fail on my RPi.

I was trying to get the pi-cam operating, used the option in raspi-config and ran rpi-update, but afterwards couldn't execute raspistill et al. (Do not know if I could [not] before.)

My situation: missing symlinks to /opt/vc/bin/* from /usr/bin/ and to /opt/vc/lib/*.so from /usr/lib/

Or is it better to be fixed (to check/create the symlinks) in raspi-config (I did fork), for example?

It could also be a "bug" in the raspberry-version of Kali (my current distribution) [CONFIRMED]


The sym-links are part of the raspbian distribution (they are there by default in new images, or get added with "apt-get upgrade" for older images).

Nothing to do with rpi-update.

You need to report this to Kali.

@popcornmix popcornmix closed this

I just did. (still I find it a good feature request, since you can get rpi-update WITHOUT apt-get, in an raspberry-toolset-unaware-distribution, other then raspbian. )


But if it's not raspbian, I don't know if /usr/bin is the desired place to create symlinks. Really that is a distribution decision.


Still true. They should have made a decision.

On the practical side: you could check if $X from ls /opt/vc/bin/, is somewhere (whereis $X) within echo $PATH, if not: ln -s /opt/vc/bin/$X `echo $PATH | cut -d: -f1`/$X. And the same for ln -s /opt/vc/lib/$ `echo $PATH | cut -d: -f1 | sed 's/bin/lib/g'`/$ In my case /usr/local/bin and /usr/local/lib, which are very suitable locations.


There's strictly not even any need for symlinks, it's again a decision to be made by the distro.
If you wanted to you could simply add /opt/vc/bin/ to $PATH and add /opt/vc/lib/ to the ldconfig search path via /etc/ (and the latter is actually how Raspbian handles the VideoCore libs - look at /etc/

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Something went wrong with that request. Please try again.