gnome-settings-daemon fails to install

2008-10-13 Thread Stefan Gräf
Hi all, While trying to install gnome-settings-daemon on 10.5 I get the error below. Any help is very much appreciated! Cheers, Stefan ---> Building gnome-settings-daemon with target all Error: Target org.macports.build returned: shell command " cd "/opt/local/var/macports/build/_opt_local_v

php5 on OSX10.5.5

2008-10-13 Thread Mark Hattam
What's broken with php5 and 10.5.5 ... ? I've just set up php5, mysql5 and apache2 on a brand new iMac with 10.5.5, and I'm getting a lot of errors in the Apache log The process has forked and you cannot use this CoreFoundation functionality safely. You MUST exec(). Break on __THE_PROCESS_HAS_

Re: php5 on OSX10.5.5

2008-10-13 Thread Chris Janton
On 2008-10-13 , at 03:01 , Mark Hattam wrote: > What's broken with php5 and 10.5.5 ... ? > > I've just set up php5, mysql5 and apache2 on a brand new iMac with > 10.5.5, and I'm getting a lot of errors in the Apache log > > The process has forked and you cannot use this CoreFoundation > functional

Re: macports and Xcode

2008-10-13 Thread Vincent Lefevre
On 2008-10-11 14:50:00 +0200, Emmanuel Hainry wrote: > And those problems would be solved if macports did not rely on third > party tools (gcc, tcl, x11 which have or have had bugs in the past and > apple's versions are not without those bugs). or are out-of-date, leading to problems like: http

Re: macports and Xcode

2008-10-13 Thread rhubbell
On Sun, 2008-10-12 at 14:43 -0500, Ryan Schmidt wrote: > On Oct 12, 2008, at 14:36, rhubbell wrote: > > > On Sat, 2008-10-11 at 01:18 -0500, Ryan Schmidt wrote: > > > >> I suppose. But what would be the advantage? What's so awful about > >> having to install Xcode? > > > > My inspiration for the q

Re: macports and Xcode

2008-10-13 Thread Adam Dershowitz
On Oct 13, 2008, at 10:02 AM, rhubbell wrote: > On Sun, 2008-10-12 at 14:43 -0500, Ryan Schmidt wrote: >> On Oct 12, 2008, at 14:36, rhubbell wrote: >> >>> On Sat, 2008-10-11 at 01:18 -0500, Ryan Schmidt wrote: >>> I suppose. But what would be the advantage? What's so awful about having

Re: macports and Xcode

2008-10-13 Thread Daniel J. Luke
On Oct 13, 2008, at 1:02 PM, rhubbell wrote: My inspiration for the question was the words in the "Membership Agreement" 6. Verification of Compliance. You agree that authorized Apple representatives, with 24 hours advance notice, may inspect the location where the Prototype is stored, the

Re: php5 on OSX10.5.5

2008-10-13 Thread Ryan Schmidt
On Oct 13, 2008, at 05:01, Mark Hattam wrote: > What's broken with php5 and 10.5.5 ... ? This, unfortunately: http://trac.macports.org/ticket/15909 I'm not sure how best to resolve it. Can you help? (See note in ticket.) > I've just set up php5, mysql5 and apache2 on a brand new iMac with >

Re: php5 on OSX10.5.5

2008-10-13 Thread Mark Hattam
At 07:48 -0700 13/10/08, Chris Janton wrote: >On 2008-10-13 , at 03:01 , Mark Hattam wrote: > >>What's broken with php5 and 10.5.5 ... ? >> >>I've just set up php5, mysql5 and apache2 on a brand new iMac with >>10.5.5, and I'm getting a lot of errors in the Apache log >> >>The process has forked an

Re: macports and Xcode

2008-10-13 Thread Damien Clauzel
Le 13 oct. 08 à 19:02, rhubbell a écrit : 6. Verification of Compliance. You agree that authorized Apple representatives, with 24 hours advance notice, may inspect the location where the Prototype is stored, the Prototype and copies of other Confidential Information and your Prototype acce

Re: php5 on OSX10.5.5

2008-10-13 Thread Ryan Schmidt
On Oct 13, 2008, at 12:54, Mark Hattam wrote: > At 07:48 -0700 13/10/08, Chris Janton wrote: > >> On 2008-10-13 , at 03:01 , Mark Hattam wrote: >> >>> What's broken with php5 and 10.5.5 ... ? >>> >>> I've just set up php5, mysql5 and apache2 on a brand new iMac with >>> 10.5.5, and I'm getting a l

Port fails to install as image. Problem with cleaning the registry.

2008-10-13 Thread Darren Weber
I have a sandbox for some ports, including postgresql83-server (see attached) and I've got some issues with my installation. I'm curious about why the 'port clean --all ' doesn't remove the registry entry? Here's a terminal session where I incur an issue with the registry and my port fails to inst