Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

A fresh install needs to run ldconfig manually #17

Closed
kbingham opened this issue Nov 20, 2020 · 5 comments
Closed

A fresh install needs to run ldconfig manually #17

kbingham opened this issue Nov 20, 2020 · 5 comments

Comments

@kbingham
Copy link
Owner

It would seem that installing libcamera from clean requires a manual invocation of ldconfig to update the ld paths.
I'd expect this to be handled by the install phase, so perhaps something is missing.

@benbaker76
Copy link

I was getting the following error when running cam --list:
cam: error while loading shared libraries: libcamera-base.so.0: cannot open shared object file: No such file or directory

I then ran ldconfig which gave me an error:
/sbin/ldconfig.real: Can't create temporary cache file /etc/ld.so.cache~: Permission denied

So I ran sudo ldconfig then re-compiled and installed libcamera and this time cam --list ran as expected.

@kbingham
Copy link
Owner Author

You don't need to recompile after running sudo ldconfig.

The issue is that on first install the libraries get put in to your system and the linker needs to be update.
When you install a package using something like apt or such the package manager does this for you, but meson doesn't.

Unless perhaps we can add a post install hook maybe...

@kbingham
Copy link
Owner Author

kbingham commented Dec 3, 2021

This should all be resolved by:

mesonbuild/meson#4737

@kbingham kbingham closed this as completed Dec 3, 2021
@mfreeborn
Copy link

Just to say, I stumbled across this issue today on my desktop computer, but also on github CI: lit-robotics/libcamera-rs#12

@kbingham
Copy link
Owner Author

kbingham commented Mar 8, 2023

So mesonbuild/meson#9721 brought this back in. The answer is simply to manually run sudo ldconfig when required as I understand it.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants