Perry Smith wrote: > LD_LIBRARY_PATH may not be resampled each time a library is loaded. I'm > not sure. The loader uses it but it gets it from the processes > environment. The question is when.
I read some articles about this and ld.so (normally linked by libc.so) calls_dl_init_paths() when it's initializing. After this, there are no more calls to this function. The input is drawn from the environment and /etc/ld.so.conf. There's not a lot to do about this, other than setting it before. In the question above, I think it shouldn't be a problem to include /usr/local/lib in your /etc/ld.so.conf (you need root access of course). Another dirty hack might be to set the LD_LIBRARY_PATH and then fork. The new process should load the newly set path, but I'm not sure if you want to fork a complete rails stack (I've done it in the past, but doesn't feel very right). -- Posted via http://www.ruby-forum.com/. --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Ruby on Rails: Talk" group. To post to this group, send email to rubyonrails-talk@googlegroups.com To unsubscribe from this group, send email to rubyonrails-talk+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/rubyonrails-talk?hl=en -~----------~----~----~----~------~----~------~--~---
