[MacPorts] #16340: PHP throwing fork()ing error

[MacPorts]

#16340: PHP throwing fork()ing error
-----------------------------------+----------------------------------------
  Reporter:  cabanela at mnstate.edu  |       Owner:  macports-tickets at lists.macosforge.org
      Type:  defect                |      Status:  new                                  
  Priority:  Normal                |   Milestone:                                       
 Component:  ports                 |     Version:  1.6.0                                
Resolution:                        |    Keywords:                                       
-----------------------------------+----------------------------------------
Comment (by cabanela at mnstate.edu):

 As I just noted on my blog:

 I've continued investigating and in Apple's Discussion boards I found
 there was a string of comments about this problem
 (--http://discussions.apple.com/thread.jspa?messageID=5693097#5961098--) .
 One user, Bill Eccles, seemed to isolate the problem and his description
 matches the symptoms I am seeing:

     Finally, there's a big problem with FreeType. As I discovered, anytime
 FreeType fonts are used by GD, they apparently make a Carbon API call of
 some sort. Problem is, Apache2 uses fork() without a corresponding exec()
 and, upon calling PHP/GD/FreeType, the Carbon call in FreeType causes
 Apache2 to crash. It shows up in the error_log as

     The process has forked and you cannot use this CoreFoundation
 functionality safely. You MUST exec().
     Break on
 __THE_PROCESS_HAS_FORKED_AND_YOU_CANNOT_USE_THIS_COREFOUNDATION_FUNCTIONALITY___YOU_MUST_EXEC__()
 to debug.
     Mon Nov 26 12:38:11 2007 notice child pid 304 exit signal Trace/BPT
 trap (5)

     and in the system.log as

     Nov 26 13:12:00 shr-g5 ReportCrash664: Formulating crash report for
 process httpd659
     Nov 26 13:12:02 shr-g5 ReportCrash664: Saved crashreport to
 /Library/Logs/CrashReporter/httpd_2007-11-26-131145_shr-g5.crash using
 uid: 0 gid: 0, euid: 0 egid: 0

     I didn't discover the cause--I can't take credit for this one. Here's
 where I discovered the FreeType/Apache2 problem:

     http://spteam-lists.blogspot.com/2007/11/freetype-digest-
 vol-35-issue-1.html

 The followup comment suggests a solution by compiling a replacement to
 Apple's built-in Freetype to version 2.3.5.  Funny thing is I have
 MacPorts Freetype 2.3.7 installed.  Any ideas?

-- 
Ticket URL: <http://trac.macports.org/ticket/16340#comment:2>
MacPorts <http://www.macports.org/>
Ports system for Mac OS