| From: | "Jim C(dot) Nasby" <jim(at)nasby(dot)net> |
|---|---|
| To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
| Cc: | Peter Eisentraut <peter_e(at)gmx(dot)net>, pgsql-hackers(at)postgresql(dot)org |
| Subject: | Re: Threaded python on FreeBSD |
| Date: | 2006-10-16 03:27:54 |
| Message-ID: | 20061016032754.GG381@nasby.net |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On Sun, Oct 15, 2006 at 06:19:12PM -0400, Tom Lane wrote:
> "Jim C. Nasby" <jim(at)nasby(dot)net> writes:
> > Take a look at the failure output...
>
> > ERROR: could not load library
> > "/home/buildfarm/buildfarm/HEAD/inst/lib/postgresql/plpython.so": dlopen
> > (/home/buildfarm/buildfarm/HEAD/inst/lib/postgresql/plpython.so) failed:
> > /usr/local/lib/python2.5/config/libpython2.5.so: Undefined symbol
> > "pthread_attr_destroy"
>
> I suspect the problem here is that the backend isn't linked with
> -lpthread. We aren't going to let libpython dictate whether we do so,
> either...
Isn't that what --enable-thread-safety does? I know I've made at least
one test with that enabled (though it may not be the failure I linked
up-thread).
--
Jim Nasby jim(at)nasby(dot)net
EnterpriseDB http://enterprisedb.com 512.569.9461 (cell)
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Jeremy Drake | 2006-10-16 03:36:25 | Re: constraints in query plans |
| Previous Message | Tom Lane | 2006-10-16 03:20:38 | Re: constraints in query plans |