Comments on: Upgrading Mac Libraries http://www.elharo.com/blog/mac/2006/11/29/upgrading-mac-libraries/ Ranting and Raving Tue, 02 Dec 2008 15:42:27 +0000 http://wordpress.org/?v=2.6.3 By: greg http://www.elharo.com/blog/mac/2006/11/29/upgrading-mac-libraries/#comment-24010 greg Thu, 30 Nov 2006 17:03:39 +0000 http://www.elharo.com/blog/mac/2006/11/29/upgrading-mac-libraries/#comment-24010 First, I doubt it's using the lib in the SDK. That's a symbols-only stub, not a loadable library with code in it. Second, libxml2.dylib is a symlink to libxml2.2.dylib, which is the actual stub. Resymlinking libxml2.dylib would solve the problem. Third, the real lib is in /usr/lib, and it's also a symlink. So resymlinking it would let you change which lib PHP is using. You could also change PHP's dylib load path (see 'man dylib'), so it searches someplace other than /usr/lib first. That way all the other clients of libxml2.dylib won't be unintentionally redirected to the new lib. I'm not sure exactly how you'd resymlink the stub lib in the SDK, or whether that's even the best approach. Ask on Apple's Xcode-users list for suggestions. I know that simply resymlinking has been suggested in the past, but there might be better suggestions. First, I doubt it’s using the lib in the SDK. That’s a symbols-only stub, not a loadable library with code in it.

Second, libxml2.dylib is a symlink to libxml2.2.dylib, which is the actual stub. Resymlinking libxml2.dylib would solve the problem.

Third, the real lib is in /usr/lib, and it’s also a symlink. So resymlinking it would let you change which lib PHP is using.

You could also change PHP’s dylib load path (see ‘man dylib’), so it searches someplace other than /usr/lib first. That way all the other clients of libxml2.dylib won’t be unintentionally redirected to the new lib.

I’m not sure exactly how you’d resymlink the stub lib in the SDK, or whether that’s even the best approach. Ask on Apple’s Xcode-users list for suggestions. I know that simply resymlinking has been suggested in the past, but there might be better suggestions.

]]> By: Elliotte Rusty Harold http://www.elharo.com/blog/mac/2006/11/29/upgrading-mac-libraries/#comment-23961 Elliotte Rusty Harold Thu, 30 Nov 2006 11:20:25 +0000 http://www.elharo.com/blog/mac/2006/11/29/upgrading-mac-libraries/#comment-23961 I just installed PHP 5.2.0 from source. Maybe I should try Marc Liyanage’s installer instead. That might be the simplest option, except "This module will only work with the original Apache web server as shipped by Apple." and I'm using a custom compiled Apache 2. I just installed PHP 5.2.0 from source. Maybe I should try Marc Liyanage’s installer instead. That might be the simplest option, except “This module will only work with the original Apache web server as shipped by Apple.” and I’m using a custom compiled Apache 2.

]]> By: Todd Ditchendorf http://www.elharo.com/blog/mac/2006/11/29/upgrading-mac-libraries/#comment-23899 Todd Ditchendorf Thu, 30 Nov 2006 03:14:23 +0000 http://www.elharo.com/blog/mac/2006/11/29/upgrading-mac-libraries/#comment-23899 I've been advised from some people I trust that you should not replace the library in the sdk directory. Out of curiousity, I just did a PHP 5.2.0 for Apache 1.3 install using <a href="http://www.entropy.ch/software/macosx/php/" rel="nofollow">Marc Liyanage's installer</a>... I noticed that my phpinfo() page claims that php is using a libxml2 located in: /usr/local/php5/. And the latest libxml2 (2.2.6.26) is indeed installed under lib there. I would guess php is using this. My php.ini file seems to be silent on the issue... I’ve been advised from some people I trust that you should not replace the library in the sdk directory.

Out of curiousity, I just did a PHP 5.2.0 for Apache 1.3 install using Marc Liyanage’s installer… I noticed that my phpinfo() page claims that php is using a libxml2 located in: /usr/local/php5/. And the latest libxml2 (2.2.6.26) is indeed installed under lib there. I would guess php is using this. My php.ini file seems to be silent on the issue…

]]>