On Sun, Aug 29, 2004 at 12:52:30PM -0400, Stas Bekman wrote:
It took me a while to figure out what was the problem with some 3rd party library using libapr. Eventually I've discovered that the libapr-0.so.0 symlink wasn't getting updated on 'make install', the old link to an older library was kept intact. Is it a bug?
/home/stas/httpd/prefork/lib> ls -l libapr-0.so.0 lrwxrwxrwx 1 stas stas 17 Aug 29 12:34 libapr-0.so.0 -> libapr-0.so.0.9.5 /home/stas/httpd/prefork/lib> cp libapr-0.so.0.9.5 libapr-0.so.0.9.5-old
This is an artificial test case - what's the real failure? An upgrade from what to what is behaving like this?
What's happening in the above case is that the libtool install mode runs ldconfig -n for that directory, and ldconfig updates the symlinks to point to the "latest" version available as appropriate, where it presumes that 0.9.5-old is a greater version than 0.9.5.
Ah, that explains it, I had it linked to 0.9.5-nondebug from 1 year ago and it wasn't getting replaced. Thanks for the explanation Joe.
-- __________________________________________________________________ Stas Bekman JAm_pH ------> Just Another mod_perl Hacker http://stason.org/ mod_perl Guide ---> http://perl.apache.org mailto:[EMAIL PROTECTED] http://use.perl.org http://apacheweek.com http://modperlbook.org http://apache.org http://ticketmaster.com
