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

libfreenect.so.0.4: cannot open shared object file: No such file or directory #382

Closed
hellocatfood opened this issue Apr 13, 2014 · 6 comments
Milestone

Comments

@hellocatfood
Copy link

I have compiled libfreenect on Ubuntu 13.10. When I run freenect-glview I am given the following error:

freenect-glview: error while loading shared libraries: libfreenect.so.0.4: cannot open shared object file: No such file or directory

@piedar
Copy link
Contributor

piedar commented Apr 14, 2014

$ cd build
$ ldd bin/freenect-glview | grep libfreenect.so
libfreenect.so.0.4 => /home/benn/code/libfreenect-upstream/build/lib/libfreenect.so.0.4 (0x00007fc0e7108000)
$ ls -hg lib/ | grep libfreenect.so
lrwxrwxrwx 1 users   18 Apr 13 21:30 libfreenect.so -> libfreenect.so.0.4
lrwxrwxrwx 1 users   20 Apr 13 21:30 libfreenect.so.0.4 -> libfreenect.so.0.4.1
-rwxr-xr-x 1 users  54K Apr 13 21:30 libfreenect.so.0.4.1

You ought to see similar results.

@hellocatfood
Copy link
Author

Yes, I do get similar results. I can run freenect-glview from the building directory but if I do "make install" it appears that the lib folder isn't copied over and isn't found, hence reporting the bug

@piedar
Copy link
Contributor

piedar commented Apr 14, 2014

This could be because Ubuntu decided to use /usr/lib/x86_64-linux-gnu instead of /usr/lib64. I don't know why they did this; probably just to annoy me...

@hellocatfood
Copy link
Author

Possibly! Could this be patched or instructions for Ubuntu users added to the README file?

@piedar
Copy link
Contributor

piedar commented Apr 14, 2014

I bet it would work to change all instances of "${PROJECT_LIBRARY_INSTALL_DIR}" to lib and let platform symlinks work out where the libs actually go.

@piedar piedar added this to the v0.4.2 milestone Apr 15, 2014
@piedar piedar closed this as completed in 935a998 Apr 15, 2014
@roboflank
Copy link

sudo ldconfig -v works for me.

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