➜

This issue tracker has been migrated to GitHub, and is currently read-only.
For more information, see the GitHub FAQs in the Python's Developer Guide.

Author koobs
Recipients Alex.Willmer, koobs, stefanrink@yahoo.com, vstinner, zach.ware
Date 2018-10-15.06:21:12
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1539584472.6.0.788709270274.issue34957@psf.upfronthosting.co.za>
In-reply-to
Content 
All our FreeBSD ports (lang/python??) and the packages produced from them all contain a LIBFFI option which is enabled by default, since 2015 [1][2]:

LIBFFI=on: Use libffi from ports instead of bundled version

This means that any 'default' package builds of these ports, including those in the official package repositories, will install and build again st the port/package version of libffi, and not the bundled version.

This was originally due to broken builds on i386 (see #22521 and issue23042), but also to due library policy (use external/upstream, not bundled libraries), and not wanting to use outdated/stale version any longer.

[1] python27: https://svnweb.freebsd.org/changeset/ports/377581
[2] python34+: https://svnweb.freebsd.org/changeset/ports/378821
History
Date User Action Args
2018-10-15 06:21:12koobssetrecipients: + koobs, vstinner, zach.ware, Alex.Willmer, stefanrink@yahoo.com
2018-10-15 06:21:12koobssetmessageid: <1539584472.6.0.788709270274.issue34957@psf.upfronthosting.co.za>
2018-10-15 06:21:12koobslinkissue34957 messages
2018-10-15 06:21:12koobscreate