Re: Python3.4 detection on 9.6 configuration

----- Original Message -----

> From: "Tom Lane" <tgl(at)sss(dot)pgh(dot)pa(dot)us>
> To: "Lou Picciano" <loupicciano(at)comcast(dot)net>
> Cc: pgsql-hackers(at)postgresql(dot)org
> Sent: Wednesday, September 28, 2016 9:33:06 AM
> Subject: Re: [HACKERS] Python3.4 detection on 9.6 configuration

> Lou Picciano <loupicciano(at)comcast(dot)net> writes:
> > Trying to build 9.6RC1, with Python3.4, on OpenIndiana (Illumos). It
> > seems the detection of shared library status of the .so has changed.

Specifically, configure is not finding the .so. It's not that the so isn't built 'shared'; it is.

> Changed from what? I don't recall that we've touched that code in quite
> some time. What was the last version that worked for you? What
> exactly is failing?

Core bit seems to be the python3.4-config behavior:

/usr/bin/python3.4-config --extension-suffix

.cpython-34m.so
I don't know if this is designed behavior for Python3.4 - or if it's a bug there? I'm working this with the Python gang as well.

Of course, this option doesn't exist under Python2.7.

> I'm having a hard time following your not-really-a-patch, but it looks
> like you're proposing forcing python_enable_shared=1 on Solaris,

Certainly not! I was simply offering this as evidence that PostgreSQL will build just fine, against Python3.4, using this hack. (It's useful in getting us a working build in situ o continue other testing - even before the more elegant fix - whatever that turns out to be!)

> which sounds like a pretty bad idea. AFAIK the shared-ness of libpython is
> up to whoever built it.

Indeed. As I mentioned, our Python3.4 is built shared.

> regards, tom lane