Magnus Hagander wrote:
> >> How about this. If the required functions (which aren't
> >*too* many) are
> >> added to libpqdll.def, everything returns to working order.
> >It does add
> >> a slight maintainability issue - whenever a new binary is using a
> >> function in libpq never before exported, it has to be added to
> >> libpqdll.def.
> >Yeah, I was assuming we'd have to do that. (Does your
> >existing patch do
> >something different?)
> Well, my existing patch just changes it to export only what's in
> libpqdll.def. That's how I came across this problem.
> I'll polish it up and include all the necessary functions in
> libpqdll.def, then. There aren't that many, but a couple. I'll also try
> to work out how to deal with the SSL vs non-SSL DLL issue while at it.
Is this going to remove the requirement for pg_dump/Makefile to use
exec.o on the link line?
Bruce Momjian | http://candle.pha.pa.us
pgman(at)candle(dot)pha(dot)pa(dot)us | (610) 359-1001
+ If your life is a hard drive, | 13 Roberts Road
+ Christ can be your backup. | Newtown Square, Pennsylvania 19073
In response to
pgsql-hackers-win32 by date
|Next:||From: Magnus Hagander||Date: 2004-10-11 07:58:56|
|Subject: Re: build error in initdb on win32|
|Previous:||From: Magnus Hagander||Date: 2004-10-10 20:59:28|
|Subject: Re: build error in initdb on win32 |