From: | Michael Paquier <michael(dot)paquier(at)gmail(dot)com> |
---|---|
To: | Peter Eisentraut <peter_e(at)gmx(dot)net> |
Cc: | pgsql-committers(at)postgresql(dot)org |
Subject: | Re: pgsql: Move interpreter shared library detection to configure |
Date: | 2015-05-02 02:22:14 |
Message-ID: | CAB7nPqTBh4YFGFqhfvpc+LHkXrN2qUg+0CaJS4Hr6JjvtW-OfQ@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-committers |
On Sat, May 2, 2015 at 10:39 AM, Peter Eisentraut <peter_e(at)gmx(dot)net> wrote:
> Move interpreter shared library detection to configure
>
> For building PL/Perl, PL/Python, and PL/Tcl, we need a shared library of
> libperl, libpython, and libtcl, respectively. Previously, this was
> checked in the makefiles, skipping the PL build with a warning if no
> shared library was available. Now this is checked in configure, with an
> error if no shared library is available.
>
> The previous situation arose because in the olden days, the configure
> options --with-perl, --with-python, and --with-tcl controlled whether
> frontend interfaces for those languages would be built. The procedural
> languages were added later, and shared libraries were often not
> available in the beginning. So it was decided skip the builds of the
> procedural languages in those cases. The frontend interfaces have since
> been removed from the tree, and shared libraries are now available most
> of the time, so that setup makes much less sense now.
>
> Also, the new setup allows contrib modules and pgxs users to rely on the
> respective PLs being available based on configure flags.
This is hurting OSX platforms at least older than 10.6 (I can get
configure working on my 10.8 laptop), and OpenBSD.
--
Michael
From | Date | Subject | |
---|---|---|---|
Next Message | Peter Eisentraut | 2015-05-02 03:14:40 | pgsql: Fix shared libpython detection on OS X |
Previous Message | Peter Eisentraut | 2015-05-02 02:20:45 | pgsql: Make hstore_plperl's build even more like plperl's |