On Mon, 2005-01-17 at 17:52 -0500, Tom Lane wrote:
> John DeSoi <[EMAIL PROTECTED]> 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
Hi,
Looks to me like you have to add -lkrb5 and -lssl to your compile flags
as well. Perhaps some more others (you can use nm in conjunction with
grep to find which libraries define the missing symbols (On OpenBSD
like so: 'cd /usr/lib && nm -o * | grep krb5_free_context' but that
might differ on
John DeSoi <[EMAIL PROTECTED]> writes:
> On Jan 17, 2005, at 2:10 PM, Matthew Metnetsky wrote:
>> I'd appreciate any suggestions on getting a statically linked library
>> against libpq. I'm currently compiling on a Fedora Core 3 machine with
>> gcc-2.95.3 against the postgresql-libs-7.4.6-1.FC3.2
On Jan 17, 2005, at 2:10 PM, Matthew Metnetsky wrote:
I'd appreciate any suggestions on getting a statically linked library
against libpq. I'm currently compiling on a Fedora Core 3 machine with
gcc-2.95.3 against the postgresql-libs-7.4.6-1.FC3.2 package.
This is what I'm using to create a versio
[EMAIL PROTECTED]Subject: Re: [GENERAL]
Statically linking against libpq
On Mon, 2005-01-17 at 14:10 -0500, Matthew Metnetsky wrote:
> I'll start off by saying that I am a compiling novice, so bear with me
> please.
>
> I have a library which is being plugged into a game server to provide
> extra functionality. The library is currently linked against libpq like
> so `
I'll start off by saying that I am a compiling novice, so bear with me
please.
I have a library which is being plugged into a game server to provide
extra functionality. The library is currently linked against libpq like
so `gcc -shared -lpq`. It compiles and runs great as long as people
have li
