From: | Kurt Roeckx <kurt(at)roeckx(dot)be> |
---|---|
To: | Bruce Momjian <pgman(at)candle(dot)pha(dot)pa(dot)us> |
Cc: | PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org> |
Subject: | Re: Bumping libpq version number? |
Date: | 2005-03-11 19:28:04 |
Message-ID: | 20050311192804.GA26406@roeckx.be |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
On Fri, Mar 11, 2005 at 01:29:46PM -0500, Bruce Momjian wrote:
> Kurt Roeckx wrote:
> >
> > Does initdb call pg_snprintf directly? Or does it call some
> > libpq function that calls it?
>
> With the current CVS, initdb calls pg_snprintf() on my platform which
> doesn't support %$ natively on my libc printf. Now, initdb could pull
> from pgport itself but I think it pulled from libpq first. Perhaps we
> should reorder how those libraries appear in the link line but I think
> that would fix just this case, not the more general one of pg client
> apps.
Do "client apps" ever link to pgport itself? I assume only
"internal" applictions link to it?
I assume libpq is staticly linked to pgport and is exporting
symbols it shouldn't. Can we prevent it from exporting those
symbols?
Kurt
From | Date | Subject | |
---|---|---|---|
Next Message | Bruce Momjian | 2005-03-11 19:37:17 | Re: Bumping libpq version number? |
Previous Message | Tom Lane | 2005-03-11 18:54:33 | Re: Functions and transactions |