The correct way to do what he wants to do is configure PYTHON=/usr/local/bin/python3.1 ... other options ...
On lör, 2010-09-11 at 17:22 -0700, Josh Berkus wrote: > I discussed this report with James Pye already, and he beleives it's a > configure script bug which should be fixed before release. Anyone > capable of taking it on? > > -------- Original Message -------- > Subject: [TESTERS] Configure/Build 9.0 rc1 - cannot build against > python3.1, with two versions of python in the environment > Date: Sat, 11 Sep 2010 13:12:13 -0400 > From: Lou Picciano <loupicci...@comcast.net> > To: pgsql-test...@postgresql.org > > > > *[TEST REPORT]* > *[Release]:* 9.0 RC1 > *[Test Type]:* Install (Build) > *[Test]:* Configure/Build 9.0 rc1 - cannot build against python3.1, with > two versions of python in the environment > *[Platform]:* Solaris 10 Sparc E450 Quad > *[Parameters]:* > --with-python \ > * > --with-includes=/usr/local/include/python3.1:/usr/local/include:/usr/local/ssl/include > > > \ > --with-libraries=/usr/local/lib/python3.1:/usr/local/lib:/usr/local/ssl/lib > \ > CONFIGURE OUTPUT: ----------------------------------------- > checking for python... /usr/bin/python > checking Python configuration directory... /usr/lib/python2.4/config > checking how to link an embedded Python application... -L/usr/lib > -lpython2.4 -lresolv -lsocket -lnsl -lrt -ldl -lm > configure: using CPPFLAGS= -I/usr/local/include/libxml2 > -I/usr/local/include/python3.1 -I/usr/local/include -I/usr/local/ssl/include > configure: using LDFLAGS= -L/usr/local/lib -L/usr/local/lib/python3.1 > [Failure]:* Can't seem to definitively config PG to a specific version > of python - v3.1, at /usr/local/bin/python3 > *[Results]:* configure seems to pick up python 2.4 configuration, but > apparently links to (desired) python 3.1 libs. > # ldd plpython2.so > libpython2.4.so.1.0 => /usr/lib/libpython2.4.so.1.0 > *[Comments]:* Tried first to see if configure picks up the PYTHONPATH > env variable to find python's configuration. No joy. Using this variable > might be a reasonable approach for configure? > -- Sent via pgsql-bugs mailing list (pgsql-bugs@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-bugs
