Re: Cleaning up multiply-defined-symbol warnings on OS X

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: Martijn van Oosterhout <kleptog(at)svana(dot)org>
Cc: Peter Eisentraut <peter_e(at)gmx(dot)net>, pgsql-patches(at)postgresql(dot)org
Subject: Re: Cleaning up multiply-defined-symbol warnings on OS X
Date: 2006-05-09 13:18:17
Message-ID: 10612.1147180697@sss.pgh.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-patches

Martijn van Oosterhout <kleptog(at)svana(dot)org> writes:
> Eh? It stops a program expecting libpq4 being linked to libpq3 for any
> reason, so the above situation can't happen. You don't need to version
> any structs, only the functions using them.

If we have an existing app built against an unversioned libpq, what
happens if we roll in a versioned libpq? Does it break completely?
That is, is the introduction of versioning by itself an incompatible
ABI break?

regards, tom lane

In response to

Responses

Browse pgsql-patches by date

  From Date Subject
Next Message Tom Lane 2006-05-09 13:56:01 Re: current version: Patch - Have psql show current values
Previous Message Martijn van Oosterhout 2006-05-09 12:14:51 Re: Cleaning up multiply-defined-symbol warnings on OS X