Is libffi obsolete?

Ronald Oussoren ronaldoussoren at
Thu Sep 21 01:15:04 PDT 2006

On Thursday, September 21, 2006, at 09:45AM, Mark Duling <mark.duling at> wrote:

>>The file the port tries to download isn't the maintained copy of  
>>libffi. I've fully integrated the libffi build into the PyObjC build  
>>and we no longer distribute a current standalone copy of libffi.
>>gcc also provides its own and I see this port more like a potential  
>>source of troubles than anything else.
>So am I hearing "this port is broke and will never work and should be
>deleted"?  Or is it more a "wait and see and let it hang around for awhile
>more" type of thing.  I hate to have ports in the tree that will never
>work because it causes confusion and bugs to be filed.

A port that works from the copy of libffi that is distributed by the PyObjC project is less than optimal. That version does not, and will never, support darwin/x86.  That's nothing that can't be fixed through patches of course ;-)


More information about the macports-dev mailing list