Heikki Linnakangas <hlinn...@iki.fi> writes:
> Joseph, any chance we could see a backtrace or some other details from
> those crashes?
+1
> 'drongo' just reported linker errors:
> postgres.def : error LNK2001: unresolved external symbol
> GetOldFunctionMessage
> [c:\\prog\\bf\\root\\HEAD\\pgsql.build\\postgres.vcxproj]
> postgres.def : error LNK2001: unresolved external symbol errfunction
> [c:\\prog\\bf\\root\\HEAD\\pgsql.build\\postgres.vcxproj]
> postgres.def : error LNK2001: unresolved external symbol pq_getstring
> [c:\\prog\\bf\\root\\HEAD\\pgsql.build\\postgres.vcxproj]
> postgres.def : error LNK2001: unresolved external symbol pq_putbytes
> [c:\\prog\\bf\\root\\HEAD\\pgsql.build\\postgres.vcxproj]
> Release/postgres/postgres.lib : fatal error LNK1120: 4 unresolved
> externals [c:\\prog\\bf\\root\\HEAD\\pgsql.build\\postgres.vcxproj]
> Done Building Project
> "c:\\prog\\bf\\root\\HEAD\\pgsql.build\\postgres.vcxproj" (default
> targets) -- FAILED.
As far as that goes, I think suspicion has to fall on this:
Not re-generating POSTGRES.DEF, file already exists.
which gendef.pl prints if it thinks the def file is newer than
all the inputs. So either drongo had some kind of clock skew
issue, or that bit of logic in gendef.pl has some unobvious bug.
(I say "had" because I see the next run went fine.)
regards, tom lane
