I've noticed the same thing on Linux and Solaris, but
have been able to build a statically linked set of
Postgresql executables on HP-UX.
Solaris (using gcc) seems even more finicky, insisting
linking to a shared libpq and libgcc even when it
has been directed to link statically.
For me, building/installing from source is the way to go.
Some of our customers, however, can't handle that and
want a "installable package".
Jon Earle wrote:
> Hi,
>
> Took the advice of folks here and decided to build a new postgresql. I
> downloaded v7.3.2 today and am trying to install it on Debian 3.0r0.
>
> It seemed to build okay. I gave it the following configure options (I
> took the configure options from the 'rules' file within the debian source
> package and tweaked them for my use [primarily deleting those I know I
> don't need]):
>
> ./configure \
>
> --disable-shared \
> --disable-rpath \
> make[3]: Entering directory
> `/root/postgresql-7.3.2/src/backend/utils/mb/conversion_procs/ascii_and_mic'
> /bin/sh ../../../../../../config/install-sh -c -m 755
> /opt/pgm/pgsql/lib/ascii_and_mic.so
> install: /opt/pgm/pgsql/lib/ascii_and_mic.so does not exist
> make[3]: *** [install] Error 1
> ..
>
> The file
> /root/postgresql-7.3.2/src/backend/utils/mb/conversion_procs/ascii_and_mic
> does exist.
--
P. J. "Josh" Rovero Sonalysts, Inc.
Email: rovero@sonalysts.com www.sonalysts.com 215 Parkway North
Work: (860)326-3671 or 442-4355 Waterford CT 06385
***********************************************************************
