From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
---|---|
To: | Matt <bsg075(at)gmail(dot)com> |
Cc: | pgsql-novice(at)postgresql(dot)org, pgsql-hackers(at)postgresql(dot)org |
Subject: | Re: Python verison for build in config.pl (Win32) |
Date: | 2010-01-20 17:59:31 |
Message-ID: | 15740.1264010371@sss.pgh.pa.us |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers pgsql-novice |
Matt <bsg075(at)gmail(dot)com> writes:
> Attempting to build 8.5 alpha on Windows XP (MSVC 2005) with Python support.
> Path to local interpreter added to config.pl (C:\Python), but message is
> presented:
> "Could not determine python version from path at build.pl line 38"
> Do the build scripts attempt to determine the Python version from the path
> name? Since my machine has a generic path name, is there a way to specify
> the interpreter version?
Hm, I see this in Mkvcbuild.pm:
$solution->{options}->{python} =~ /\\Python(\d{2})/i
|| croak "Could not determine python version from path";
$plpython->AddLibrary($solution->{options}->{python} . "\\Libs\\python$1.lib");
Apparently you need to hack that to deduce the appropriate library
pathname. What exactly is your python path name, and is it a standard
installation pattern at all?
regards, tom lane
From | Date | Subject | |
---|---|---|---|
Next Message | Heikki Linnakangas | 2010-01-20 18:00:33 | Synchronization primitives (Was: Re: An example of bugs for Hot Standby) |
Previous Message | Leonardo F | 2010-01-20 17:48:00 | Re: About "Our CLUSTER implementation is pessimal" patch |
From | Date | Subject | |
---|---|---|---|
Next Message | Tom Lane | 2010-01-20 18:13:22 | Re: UUID - 8.4.2 |
Previous Message | Morris, Roy | 2010-01-20 17:49:39 | UUID - 8.4.2 |