pg.ddx.io pgsql-committers@postgresql.org mailing list archivehelp / color / mirror / Atom feed
pgsql: On OS X, link libpython normally, ignoring the "framework" frame 6+ messages / 1 participants [nested] [flat]
* pgsql: On OS X, link libpython normally, ignoring the "framework" frame @ 2014-05-30 22:19 Tom Lane <tgl@sss.pgh.pa.us> 0 siblings, 0 replies; 6+ messages in thread From: Tom Lane @ 2014-05-30 22:19 UTC (permalink / raw) To: pgsql-committers On OS X, link libpython normally, ignoring the "framework" framework. As of Xcode 5.0, Apple isn't including the Python framework as part of the SDK-level files, which means that linking to it might fail depending on whether Xcode thinks you've selected a specific SDK version. According to their Tech Note 2328, they've basically deprecated the framework method of linking to libpython and are telling people to link to the shared library normally. (I'm pretty sure this is in direct contradiction to the advice they were giving a few years ago, but whatever.) Testing says that this approach works fine at least as far back as OS X 10.4.11, so let's just rip out the framework special case entirely. We do still need a special case to decide that OS X provides a shared library at all, unfortunately (I wonder why the distutils check doesn't work ...). But this is still less of a special case than before, so it's fine. Back-patch to all supported branches, since we'll doubtless be hearing about this more as more people update to recent Xcode. Branch ------ REL9_1_STABLE Details ------- http://git.postgresql.org/pg/commitdiff/a784a39c49cbecf4b69324db96ce6bd119e967e8 Modified Files -------------- src/pl/plpython/Makefile | 4 +--- 1 file changed, 1 insertion(+), 3 deletions(-) -- Sent via pgsql-committers mailing list (pgsql-committers@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-committers ^ permalink raw reply [nested|flat] 6+ messages in thread
* pgsql: On OS X, link libpython normally, ignoring the "framework" frame @ 2014-05-30 22:19 Tom Lane <tgl@sss.pgh.pa.us> 0 siblings, 0 replies; 6+ messages in thread From: Tom Lane @ 2014-05-30 22:19 UTC (permalink / raw) To: pgsql-committers On OS X, link libpython normally, ignoring the "framework" framework. As of Xcode 5.0, Apple isn't including the Python framework as part of the SDK-level files, which means that linking to it might fail depending on whether Xcode thinks you've selected a specific SDK version. According to their Tech Note 2328, they've basically deprecated the framework method of linking to libpython and are telling people to link to the shared library normally. (I'm pretty sure this is in direct contradiction to the advice they were giving a few years ago, but whatever.) Testing says that this approach works fine at least as far back as OS X 10.4.11, so let's just rip out the framework special case entirely. We do still need a special case to decide that OS X provides a shared library at all, unfortunately (I wonder why the distutils check doesn't work ...). But this is still less of a special case than before, so it's fine. Back-patch to all supported branches, since we'll doubtless be hearing about this more as more people update to recent Xcode. Branch ------ REL9_2_STABLE Details ------- http://git.postgresql.org/pg/commitdiff/83ed4598b251f05f01fb7ea1d562b2a96830d738 Modified Files -------------- src/pl/plpython/Makefile | 4 +--- 1 file changed, 1 insertion(+), 3 deletions(-) -- Sent via pgsql-committers mailing list (pgsql-committers@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-committers ^ permalink raw reply [nested|flat] 6+ messages in thread
* pgsql: On OS X, link libpython normally, ignoring the "framework" frame @ 2014-05-30 22:19 Tom Lane <tgl@sss.pgh.pa.us> 0 siblings, 0 replies; 6+ messages in thread From: Tom Lane @ 2014-05-30 22:19 UTC (permalink / raw) To: pgsql-committers On OS X, link libpython normally, ignoring the "framework" framework. As of Xcode 5.0, Apple isn't including the Python framework as part of the SDK-level files, which means that linking to it might fail depending on whether Xcode thinks you've selected a specific SDK version. According to their Tech Note 2328, they've basically deprecated the framework method of linking to libpython and are telling people to link to the shared library normally. (I'm pretty sure this is in direct contradiction to the advice they were giving a few years ago, but whatever.) Testing says that this approach works fine at least as far back as OS X 10.4.11, so let's just rip out the framework special case entirely. We do still need a special case to decide that OS X provides a shared library at all, unfortunately (I wonder why the distutils check doesn't work ...). But this is still less of a special case than before, so it's fine. Back-patch to all supported branches, since we'll doubtless be hearing about this more as more people update to recent Xcode. Branch ------ REL9_0_STABLE Details ------- http://git.postgresql.org/pg/commitdiff/4f725bbc4e6938b4c8ce960d59791f4675f4a3d1 Modified Files -------------- src/pl/plpython/Makefile | 4 +--- 1 file changed, 1 insertion(+), 3 deletions(-) -- Sent via pgsql-committers mailing list (pgsql-committers@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-committers ^ permalink raw reply [nested|flat] 6+ messages in thread
* pgsql: On OS X, link libpython normally, ignoring the "framework" frame @ 2014-05-30 22:19 Tom Lane <tgl@sss.pgh.pa.us> 0 siblings, 0 replies; 6+ messages in thread From: Tom Lane @ 2014-05-30 22:19 UTC (permalink / raw) To: pgsql-committers On OS X, link libpython normally, ignoring the "framework" framework. As of Xcode 5.0, Apple isn't including the Python framework as part of the SDK-level files, which means that linking to it might fail depending on whether Xcode thinks you've selected a specific SDK version. According to their Tech Note 2328, they've basically deprecated the framework method of linking to libpython and are telling people to link to the shared library normally. (I'm pretty sure this is in direct contradiction to the advice they were giving a few years ago, but whatever.) Testing says that this approach works fine at least as far back as OS X 10.4.11, so let's just rip out the framework special case entirely. We do still need a special case to decide that OS X provides a shared library at all, unfortunately (I wonder why the distutils check doesn't work ...). But this is still less of a special case than before, so it's fine. Back-patch to all supported branches, since we'll doubtless be hearing about this more as more people update to recent Xcode. Branch ------ master Details ------- http://git.postgresql.org/pg/commitdiff/20561acf93d32b7d7fdd59d054344b2e341d6aa0 Modified Files -------------- config/python.m4 | 11 ++--------- configure | 11 ++--------- src/pl/plpython/Makefile | 9 ++++++--- 3 files changed, 10 insertions(+), 21 deletions(-) -- Sent via pgsql-committers mailing list (pgsql-committers@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-committers ^ permalink raw reply [nested|flat] 6+ messages in thread
* pgsql: On OS X, link libpython normally, ignoring the "framework" frame @ 2014-05-30 22:19 Tom Lane <tgl@sss.pgh.pa.us> 0 siblings, 0 replies; 6+ messages in thread From: Tom Lane @ 2014-05-30 22:19 UTC (permalink / raw) To: pgsql-committers On OS X, link libpython normally, ignoring the "framework" framework. As of Xcode 5.0, Apple isn't including the Python framework as part of the SDK-level files, which means that linking to it might fail depending on whether Xcode thinks you've selected a specific SDK version. According to their Tech Note 2328, they've basically deprecated the framework method of linking to libpython and are telling people to link to the shared library normally. (I'm pretty sure this is in direct contradiction to the advice they were giving a few years ago, but whatever.) Testing says that this approach works fine at least as far back as OS X 10.4.11, so let's just rip out the framework special case entirely. We do still need a special case to decide that OS X provides a shared library at all, unfortunately (I wonder why the distutils check doesn't work ...). But this is still less of a special case than before, so it's fine. Back-patch to all supported branches, since we'll doubtless be hearing about this more as more people update to recent Xcode. Branch ------ REL8_4_STABLE Details ------- http://git.postgresql.org/pg/commitdiff/ae41bb4befa4eaa4207f2bacbdce5d7ebfae4d8f Modified Files -------------- src/pl/plpython/Makefile | 4 +--- 1 file changed, 1 insertion(+), 3 deletions(-) -- Sent via pgsql-committers mailing list (pgsql-committers@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-committers ^ permalink raw reply [nested|flat] 6+ messages in thread
* pgsql: On OS X, link libpython normally, ignoring the "framework" frame @ 2014-05-30 22:19 Tom Lane <tgl@sss.pgh.pa.us> 0 siblings, 0 replies; 6+ messages in thread From: Tom Lane @ 2014-05-30 22:19 UTC (permalink / raw) To: pgsql-committers On OS X, link libpython normally, ignoring the "framework" framework. As of Xcode 5.0, Apple isn't including the Python framework as part of the SDK-level files, which means that linking to it might fail depending on whether Xcode thinks you've selected a specific SDK version. According to their Tech Note 2328, they've basically deprecated the framework method of linking to libpython and are telling people to link to the shared library normally. (I'm pretty sure this is in direct contradiction to the advice they were giving a few years ago, but whatever.) Testing says that this approach works fine at least as far back as OS X 10.4.11, so let's just rip out the framework special case entirely. We do still need a special case to decide that OS X provides a shared library at all, unfortunately (I wonder why the distutils check doesn't work ...). But this is still less of a special case than before, so it's fine. Back-patch to all supported branches, since we'll doubtless be hearing about this more as more people update to recent Xcode. Branch ------ REL9_3_STABLE Details ------- http://git.postgresql.org/pg/commitdiff/4f5f4da79ee805681f1f23a107bc905d647f12bc Modified Files -------------- config/python.m4 | 11 ++--------- configure | 11 ++--------- src/pl/plpython/Makefile | 9 ++++++--- 3 files changed, 10 insertions(+), 21 deletions(-) -- Sent via pgsql-committers mailing list (pgsql-committers@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-committers ^ permalink raw reply [nested|flat] 6+ messages in thread
end of thread, other threads:[~2014-05-30 22:19 UTC | newest] Thread overview: 6+ messages (download: mbox mbox.gz follow: Atom feed) -- links below jump to the message on this page -- 2014-05-30 22:19 pgsql: On OS X, link libpython normally, ignoring the "framework" frame Tom Lane <tgl@sss.pgh.pa.us> 2014-05-30 22:19 pgsql: On OS X, link libpython normally, ignoring the "framework" frame Tom Lane <tgl@sss.pgh.pa.us> 2014-05-30 22:19 pgsql: On OS X, link libpython normally, ignoring the "framework" frame Tom Lane <tgl@sss.pgh.pa.us> 2014-05-30 22:19 pgsql: On OS X, link libpython normally, ignoring the "framework" frame Tom Lane <tgl@sss.pgh.pa.us> 2014-05-30 22:19 pgsql: On OS X, link libpython normally, ignoring the "framework" frame Tom Lane <tgl@sss.pgh.pa.us> 2014-05-30 22:19 pgsql: On OS X, link libpython normally, ignoring the "framework" frame Tom Lane <tgl@sss.pgh.pa.us>
This inbox is served by DDX for PostgreSQL; see mirroring instructions for how to clone and mirror all data and code used for this inbox