View Single Post
Old 11-28-2014, 04:33 AM   #12
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 brianinmaine View Post
Tried like this:
/mnt/us/extensions/pianobar/ # LD_LIBRARY_PATH=./lib:/usr/lib:/lib LD_DEBUG=libs bin/pianobar

I get lots of output, but none of it is the alsa stuff. Pianobar loads properly, I type in my email and password, select station and it starts to play - this is with the symlink to libalsa.so in /usr/lib/ao/plugins-4/libalsa.so pointing to the local copy. The output is all the libs loaded EXCEPT the libalsa.so library.
- - - - -
In that case, then it isn't dynamic load requirement, but instead an application resource loaded by dl(open) and friends.

The build linkage command should mention libdl (-dl) and this is at least one of the places its being used.

Hawhill had mentioned something about this earlier in this thread.

- - - - -

I read on, further than I quoted, and see you figured that one out and how to change the configuration of where it looks at runtime for its dlopen'd resources.

- - - - -

Just the same, this sort of failure forensics is one of those 'developer tricks' that sometimes has to be used.
knc1 is offline   Reply With Quote