Re: static or dynamic libpgport

On lör, 2011-12-10 at 20:26 -0500, Tom Lane wrote:
> > The other 
> > thing is we'd need to turn on flags that make the object suitable for a 
> > dynamic library (e.g. -fpic).
> 
> Right now, libpq laboriously rebuilds all the .o files it needs from
> src/port/ so as to get them with -fpic.  It would be nice if we could
> clean that up while we're doing this.  It might be all right to always
> build the client-side version of libpgport with -fpic, though I'd be sad
> if that leaked into the server-side build.

So would we continue to build the client binaries (psql, pg_dump, etc.)
against the static libpgport.a, thus keeping it "invisible" there, or
would we dynamically link them, thus creating a new dependency.