On Tue, Oct 15, 2013 at 9:48 AM, Peter Eisentraut <peter_e@gmx.net> wrote:
On Mon, 2013-10-14 at 23:08 +1300, David Rowley wrote:
> > Looks like something like: > > > #ifndef WIN32 > #define HAVE_VA_COPY 1 > #endif > > > would need to be added to asprintf.c, but also some work needs to be > done with mcxt.c as it uses va_copy unconditionally. Perhaps just > defining a macro for va_copy would be better for windows. I was not > quite sure the best header file for such a macro so I did not write a > patch to fix it.
Does Windows not have va_copy? What do they use instead?
Not quite sure what is used instead as I've never had the need to use it before, but Mircosoft do seem to be getting around to implementing the C99 standard for Visual Studios 2013. See here.
isolationtester.obj : error LNK2019: unresolved external symbol _pg_strdup referenced in function _try_complete_step [D:\Postgres\c\isolationtester.vcxproj]
isolationtester.obj : error LNK2019: unresolved external symbol _pg_asprintf referenced in function _try_complete_step [D:\Postgres\c\isolationtester.vcxproj