View Single Post
Old 05-23-2012, 09:31 AM   #87
knc1
Going Viral
knc1 ought to be getting tired of karma fortunes by now.knc1 ought to be getting tired of karma fortunes by now.knc1 ought to be getting tired of karma fortunes by now.knc1 ought to be getting tired of karma fortunes by now.knc1 ought to be getting tired of karma fortunes by now.knc1 ought to be getting tired of karma fortunes by now.knc1 ought to be getting tired of karma fortunes by now.knc1 ought to be getting tired of karma fortunes by now.knc1 ought to be getting tired of karma fortunes by now.knc1 ought to be getting tired of karma fortunes by now.knc1 ought to be getting tired of karma fortunes by now.
 
knc1's Avatar
 
Posts: 17,212
Karma: 18210809
Join Date: Feb 2012
Location: Central Texas
Device: No K1, PW2, KV, KOA
Quote:
Originally Posted by geekmaster View Post
See my fix above. On firmware 3.3 the /usr/lib folder is missing some "generic" symlinks to the libraries in /lib. You can compare to other firmware versions to see what is missing.
Actually, that is a bit misleading - although correct for the lab126 file system layout.
There should not be any links between the content of /usr/lib/* and /lib/* - but there existance is a lab126 screw-up that we have to live with.

Quote:
Originally Posted by geekmaster View Post
Another reported problem for some people is that a symlink to a symlink might not work sometimes (but it worked for me for libc.so). In that case change the symlink destination to the actual versions-dependent binary library file.
That is what I am about to direct the O.P. to do, once I know the contents of that too short lab126 brain fart.
knc1 is offline   Reply With Quote