Обсуждение: 8.2beta1 does not compile for me on Solaris 10
[jks@xx ~/postgresql-8.2beta1]$ ./configure --enable-debug --with-cassert checking build system type... i386-pc-solaris2.10 checking host system type... i386-pc-solaris2.10 checking which template to use... solaris checking whether to build with 64-bit integer date/time support... no checking whether NLS is wanted... no checking for default port number... 5432 checking for gcc... gcc checking for C compiler default output file name... a.out checking whether the C compiler works... yes checking whether we are cross compiling... no checking for suffix of executables... checking for suffix of object files... o checking whether we are using the GNU C compiler... yes checking whether gcc accepts -g... yes checking for gcc option to accept ANSI C... none needed checking if gcc supports -Wdeclaration-after-statement... yes checking if gcc supports -Wendif-labels... yes checking if gcc supports -fno-strict-aliasing... yes configure: using CFLAGS=-O2 -Wall -Wmissing-prototypes -Wpointer-arith -Winline -Wdeclaration-after-statement -Wendif-labels -fno-strict-aliasing -g checking whether the C compiler still works... yes checking how to run the C preprocessor... gcc -E checking allow thread-safe client libraries... no checking whether to build with Tcl... no checking whether to build Perl modules... no checking whether to build Python modules... no checking whether to build with Kerberos 5 support... no checking whether to build with PAM support... no checking whether to build with LDAP support... no checking whether to build with Bonjour support... no checking whether to build with OpenSSL support... no checking for egrep... egrep configure: using CPPFLAGS= configure: using LDFLAGS= checking for gawk... no checking for mawk... no checking for nawk... nawk checking for flex... /usr/sfw/bin/flex checking whether ln -s works... yes checking for ld used by GCC... /usr/ccs/bin/ld checking if the linker (/usr/ccs/bin/ld) is GNU ld... no checking for ranlib... ranlib checking for tar... /usr/bin/tar checking for strip... strip checking whether it is possible to strip libraries... no checking for bison... bison -y checking for perl... /usr/bin/perl checking for library containing setproctitle... no checking for library containing pow... -lm checking for library containing dlopen... none required checking for library containing socket... -lsocket checking for library containing shl_load... no checking for library containing getopt_long... none required checking for library containing crypt... none required checking for library containing fdatasync... -lrt checking for library containing shmget... none required checking for -lreadline... no checking for -ledit... no configure: error: readline library not found If you have readline already installed, see config.log for details on the failure. It is possible the compiler isn't looking in the proper directory. Use --without-readline to disable readline support. [jks@xx ~/postgresql-8.2beta1]$ uname -a SunOS xx 5.10 Generic i86pc i386 i86pc config.log ends with: ## ----------- ## ## confdefs.h. ## ## ----------- ## #define DEF_PGPORT 5432 #define DEF_PGPORT_STR "5432" #define PACKAGE_BUGREPORT "pgsql-bugs@postgresql.org" #define PACKAGE_NAME "PostgreSQL" #define PACKAGE_STRING "PostgreSQL 8.2beta1" #define PACKAGE_TARNAME "postgresql" #define PACKAGE_VERSION "8.2beta1" #define PG_KRB_SRVNAM "postgres" #define PG_VERSION "8.2beta1" #define PG_VERSION_NUM 80200 #define PG_VERSION_STR "PostgreSQL 8.2beta1 on i386-pc-solaris2.10, compiled by GCC gcc (GCC) 3.4.3 (csl-sol210-3_4-branch+sol_rpath)" configure: exit 1
Joseph Shraibman wrote: > [jks@xx ~/postgresql-8.2beta1]$ ./configure --enable-debug --with-cassert > configure: error: readline library not found > If you have readline already installed, see config.log for details on the > failure. It is possible the compiler isn't looking in the proper > directory. > Use --without-readline to disable readline support. > [jks@xx ~/postgresql-8.2beta1]$ uname -a > SunOS xx 5.10 Generic i86pc i386 i86pc Do you have readline installed? Joshua D. Drake -- === The PostgreSQL Company: Command Prompt, Inc. === Sales/Support: +1.503.667.4564 || 24x7/Emergency: +1.800.492.2240 Providing the most comprehensive PostgreSQL solutionssince 1997 http://www.commandprompt.com/
> > Use --without-readline to disable readline support. > > [jks@xx ~/postgresql-8.2beta1]$ uname -a > > SunOS xx 5.10 Generic i86pc i386 i86pc > > Do you have readline installed? It's not standard on Solaris. I don't know if it's even available from Blastwave. -- --Josh Josh Berkus PostgreSQL @ Sun San Francisco
Joshua D. Drake wrote: > Joseph Shraibman wrote: > >>[jks@xx ~/postgresql-8.2beta1]$ ./configure --enable-debug --with-cassert >>configure: error: readline library not found >>If you have readline already installed, see config.log for details on the >>failure. It is possible the compiler isn't looking in the proper >>directory. >>Use --without-readline to disable readline support. >>[jks@xx ~/postgresql-8.2beta1]$ uname -a >>SunOS xx 5.10 Generic i86pc i386 i86pc > > > Do you have readline installed? > Apparently not. Of course it could be in some strange place where neither I nor the configure script can find it. Solaris is like that. I don't run postgresql on Solaris, I just happened to have a Solaris box on which I could test compile the beta, and I'mreporting the results.
Josh Berkus wrote: >>>Use --without-readline to disable readline support. >>>[jks@xx ~/postgresql-8.2beta1]$ uname -a >>>SunOS xx 5.10 Generic i86pc i386 i86pc >> >>Do you have readline installed? > > > It's not standard on Solaris. I don't know if it's even available from > Blastwave. > Apparently it is. http://www.blastwave.org/packages.php/readline postgresql is listed as one of the packages that depends on readline. Anyway I installed the readline package from blastwave but the configure script still didn't find it.
Joseph S wrote: > Joshua D. Drake wrote: >> Joseph Shraibman wrote: >> >>> [jks@xx ~/postgresql-8.2beta1]$ ./configure --enable-debug >>> --with-cassert >>> configure: error: readline library not found >>> If you have readline already installed, see config.log for details >>> on the >>> failure. It is possible the compiler isn't looking in the proper >>> directory. >>> Use --without-readline to disable readline support. >>> [jks@xx ~/postgresql-8.2beta1]$ uname -a >>> SunOS xx 5.10 Generic i86pc i386 i86pc >> >> >> Do you have readline installed? >> > Apparently not. Of course it could be in some strange place where > neither I nor the configure script can find it. Solaris is like that. > I don't run postgresql on Solaris, I just happened to have a Solaris > box on which I could test compile the beta, and I'm reporting the > results. I had to install a private copy of readline on buildfarm hyena to get it working there. cheers andrew
Joseph S <jks@selectacast.net> writes:
> Anyway I installed the readline package from blastwave but the configure
> script still didn't find it.
Where does blastwave put it? You likely need --with-includes and/or
--with=libraries switches to tell configure where to look.
regards, tom lane
Tom Lane wrote: > Joseph S <jks@selectacast.net> writes: > >>Anyway I installed the readline package from blastwave but the configure >>script still didn't find it. > > > Where does blastwave put it? You likely need --with-includes and/or > --with=libraries switches to tell configure where to look. > > regards, tom lane If I run: ./configure --enable-debug --with-cassert --with-includes=/opt/csw/include --with-libraries=/opt/csw/lib it gets past the readline problem, but fails later with: checking for _LARGEFILE_SOURCE value needed for large files... no checking for fseeko... (cached) yes checking test program... failed configure: error: *** Could not execute a simple test program. This may be a problem *** related to locating shared libraries. Check the file 'config.log' *** for the exact reason. $ tail config.log #define PACKAGE_NAME "PostgreSQL" #define PACKAGE_STRING "PostgreSQL 8.2beta1" #define PACKAGE_TARNAME "postgresql" #define PACKAGE_VERSION "8.2beta1" #define PG_KRB_SRVNAM "postgres" #define PG_VERSION "8.2beta1" #define PG_VERSION_NUM 80200 #define PG_VERSION_STR "PostgreSQL 8.2beta1 on i386-pc-solaris2.10, compiled by GCC gcc (GCC) 3.4.3 (csl-sol210-3_4-branch+sol_rpath)" configure: exit 1
Joseph S wrote: > Josh Berkus wrote: >>>> Use --without-readline to disable readline support. >>>> [jks@xx ~/postgresql-8.2beta1]$ uname -a >>>> SunOS xx 5.10 Generic i86pc i386 i86pc >>> >>> Do you have readline installed? >> >> >> It's not standard on Solaris. I don't know if it's even available >> from Blastwave. >> > Apparently it is. > > http://www.blastwave.org/packages.php/readline > > postgresql is listed as one of the packages that depends on readline. > > Anyway I installed the readline package from blastwave but the > configure script still didn't find it. > > blastwave installs packages in /opt/csw -- so you have to point configure to the directory if you are going to use that package -- I usually use the packages from sunfreeware.com which installs in /usr/local.
Joseph S wrote: > Tom Lane wrote: >> Joseph S <jks@selectacast.net> writes: >> >>> Anyway I installed the readline package from blastwave but the >>> configure script still didn't find it. >> >> >> Where does blastwave put it? You likely need --with-includes and/or >> --with=libraries switches to tell configure where to look. >> >> regards, tom lane > > If I run: > > ./configure --enable-debug --with-cassert > --with-includes=/opt/csw/include --with-libraries=/opt/csw/lib > > it gets past the readline problem, but fails later with: > > checking for _LARGEFILE_SOURCE value needed for large files... no > checking for fseeko... (cached) yes > checking test program... failed > configure: error: > *** Could not execute a simple test program. This may be a problem > *** related to locating shared libraries. Check the file 'config.log' > *** for the exact reason. > > $ tail config.log > #define PACKAGE_NAME "PostgreSQL" > #define PACKAGE_STRING "PostgreSQL 8.2beta1" > #define PACKAGE_TARNAME "postgresql" > #define PACKAGE_VERSION "8.2beta1" > #define PG_KRB_SRVNAM "postgres" > #define PG_VERSION "8.2beta1" > #define PG_VERSION_NUM 80200 > #define PG_VERSION_STR "PostgreSQL 8.2beta1 on i386-pc-solaris2.10, > compiled by GCC gcc (GCC) 3.4.3 (csl-sol210-3_4-branch+sol_rpath)" > > configure: exit 1 > I had similar issues, which is why I installed a private copy of readline. See working config at http://www.pgbuildfarm.org/cgi-bin/show_stage_log.pl?nm=hyena&dt=2006-10-10%20012001&stg=config cheers andrew
Joseph, How about just compiling --without-readline? Also, if you have Sun Studio 11 available, you'll get better performance out of your PostgreSQL. -- --Josh Josh Berkus PostgreSQL @ Sun San Francisco
Andrew Dunstan <andrew@dunslane.net> writes:
> Joseph S wrote:
>> checking test program... failed
>> configure: error:
>> *** Could not execute a simple test program. This may be a problem
>> *** related to locating shared libraries. Check the file 'config.log'
>> *** for the exact reason.
> I had similar issues, which is why I installed a private copy of readline.
This suggests that blastwave's version of readline needs some help, but
if you want to find out what went wrong you need to do more work than
"tail config.log". The last several hundred lines of output in that
file will usually just be configure dumping all its internal variables
--- everything after the comment
## ---------------- ##
## Cache variables. ##
## ---------------- ##
is usually unhelpful in my experience. You have to look at the output
from the failed test itself, just above that.
regards, tom lane
Joseph S <jks@selectacast.net> writes:
> I'm attaching the whole log.
It appears that blastwave's version of readline passes the link test:
> configure:6320: checking for -lreadline
> configure:6347: gcc -o conftest -O2 -Wall -Wmissing-prototypes -Wpointer-arith -Winline -Wdeclaration-after-statement
-Wendif-labels-fno-strict-aliasing -g -I/opt/csw/include -L/opt/csw/lib conftest.c -lreadline -lrt -lsocket -lm
>&5
> configure:6353: $? = 0
but fails at execution:
> configure:17432: checking test program
> configure:17447: gcc -o conftest -O2 -Wall -Wmissing-prototypes -Wpointer-arith -Winline
-Wdeclaration-after-statement-Wendif-labels -fno-strict-aliasing -g -I/opt/csw/include -L/opt/csw/lib conftest.c
-lz-lreadline -lrt -lsocket -lm >&5
> configure:17450: $? = 0
> configure:17452: ./conftest
> ld.so.1: ./conftest: fatal: libreadline.so.5: open failed: No such file or directory
> ./configure: line 17453: 9775 Killed ./conftest$ac_exeext
> configure:17455: $? = 137
> configure: program exited with status 137
This most likely means that libreadline depends on another shared
library (termcap maybe?) that isn't installed in your default search
path; so you'd need to set LD_LIBRARY_PATH or LD_RUN_PATH --- see item 3
in our FAQ_Solaris for info. One would think that blastwave's
documentation for the package would warn about this though.
I tend to agree with Andrew's solution of installing it in a more
standard place than /opt/csw ...
regards, tom lane
Tom Lane wrote: > This most likely means that libreadline depends on another shared > library (termcap maybe?) that isn't installed in your default search > path; so you'd need to set LD_LIBRARY_PATH or LD_RUN_PATH --- see > item 3 in our FAQ_Solaris for info. One would think that blastwave's > documentation for the package would warn about this though. The link editor looks in different places than the run-time linker, and that's why you need to give extra help to the run-time linker. It has nothing to do with readline, termcap, or blastwave. > I tend to agree with Andrew's solution of installing it in a more > standard place than /opt/csw ... That is the standard place. -- Peter Eisentraut http://developer.postgresql.org/~petere/