Tom Lane wrote: > Andrew Dunstan <[EMAIL PROTECTED]> writes: > > That got me through the backend compile and through libpq to ecpg, which > > fell over at the link stage complaining about missing references to > > pg_sprintf and pg_snprintf ... not sure how to fix that - windows > > experts, please advise. > > Plan A would be to make libpq export pg_snprintf and friends, Plan B > would be to give ecpg its own copy of snprintf.o. Plan A is probably > better since you're going to hit the same issue no doubt in all of the > src/bin programs.
I am confused why we would need either of these. All apps use libpgport, and that pg_*printf should be in that library. The original work Andrew did has problems particularly with ecpg, but why does ecpg cause problems? Doesn't it link in pgport? -- Bruce Momjian | http://candle.pha.pa.us pgman@candle.pha.pa.us | (610) 359-1001 + If your life is a hard drive, | 13 Roberts Road + Christ can be your backup. | Newtown Square, Pennsylvania 19073 ---------------------------(end of broadcast)--------------------------- TIP 6: explain analyze is your friend
