Comments on: PHP and Mac OS X Leopard—A Warning http://foundationphp.com/blog/2007/10/27/php-and-mac-os-x-leoparda-warning/ Tue, 15 May 2012 13:16:10 +0000 hourly 1 http://wordpress.org/?v=3.3.2 By: Josh http://foundationphp.com/blog/2007/10/27/php-and-mac-os-x-leoparda-warning/comment-page-1/#comment-15799 Josh Thu, 19 Feb 2009 02:00:19 +0000 http://foundationphp.com/blog/2007/10/27/php-and-mac-os-x-leoparda-warning/#comment-15799 okay, i took one more look at my db settings and realized i had the wrong name for the host. changed it in the connection file and i'm good to go. thanks, jf okay, i took one more look at my db settings and realized i had the wrong name for the host. changed it in the connection file and i’m good to go. thanks,

jf

]]> By: Josh http://foundationphp.com/blog/2007/10/27/php-and-mac-os-x-leoparda-warning/comment-page-1/#comment-15798 Josh Thu, 19 Feb 2009 01:47:13 +0000 http://foundationphp.com/blog/2007/10/27/php-and-mac-os-x-leoparda-warning/#comment-15798 hi david, i'm new to this stuff and have really enjoyed learning with your dreamweaver cs3 book. i was having a hard time getting mysql up and running on my ppc g5 10.5.6 so i ended up doing a mamp install and everything is working great locally. i synced the site with my remote server and when i try to access the site online i get this error: "Fatal error: Can't connect to local MySQL server through socket '/tmp/mysql.sock' (2) in /data/17/1/95/148/1584637/user/1707142/htdocs/driendlgroup/Connections/DGmampCONN.php on line 9" it seems like there should be an easy solution to this, but it is outside of my understanding. any help you can give would be greatly appreciated. thanks, josh hi david,

i’m new to this stuff and have really enjoyed learning with your dreamweaver cs3 book.

i was having a hard time getting mysql up and running on my ppc g5 10.5.6 so i ended up doing a mamp install and everything is working great locally.

i synced the site with my remote server and when i try to access the site online i get this error:
“Fatal error: Can’t connect to local MySQL server through socket ‘/tmp/mysql.sock’ (2) in /data/17/1/95/148/1584637/user/1707142/htdocs/driendlgroup/Connections/DGmampCONN.php on line 9″

it seems like there should be an easy solution to this, but it is outside of my understanding. any help you can give would be greatly appreciated. thanks,

josh

]]> By: Henrik http://foundationphp.com/blog/2007/10/27/php-and-mac-os-x-leoparda-warning/comment-page-1/#comment-15722 Henrik Wed, 17 Dec 2008 13:22:44 +0000 http://foundationphp.com/blog/2007/10/27/php-and-mac-os-x-leoparda-warning/#comment-15722 Building a soap module for the stock leopard php install works now: http://www.entropy.ch/phpbb2/viewtopic.php?p=12785#12785 Building a soap module for the stock leopard php install works now:
http://www.entropy.ch/phpbb2/viewtopic.php?p=12785#12785

]]> By: Marc Poirier http://foundationphp.com/blog/2007/10/27/php-and-mac-os-x-leoparda-warning/comment-page-1/#comment-15481 Marc Poirier Mon, 23 Jun 2008 17:24:55 +0000 http://foundationphp.com/blog/2007/10/27/php-and-mac-os-x-leoparda-warning/#comment-15481 Hi.. After reading the posts I saw that Sonya had the same problem as I have, in the way that my test.php page only show the code, not the php page... Was this problem addressed? any clues? thanks Marc. Hi.. After reading the posts I saw that Sonya had the same problem as I have, in the way that my test.php page only show the code, not the php page… Was this problem addressed? any clues?

thanks

