|
Home > Archive > Slony1 PostgreSQL Replication > January 2006 > Re: Thread test program failed. Your platform is
You are viewing an archived Text-only version of the thread.
To view this thread in it's original format and/or if you want to reply to
this thread please [click here]
| Author |
Re: Thread test program failed. Your platform is
|
|
| Christopher Browne 2006-01-22, 8:24 pm |
| ML mail <mlnospam-/ E1597aS9LQAvxtiuMwx3
w@public.gmane.org> writes:
> Hello,
> I am currently installing Slony1 1.1.2 with PostgreSQL 8.1.2 and read in =
the INSTALL file that I should compile PostgreSQL with the
> --enable-thread-safety option because I am using Solaris 9 on SPARC Platf=
orm (Sun Netra X1). That's what I did but at the end of the
> configure I get the following error message:
> *** Thread test program failed.=A0 Your platform is not thread-safe.
> *** Check the file 'config.log'for the exact reason.
> ***
> *** You can use the configure option --enable-thread-safety-force
> *** to force threads to be enabled.=A0 However, you must then run
> *** the program in src/tools/thread and add locking function calls
> *** to your applications to guarantee thread safety. =A0=A0=A0=A0=A0=A0=A
0=
=A0=A0=A0=A0=A0=A0[c
olor=darkred]
> Does anyone know what's the problem here and what should I do ? Shall I s=[/color]
imply ignore this error and compile ? Or can I use PostgreSQL with
> Slony1 without this option ?
> Many thanks in advance for any hints or advices.
> Best regards
Hmm. We're not using Solaris anymore so wisdom available may be
limited.
The thing that you need is for libpq to be compiled with thread safety
turned on, as otherwise, the multiple Slony-I threads that call libpq
will trample over one another.
What I'd suggest is that you look in config.log; the last program that
configure compiled should be listed there, and there should be some
indication as to what failed. (Sometimes error messages are
deceiving, of course.)
You can always *try* to proceed, and see what you get.
If libpq isn't suitably thread safe, you can expect that slon queries
looking for events will fail; there are a couple of typical error
messages.
See the FAQ for more details...
<http://linuxdatabases.info/info/faq.html>
-- =
select 'cbbrowne' || '@' || 'ca.afilias.info';
<http://dba2.int.libertyrms.com/>
Christopher Browne
(416) 673-4124 (land)
| |
| ML mail 2006-01-22, 8:24 pm |
| Hi Christopher,
First many thanks for your answer !
What I'd suggest is that you look in config.log; the last program that
configure compiled should be listed there, and there should be some
indication as to what failed. (Sometimes error messages are
deceiving, of course.)
I am not really a programmer and have not much clues about C/C++/Makefiles so I thought I may attach you the config.log file which the configure script generated. Could you maybe have a quick look if you can see where the problem is ? I've attached it as gzip to this mail.
Best regards
---------------------------------
Yahoo! Photos
Got holiday prints? See all the ways to get quality prints in your handsASAP.
| |
| Philip Yarra 2006-01-22, 8:24 pm |
| ML mail wrote:
> I am not really a programmer and have not much clues about
> C/C++/Makefiles so I thought I may attach you the config.log file which
> the configure script generated. Could you maybe have a quick look if you
> can see where the problem is ? I've attached it as gzip to this mail.
Uhhh... looking at the output of config.log, I'm not sure I trust this
output to mean "your platform is not thread safe" - more like "something
went spoink, and that's what we were doing at the time".
I've just tried CC=gcc ./configure --enable-thread-safety
--without-readline on a Solaris9 sparc box here, and I don't get the
same issue.
What I find really odd in your results is this:
configure:22452: checking thread safety of required library functions
configure:22480: gcc -o conftest -O2 -Wall -Wmissing-prototypes
-Wpointer-arith -Winline -Wendif-labels -fno-strict-aliasing -pthreads
-pthreads -D_REENTRANT -D_THREAD_SAFE - D_POSIX_PTHREAD_SEMA
NTICS
-DIN_CONFIGURE -I/opt/sfw/include -I/opt/sfw/include -L/opt/sfw/lib
-R/opt/sfw/lib -L/opt/sfw/lib conftest.c -lz -lreadline -ltermcap -lrt
-lresolv -lgen -lsocket -lnsl -ldl -lm -lpthread -lpthread >&5
conftest.c:135:44: ./src/tools/thread/thread_test.c: No such file or
directory
From the location where you ran configure, can you check that
../src/tools/thread/thread_test.c actually exists? It certainly does
here. If that's missing, perhaps your source is incomplete?
Regards, Philip.
| |
| ML mail 2006-01-23, 3:24 am |
| Philip Yarra <philip-/ Gi33b8PZOwAvxtiuMwx3
w@public.gmane.org> wrote:What I find really odd in your results is this:
configure:22452: checking thread safety of required library functions
configure:22480: gcc -o conftest -O2 -Wall -Wmissing-prototypes
-Wpointer-arith -Winline -Wendif-labels -fno-strict-aliasing -pthreads
-pthreads -D_REENTRANT -D_THREAD_SAFE - D_POSIX_PTHREAD_SEMA
NTICS
-DIN_CONFIGURE -I/opt/sfw/include -I/opt/sfw/include -L/opt/sfw/lib
-R/opt/sfw/lib -L/opt/sfw/lib conftest.c -lz -lreadline -ltermcap -lrt
-lresolv -lgen -lsocket -lnsl -ldl -lm -lpthread -lpthread >&5
conftest.c:135:44: ./src/tools/thread/thread_test.c: No such file or
directory
From the location where you ran configure, can you check that
../src/tools/thread/thread_test.c actually exists? It certainly does
here. If that's missing, perhaps your source is incomplete?
Hi Philip,
I checked in my source directory of PostgreSQL 8.1.2 and you're right there is no src/tools/thread directory. I'm using the file postgresql-base-8.1.2.tar.gz which I've downloaded from the PostgreSQL main website. Do I maybe need any other source files ? Or is that a case where I need to decompress this file with GNU tar and not Solaris tar ?
Thanks for your help
Best regards
---------------------------------
Yahoo! Photos – Showcase holiday pictures in hardcover
Photo Books. You design it and we’ll bind it!
| |
|
|
| Philip Yarra 2006-01-24, 3:24 am |
| On Mon, 23 Jan 2006 06:26 pm, ML mail wrote:
> I checked in my source directory of PostgreSQL 8.1.2 and you're right
> there is no src/tools/thread directory. I'm using the file
> postgresql-base-8.1.2.tar.gz which I've downloaded from the PostgreSQL main
> website.
I'd suggest you have a faulty download, or some files have been deleted since
you unpacked it.
$ wget \
ftp://ftp.au.postgresql.org/pub/pos...ql-8.1.2.tar.gz
[file comes down...]
$ gunzip -c postgresql-8.1.2.tar.gz | tar tf - | grep 'src\/tools\/thread'
postgresql-8.1.2/src/tools/thread/
postgresql-8.1.2/src/tools/thread/Makefile
postgresql-8.1.2/src/tools/thread/README
postgresql-8.1.2/src/tools/thread/thread_test.c
> Do I maybe need any other source files ?
No
> Or is that a case where I
> need to decompress this file with GNU tar and not Solaris tar ?
Solaris tar is fine (it is what I used in the example above). I think your
best course of action is to re-download the tarball and check that it
contains the right files.
Regards, Philip.
--
"Debugging is twice as hard as writing the code in the first place.
Therefore, if you write the code as cleverly as possible, you are,
by definition, not smart enough to debug it." - Brian W. Kernighan
-----------------
Utiba Pty Ltd
This message has been scanned for viruses and
dangerous content by Utiba mail server and is
believed to be clean.
| |
| Philip Yarra 2006-01-24, 3:24 am |
| My apologies, just after I posted this I realised that you've got the -base
package. I downloaded that and yes, it's missing files. I suggest you grab
postgresql-8.1.2.tar.gz instead.
Regards, Philip.
On Tue, 24 Jan 2006 01:54 pm, Philip Yarra wrote:
> On Mon, 23 Jan 2006 06:26 pm, ML mail wrote:
>
> I'd suggest you have a faulty download, or some files have been deleted
> since you unpacked it.
>
> $ wget \
> ftp://ftp.au.postgresql.org/pub/pos...tgresql-8.1.2.t
>ar.gz [file comes down...]
> $ gunzip -c postgresql-8.1.2.tar.gz | tar tf - | grep 'src\/tools\/thread'
> postgresql-8.1.2/src/tools/thread/
> postgresql-8.1.2/src/tools/thread/Makefile
> postgresql-8.1.2/src/tools/thread/README
> postgresql-8.1.2/src/tools/thread/thread_test.c
>
>
> No
>
>
> Solaris tar is fine (it is what I used in the example above). I think your
> best course of action is to re-download the tarball and check that it
> contains the right files.
>
> Regards, Philip.
--
"Debugging is twice as hard as writing the code in the first place.
Therefore, if you write the code as cleverly as possible, you are,
by definition, not smart enough to debug it." - Brian W. Kernighan
-----------------
Utiba Pty Ltd
This message has been scanned for viruses and
dangerous content by Utiba mail server and is
believed to be clean.
|
|
|
|
|