FreeType crasher: how to recompile ?

Yann Corno yann+macports at
Thu Aug 21 00:21:58 PDT 2008

Dear MacPorts people:

Following up on this, I finally found the solution. Maybe I was not 
recompiling properly FreeType, or maybe the little additional changes I 
made in the configure.args options made it work. Anyway, it works, so I 
am not going to touch it again ;-)

Here is the procedure:

* Uninstall Freetype:

sudo port uninstall -f freetype     # The -f option will force the 
un-install despite other packages dependencies

* Edit the portfile:

sudo port edit freetype
# In the editor, change the configure.args option like this:
configure.args \
     --with-old-mac-fonts=no \
     --with-quickdraw-toolbox=no --with-quickdraw-carbon=no

* Save the portfile, then re-install Freetype:

sudo port install freetype

If you have any comments, I'll be happy to hear them :-)

Thanks for your attention,


> Hello everyone:
> I am suffering from a crasher recently introduced in FreeType (or so it
> seems). After a wild goose chase from Apache to PHP to GD2 to FreeType,
> it boils down to a crash because Apache2 uses fork() without a
> corresponding exec() and, upon calling PHP/GD/FreeType, the Carbon call
> in FreeType causes Apache2 to crash. This is what is explained here:
> The next comment in the above link explains that FreeType should be
> recompiled with a couple of options off: with-quickdraw-carbon and
> with-quickdraw-toolbox
> My question is: how do I do this in MacPort?
> I tried to change the portfile like this:
> configure.args \
>     --with-old-mac-fonts \
>     --with-fsspec=no --with-fsref=no --with-quickdraw-toolbox=no
> --with-quickdraw-carbon=no
> But it does not seem to make any difference. Heck, I am not even sure
> that these options carry through down to the compiler. Sorry, I am such
> a MacPort newbee...
> Any advise on what I should do? Should I also rebuild gd2 and php5 after
> that?
> Thanks in advance for your insights,
> Yann
> PS: I am using Mac OS X 10.5.4 on a PowerPC G4 PowerBook machine, and
> updated to the latest MacPorts builds.

More information about the macports-dev mailing list