Marc.

]]> By: David Powers http://foundationphp.com/blog/2007/10/27/php-and-mac-os-x-leoparda-warning/comment-page-1/#comment-15475 David Powers Sun, 15 Jun 2008 13:39:37 +0000 http://foundationphp.com/blog/2007/10/27/php-and-mac-os-x-leoparda-warning/#comment-15475 Sure, but compiling PHP on a Mac isn't easy. If you have the skill to do it, fine. But I suspect that most Mac users don't. It would have been better if Apple had compiled a more fully featured version and made it part of the software update options when a new version of PHP is released. Sure, but compiling PHP on a Mac isn’t easy. If you have the skill to do it, fine. But I suspect that most Mac users don’t. It would have been better if Apple had compiled a more fully featured version and made it part of the software update options when a new version of PHP is released.

]]> By: Whisller http://foundationphp.com/blog/2007/10/27/php-and-mac-os-x-leoparda-warning/comment-page-1/#comment-15474 Whisller Sun, 15 Jun 2008 13:31:28 +0000 http://foundationphp.com/blog/2007/10/27/php-and-mac-os-x-leoparda-warning/#comment-15474 Yeah Leopard has a php 5.2.5 but it doesn't support PostgreSQL, so if you want use it you must re-compile whole php. So I don't see why they added PHP, so you must re-compile it if you want have extensions what you need. Better will be not adding apache and php. Then you can compile it by yourself with configuration what you need. Yeah Leopard has a php 5.2.5 but it doesn’t support PostgreSQL, so if you want use it you must re-compile whole php.
So I don’t see why they added PHP, so you must re-compile it if you want have extensions what you need.

Better will be not adding apache and php. Then you can compile it by yourself with configuration what you need.

]]> By: David Powers http://foundationphp.com/blog/2007/10/27/php-and-mac-os-x-leoparda-warning/comment-page-1/#comment-15453 David Powers Tue, 27 May 2008 17:38:30 +0000 http://foundationphp.com/blog/2007/10/27/php-and-mac-os-x-leoparda-warning/#comment-15453 @Andre: I presume you have been running XAMPP on a Mac without problems, but the XAMPP site still has this message on its front page concerning the Mac version: "WARNING: This version of XAMPP is still in the first steps of development. Use at you own risk!" I wonder if that's an old message that hasn't been updated? @Andre: I presume you have been running XAMPP on a Mac without problems, but the XAMPP site still has this message on its front page concerning the Mac version: “WARNING: This version of XAMPP is still in the first steps of development. Use at you own risk!”

I wonder if that’s an old message that hasn’t been updated?

]]> By: Andre http://foundationphp.com/blog/2007/10/27/php-and-mac-os-x-leoparda-warning/comment-page-1/#comment-15452 Andre Tue, 27 May 2008 16:47:10 +0000 http://foundationphp.com/blog/2007/10/27/php-and-mac-os-x-leoparda-warning/#comment-15452 Solution 1. Download & install XAMPP http://www.apachefriends.org/en/xampp.html 2. Backup /usr/bin/php cp /usr/bin/php /usr/bin/php.backup 3. Create a symbolic link to the XAMPP version ln -s /Applications/xampp/xamppfiles/bin/php /usr/bin/php Solution

1. Download & install XAMPP
http://www.apachefriends.org/en/xampp.html

2. Backup /usr/bin/php
cp /usr/bin/php /usr/bin/php.backup

3. Create a symbolic link to the XAMPP version
ln -s /Applications/xampp/xamppfiles/bin/php /usr/bin/php

]]> By: Henrik http://foundationphp.com/blog/2007/10/27/php-and-mac-os-x-leoparda-warning/comment-page-1/#comment-15442 Henrik Mon, 19 May 2008 12:20:22 +0000 http://foundationphp.com/blog/2007/10/27/php-and-mac-os-x-leoparda-warning/#comment-15442 I've tried building a soap module for the stock php in leopard as well, without success. I really cannot figure out why it should be all that difficult. My struggles are documented here: http://www.entropy.ch/phpbb2/viewtopic.php?t=2956 http://discussions.apple.com/thread.jspa?messageID=7046696&#7046696 Has anyone gotten any further? I’ve tried building a soap module for the stock php in leopard as well, without success. I really cannot figure out why it should be all that difficult. My struggles are documented here:

http://www.entropy.ch/phpbb2/viewtopic.php?t=2956
http://discussions.apple.com/thread.jspa?messageID=7046696&#7046696

Has anyone gotten any further?

]]> By: David G http://foundationphp.com/blog/2007/10/27/php-and-mac-os-x-leoparda-warning/comment-page-1/#comment-15062 David G Fri, 18 Jan 2008 10:00:28 +0000 http://foundationphp.com/blog/2007/10/27/php-and-mac-os-x-leoparda-warning/#comment-15062 Thanks David for the help! It was my user folder who was set to only allow me to se the contents and therefore the sites folder was locked too because it is inside the user folder. Now it seems to work. Thanks! Thanks David for the help!

It was my user folder who was set to only allow me to se the contents and therefore the sites folder was locked too because it is inside the user folder. Now it seems to work. Thanks!

]]>