Thread: Solaris 10 Sun Studio 11 compile error configtest

     1239

Hello, I'm having problems compiling pgsql 8.1.0 for
Solaris 10 using Sun Studio 11.

I'm giving configure the following arguments:

OS: Solaris 10
Hardware: SunFire V100

PATH (the /usr/ucb/cc was renamed to /usr/ucb/cc.old
and chmod 000)
/opt/SUNWspro/bin:/usr/ccs/bin:/usr/bin:/usr/sbin:/sbin:/usr/sfw/bin:/usr/sfw/sbin:/opt/sfw/bin:/opt/sfw/sbin:/usr/ucb

LD_LIBRARY_PATH=/lib:/usr/lib:/usr/sfw/lib:/opt/sfw/lib
export LD_LIBRARY_PATH
./configure --prefix=/opt/sfw/pgsql8
--with-includes=/usr/include:/usr/sfw/inclu
de:/opt/sfw/include
--with-libs=/lib:/usr/lib:/usr/sfw/lib:/opt/sfw/lib
--enable
-integer-datetimes --with-open-ssl
--enable-thread-safety --enable-system-crypt

checking for gethostbyname_r... yes
checking whether getpwuid_r takes a fifth argument...
yes
checking whether strerror_r returns int... 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.
$ more config.log


configure:2028: checking for gcc
configure:2057: result: no
configure:2028: checking for cc
configure:2044: found /opt/SUNWspro/bin/cc
configure:2054: result: cc
configure:2075: checking for C compiler version
configure:2078: cc --version </dev/null >&5
cc: Warning: option -- passed to ld
usage: cc [ options] files.  Use 'cc -flags' for
details
configure:2081: $? = 1
configure:2083: cc -v </dev/null >&5
usage: cc [ options] files.  Use 'cc -flags' for
details
configure:2086: $? = 1
configure:2088: cc -V </dev/null >&5
cc: Sun C 5.8 2005/10/13
usage: cc [ options] files.  Use 'cc -flags' for
details
configure:2091: $? = 1
configure:2114: checking for C compiler default output
file name
configure:2117: cc    conftest.c  >&5
configure:2120: $? = 0
configure:2166: result: a.out
configure:2171: checking whether the C compiler works
configure:2177: ./a.out
configure:2180: $? = 0
configure:2197: result: yes
configure:2204: checking whether we are cross
compiling
configure:2206: result: no
configure:2209: checking for suffix of executables
configure:2211: cc -o conftest    conftest.c  >&5
configure:2214: $? = 0
configure:2239: result:
configure:2245: checking for suffix of object files
configure:2266: cc -c   conftest.c >&5
configure:2269: $? = 0
configure:2291: result: o
configure:2295: checking whether we are using the GNU
C compiler
configure:2319: cc -c   conftest.c >&5
"conftest.c", line 18: undefined symbol: choke
"conftest.c", line 18: syntax error before or at: me
cc: acomp failed for conftest.c
configure:2325: $? = 2
configure: failed program was:
| /* confdefs.h.  */
|
| #define PACKAGE_NAME "PostgreSQL"
| #define PACKAGE_TARNAME "postgresql"

Any ideas? Thanks!

-William



__________________________________________________
Do You Yahoo!?
Tired of spam?  Yahoo! Mail has the best spam protection around
http://mail.yahoo.com

William <rotaecho@yahoo.com> writes:
> 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.
> $ more config.log

You need to read a LOT further than that in config.log to find the
failure associated with this error.  There are going to be dozens or
hundreds of expected failures; the unexpected one will be at the end
(modulo some probably-useless printouts of variable values).

            regards, tom lane

Thanks, I figured that was as far as I had to go for
the error.

Turned out readline was searching for GCC (Sun's
Companion) version.  Disabled readline and went
without a hitch.

Thanks!

--- Tom Lane <tgl@sss.pgh.pa.us> wrote:

> William <rotaecho@yahoo.com> writes:
> > 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.
> > $ more config.log
>
> You need to read a LOT further than that in
> config.log to find the
> failure associated with this error.  There are going
> to be dozens or
> hundreds of expected failures; the unexpected one
> will be at the end
> (modulo some probably-useless printouts of variable
> values).
>
>             regards, tom lane
>


__________________________________________________
Do You Yahoo!?
Tired of spam?  Yahoo! Mail has the best spam protection around
http://mail.yahoo.com