OK, so I'm working on updating the RH Linux rpm of Postgres to our new
release. And so I'll have to figure out how to *really* install all of
the Postgres components to make this work. Anyway, I've already asked
about the python installation procedure: thanks for the tips and I'll
try it out soon.
In the meantime, I've got other nagging problems/issues/questions.
Here is one:
On my linux box, psql has always built as a static app, not using the
libpq.so shared library. There seem to be two issues:
- libpq.so has not been installed at the time psql is built, so the
shared library is not available
- the link step for psql points at the libpq source directory, which
contains only the .a library, not the sharable library since that is
built on the fly during the library installation.
I can see how to modify the psql makefile to get a version using
shared libraries, but istm that one would really like to phase the
installation so that libraries are actually installed before apps need
to be linked.
Should we just build the sharable library during the "make all" rather
than the "make install"? Or perhaps it would be better to install the
library(ies) and then move on to building apps.
Comments?
--
Thomas Lockhart lockhart@alumni.caltech.edu
South Pasadena, California
