Re: Statically linking against libpq

On Mon, 2005-01-17 at 17:52 -0500, Tom Lane wrote:
> John DeSoi <desoi(at)pgedit(dot)com> writes:
> Presumably you are using a fairly vanilla set of configure options, too.
> Matthew's missing symbols are Kerberos subroutines, so evidently his
> problem is that he configured --with-krb5 but didn't bother to mention
> the Kerberos library(s) in his link command.
>
> What I would recommend if you want a plugin substitute for the RPM
> version of the library is to rebuild from the corresponding SRPM
> and look at the log output to determine what options were used and what
> libraries need to be mentioned while linking libpq.

By combining a bunch of the suggestions I've finally gotten it to work!
Thanks everyone! Essentially, I had to recompile libpq so that when I
compiled against it everything was included. Just setting the `-lpq -
lssl -lkrb5` to my linker wasn't enough. I had to compile libpq as
such, which then worked when I passed the same parameters to my linker.

~ Matthew

P.S. Still linking against crypt.so, so one more to kill!