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 ler@lerctr.org writes:
On Jul 26 2005, Jim C. Nasby wrote:
So the question now is: how do we fix the issue with threaded python?
Jim C. Nasby wrote:
My buildfarm machine
(http://pgbuildfarm.org/cgi-bin/show_history.pl?nm=octopusbr=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 tisdag, juli 26, 2005 15.17.57 -0400 Tom Lane [EMAIL PROTECTED]
wrote:
Larry Rosenman ler@lerctr.org 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
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=octopusdt=2005-07-26%2015:29:33
So the question now is: how do
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:
Larry Rosenman ler@lerctr.org 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
On 2005-07-26, Larry Rosenman ler@lerctr.org 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
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
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:
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:
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]~:47nm `locate libpython|grep .so`
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 close as possible to the
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]~:47nm `locate libpython|grep .so`
/usr/local/lib/compat/pkg/libpython2.3.so.1:
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
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 idea to
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 this already, but
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
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=octopusdt=2005-07-24%2008
:05:01
thanks
andrew
It appears that the
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, but
--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
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:37cat
patch-plpython-Makefile
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
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:
None of those
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 original report
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
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.
Anyone have any
26 matches
Mail list logo
