Aidan Van Dyk writes:
> https://packages.debian.org/jessie/amd64/libpython3.4/filelist
> The ".so." is in /usr/lib/, but ".so" symlink is in the
> config directory...
Hah. I guess that explains why they are setting LIBDIR to /usr/lib.
Thanks for the info!
regards, tom la
Robert Haas writes:
> On Tue, Oct 4, 2016 at 3:38 PM, Tom Lane wrote:
>> So I pushed that, and most of the Debian-based buildfarm critters
>> don't like it. Where does Debian keep the python shlib, pray tell?
> ...must...not...say...I...told...you...so...
Meh. How about you don't say it, unti
On Tue, Oct 4, 2016 at 3:38 PM, Tom Lane wrote:
> Robert Haas writes:
>> On Tue, Oct 4, 2016 at 12:57 PM, Tom Lane wrote:
>>> Sure, but it will only matter given a more-or-less-broken Python
>>> installation. Anyway, if you have a better idea, let's hear it.
>
>> Sorry, no clue
>
> So I pus
Robert Haas writes:
> On Tue, Oct 4, 2016 at 12:57 PM, Tom Lane wrote:
>> Sure, but it will only matter given a more-or-less-broken Python
>> installation. Anyway, if you have a better idea, let's hear it.
> Sorry, no clue
So I pushed that, and most of the Debian-based buildfarm critters
d
On Tue, Oct 4, 2016 at 12:57 PM, Tom Lane wrote:
> Robert Haas writes:
>> On Tue, Oct 4, 2016 at 11:45 AM, Tom Lane wrote:
>>> "$python_libdir /usr/lib64 /usr/lib" (too bad there's no easy
>>> platform-independent way to find out the linker's default search path).
>
>> "too bad" sounds like a gr
Robert Haas writes:
> On Tue, Oct 4, 2016 at 11:45 AM, Tom Lane wrote:
>> "$python_libdir /usr/lib64 /usr/lib" (too bad there's no easy
>> platform-independent way to find out the linker's default search path).
> "too bad" sounds like a grave understatement of the perils involved
> using a fixed
On Tue, Oct 4, 2016 at 11:45 AM, Tom Lane wrote:
> "$python_libdir /usr/lib64 /usr/lib" (too bad there's no easy
> platform-independent way to find out the linker's default search path).
"too bad" sounds like a grave understatement of the perils involved
using a fixed list of paths which may or m
Andrew Dunstan writes:
> On 10/04/2016 10:43 AM, Tom Lane wrote:
>> In short: I propose replacing all of this logic with "if there's something
>> in $python_libdir that has the right name to be a python shared library,
>> use that, else try the same in $python_configdir, else fail". Thoughts?
>
On 10/04/2016 10:43 AM, Tom Lane wrote:
While chasing down last night's failure on buildfarm member longfin,
I came across an interesting factoid. If you just do
./configure --enable-shared
make
make install
in unmodified Python sources, what you will get is an instal
While chasing down last night's failure on buildfarm member longfin,
I came across an interesting factoid. If you just do
./configure --enable-shared
make
make install
in unmodified Python sources, what you will get is an install tree in
which libpython.so (or local equiv
10 matches
Mail list logo
