Re: pgsql: Move interpreter shared library detection to configure
От | Michael Paquier |
---|---|
Тема | Re: pgsql: Move interpreter shared library detection to configure |
Дата | |
Msg-id | CAB7nPqTBh4YFGFqhfvpc+LHkXrN2qUg+0CaJS4Hr6JjvtW-OfQ@mail.gmail.com обсуждение исходный текст |
Ответ на | pgsql: Move interpreter shared library detection to configure (Peter Eisentraut <peter_e@gmx.net>) |
Ответы |
Re: pgsql: Move interpreter shared library detection
to configure
|
Список | pgsql-committers |
On Sat, May 2, 2015 at 10:39 AM, Peter Eisentraut <peter_e@gmx.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
В списке pgsql-committers по дате отправления: