Re: BUG #4219: fseeko test failure in configure script

I have finally gotten cleanly through the configure step. The
documentation for postgres under section 15.5 gives the various
options, one of which is the --with-libraries. This option does not
seem to work correctly for Solaris 10 with various packages added
into /usr/local and /usr/local/ssl. A previous response indicated
that the use of LDFLAGS would solve this. However, the documentation
in section 15.5 does not give any indications or hisnts about what
types of usage are possible. Thus, the suggestion for putting in the
following as a template:
"-R /usr/local/lib:/usr/sfw/lib..." was the ticket. Thus, my script
is as follows:

./configure
--with-openssl
--with-libxml
--with-libxslt
--with-libraries=/usr/lib:/usr/local/ssl/lib:/usr/sfw/lib:
/usr/local/BerkeleyDB.4.2/lib:/usr/ccs/lib:/usr/ucblib
--with-includes=/usr/local/ssl/include:/usr/sfw/include:
/usr/local/BerkeleyDB.4.2/include
LDFLAGS='-R /usr/local/lib:/usr/local/ssl/lib:/usr/sfw/lib:
/usr/local/BerkeleyDB.4.2/lib:/usr/ccs/lib:/usr/ucblib'

++++++++++++++++

The pertinent ENV vars are:

HOSTTYPE=sun4
PATH=/usr/local/bin:/usr/local/sbin:/usr/sbin:/usr/bin:/usr/ccs/bin
PWD=/u1/installs/postgresql-8.3.1
JAVA_HOME=/usr/java
TZ=US/Pacific
PS1=#
SHLVL=2
OSTYPE=solaris
VENDOR=sun
MACHTYPE=sparc

++++++++++++++++++

All of the necessary components with dependencies were brought in
from sunfreeware and installed with pkgadd.
gcc=3.4.6 as the compiler and primary libgcc.

Nathan K. Reed
Programmer/Analyst
Supervisor of Records group
University of California, Irvine
Office of Admissions and Relations with Schools
(949) 824-9631

At 08:56 AM 6/6/2008, Peter Eisentraut wrote:
>Am Freitag, 6. Juni 2008 schrieb Nathan Reed:
> > Does not change anything. I have run the generic configure without
> > any parameters (--with-ssl, etc) and I get the same result. I have
> > done a number of permutations, made sure that bison is in place,
> > etc,etc,etc.
>
>Trying countless permutations of unrelated parameters is not going to get you
>closer to success. And neither is posting generic "I am not getting beyond
>this linker failure on the test of fseeko" error "descriptions" that have
>nothing to do with your problem. If you want to get any useful help, post
>your *exact* command line, and the *exact* output you get on the screen as
>well as the *complete* contents of files that the error message refers you
>to. And leave the interpretation to others. As far as I can tell, the
>problem you post is quite common on Solaris, but without any concrete
>information, I can't tell you how to fix it.