Jim C. Nasby wrote:
>
> My buildfarm machine
> (http://pgbuildfarm.org/cgi-bin/show_history.pl?nm=octopus&br=HEAD)
> is SMP, so if anything we need UP testing.
My UP 4.11-STABLE box is back accessable again.
If someone wants, I can set up another buildfarm member...
LER
--
Larry Rosenman
On Tue, Jul 26, 2005 at 10:17:05PM +0200, Palle Girgensohn wrote:
> --On tisdag, juli 26, 2005 15.17.57 -0400 Tom Lane <[EMAIL PROTECTED]>
> wrote:
>
> >Larry Rosenman writes:
> >>On Jul 26 2005, Jim C. Nasby wrote:
> >>>So the question now is: how do we fix the issue with threaded python?
> >
>
--On tisdag, juli 26, 2005 15.17.57 -0400 Tom Lane <[EMAIL PROTECTED]>
wrote:
Larry Rosenman writes:
On Jul 26 2005, Jim C. Nasby wrote:
So the question now is: how do we fix the issue with threaded python?
how do we get libc_r into the mix on FreeBSD 4.11?
A possible compromise is to a
On 2005-07-26, Larry Rosenman wrote:
>> So the question now is: how do we fix the issue with threaded python?
>
> how do we get libc_r into the mix on FreeBSD 4.11?
You'd have to build the backend with -pthread.
Including -lc_r explicitly when linking stuff on freebsd will usually
cause things t
Larry Rosenman writes:
> On Jul 26 2005, Jim C. Nasby wrote:
>> So the question now is: how do we fix the issue with threaded python?
> how do we get libc_r into the mix on FreeBSD 4.11?
A possible compromise is to add -lc_r to LIBS if (a) --enable-python
and (b) platform is one of those known t
On Jul 26 2005, Jim C. Nasby wrote:
On Mon, Jul 25, 2005 at 05:02:02PM -0500, Jim C. Nasby wrote:
> > Can you try rebuilding python and it's dependencies WITHOUT_THREADS?
> >
> > I think that would get us where we need?
Worked:
http://pgbuildfarm.org/cgi-bin/show_log.pl?nm=octopus&dt=2005-07
On Mon, Jul 25, 2005 at 05:02:02PM -0500, Jim C. Nasby wrote:
> > Can you try rebuilding python and it's dependencies WITHOUT_THREADS?
> >
> > I think that would get us where we need?
Worked:
http://pgbuildfarm.org/cgi-bin/show_log.pl?nm=octopus&dt=2005-07-26%2015:29:33
So the question now is: h
On Mon, Jul 25, 2005 at 04:40:19PM -0500, Jim C. Nasby wrote:
> FWIW, AFAICT I did build the port with default options. Though, nm shows
> no symbols for my libpython(s)...
>
> [EMAIL PROTECTED]:38]~:47>nm `locate libpython|grep .so`
>
> /usr/local/lib/compat/pkg/libpython2.3.so.1:
> /usr/libexec
On Mon, Jul 25, 2005 at 05:54:45PM -0400, Larry Rosenman wrote:
> Jim C. Nasby wrote:
> > On Sun, Jul 24, 2005 at 07:38:46PM -0400, Larry Rosenman wrote:
> >> Andrew Dunstan wrote:
> >>> Larry,
> >>>
> >>> please try building and testing (especially PL installcheck) on that
> >>> box using as clos
On Mon, Jul 25, 2005 at 04:03:58PM -0600, Michael Fuhr wrote:
> On Mon, Jul 25, 2005 at 04:40:19PM -0500, Jim C. Nasby wrote:
> > FWIW, AFAICT I did build the port with default options. Though, nm shows
> > no symbols for my libpython(s)...
> >
> > [EMAIL PROTECTED]:38]~:47>nm `locate libpython|gr
On Sun, Jul 24, 2005 at 07:38:46PM -0400, Larry Rosenman wrote:
> Andrew Dunstan wrote:
> > Larry,
> >
> > please try building and testing (especially PL installcheck) on that
> > box using as close as possible to the same config setup as octopus:
> >
> >
> http://www.pgbuildfarm.org/cgi-bin/sho
Jim C. Nasby wrote:
> On Sun, Jul 24, 2005 at 07:38:46PM -0400, Larry Rosenman wrote:
>> Andrew Dunstan wrote:
>>> Larry,
>>>
>>> please try building and testing (especially PL installcheck) on that
>>> box using as close as possible to the same config setup as octopus:
>>>
>>>
>> http://www.pgb
On Sun, Jul 24, 2005 at 06:01:46PM -0600, Michael Fuhr wrote:
> On Sun, Jul 24, 2005 at 06:40:35PM -0400, Tom Lane wrote:
> > I think someone mentioned this already, but it'd be a good idea to
> > compare the python situation to plperl. On my Linux box, libperl.so
> > shows several references to p
On Sun, Jul 24, 2005 at 06:40:35PM -0400, Tom Lane wrote:
> I think someone mentioned this already, but it'd be a good idea to
> compare the python situation to plperl. On my Linux box, libperl.so
> shows several references to pthread_xxx symbols ... not the same ones
> libpython.so depends on, bu
Andrew Dunstan wrote:
> Larry,
>
> please try building and testing (especially PL installcheck) on that
> box using as close as possible to the same config setup as octopus:
>
>
http://www.pgbuildfarm.org/cgi-bin/show_log.pl?nm=octopus&dt=2005-07-24%2008
:05:01
>
> thanks
>
> andrew
It appear
Larry Rosenman wrote:
Tom Lane wrote:
Andrew Dunstan <[EMAIL PROTECTED]> writes:
We don't seem to have made any progress on this. Is there someone
else who has a machine with these specs that they can test this for
us?
FreeBSD 4.11-RELEASE-p10
gcc 2.95.4
x86 SMP
I th
Tom Lane wrote:
> Andrew Dunstan <[EMAIL PROTECTED]> writes:
>> We don't seem to have made any progress on this. Is there someone
>> else who has a machine with these specs that they can test this for
>> us?
>
>> FreeBSD 4.11-RELEASE-p10
>> gcc 2.95.4
>> x86 SMP
>
> I think someone mentioned thi
Andrew Dunstan <[EMAIL PROTECTED]> writes:
> We don't seem to have made any progress on this. Is there someone else
> who has a machine with these specs that they can test this for us?
> FreeBSD 4.11-RELEASE-p10
> gcc 2.95.4
> x86 SMP
I think someone mentioned this already, but it'd be a good id
We don't seem to have made any progress on this. Is there someone else
who has a machine with these specs that they can test this for us?
FreeBSD 4.11-RELEASE-p10
gcc 2.95.4
x86 SMP
cheers
andrew
Jim C. Nasby wrote:
On Tue, Jul 19, 2005 at 03:53:26PM -0400, Andrew Dunstan wrote:
Do y
--On tisdag, juli 19, 2005 15.11.31 -0400 Tom Lane <[EMAIL PROTECTED]>
wrote:
"Jim C. Nasby" <[EMAIL PROTECTED]> writes:
http://archives.postgresql.org/pgsql-bugs/2005-07/msg00096.php describes
what I think is causing octopus to fail. What's also interesting is
these patches from the FreeBSD
On Tue, Jul 19, 2005 at 03:53:26PM -0400, Andrew Dunstan wrote:
> Do you have any other libpython*.so files on your system?
[EMAIL PROTECTED]:56]~:2>locate libpython
/usr/local/lib/compat/pkg/libpython2.3.so.1
/usr/local/lib/libpython2.4.so
/usr/local/lib/libpython2.4.so.1
/usr/local/lib/python2.4/
Tom Lane wrote:
"Jim C. Nasby" <[EMAIL PROTECTED]> writes:
On Tue, Jul 19, 2005 at 03:11:31PM -0400, Tom Lane wrote:
None of those patches are necessary; if they were, we'd be seeing the
failures at the build stage, not at runtime.
Anyone have any ideas on why octopus is
On Tue, Jul 19, 2005 at 03:47:48PM -0400, Tom Lane wrote:
> "Jim C. Nasby" <[EMAIL PROTECTED]> writes:
> > On Tue, Jul 19, 2005 at 03:11:31PM -0400, Tom Lane wrote:
> >> None of those patches are necessary; if they were, we'd be seeing the
> >> failures at the build stage, not at runtime.
>
> > An
Jim C. Nasby wrote:
On Tue, Jul 19, 2005 at 03:11:31PM -0400, Tom Lane wrote:
"Jim C. Nasby" <[EMAIL PROTECTED]> writes:
http://archives.postgresql.org/pgsql-bugs/2005-07/msg00096.php describes
what I think is causing octopus to fail. What's also interesting is
these patches from the
"Jim C. Nasby" <[EMAIL PROTECTED]> writes:
> On Tue, Jul 19, 2005 at 03:11:31PM -0400, Tom Lane wrote:
>> None of those patches are necessary; if they were, we'd be seeing the
>> failures at the build stage, not at runtime.
> Anyone have any ideas on why octopus is failing then?
Well, the origina
On Tue, Jul 19, 2005 at 03:11:31PM -0400, Tom Lane wrote:
> "Jim C. Nasby" <[EMAIL PROTECTED]> writes:
> > http://archives.postgresql.org/pgsql-bugs/2005-07/msg00096.php describes
> > what I think is causing octopus to fail. What's also interesting is
> > these patches from the FreeBSD port:
>
> N
"Jim C. Nasby" <[EMAIL PROTECTED]> writes:
> http://archives.postgresql.org/pgsql-bugs/2005-07/msg00096.php describes
> what I think is causing octopus to fail. What's also interesting is
> these patches from the FreeBSD port:
None of those patches are necessary; if they were, we'd be seeing the
f
http://archives.postgresql.org/pgsql-bugs/2005-07/msg00096.php describes
what I think is causing octopus to fail. What's also interesting is
these patches from the FreeBSD port:
[EMAIL PROTECTED]:48]/usr/ports/databases/postgresql80-server/files:37>cat
patch-plpython-Makefile patch-src-makefiles-
28 matches
Mail list logo
