Is libffi obsolete?

Mark Duling mark.duling at
Thu Sep 21 00:45:07 PDT 2006

>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.


More information about the macports-dev mailing list