Re: [HACKERS] PostgreSQL 9.4 InterlockedCompareExchange appearing in mingw64-w32 causing issue with PostGIS win32 load

2014-05-22 Thread Paragon Corporation
-- REVISED NOTE -- > Hm. s_lock.h does define TAS() in terms of InterlockedCompareExchange() if WIN32_ONLY_COMPILER is defined ... but that code hasn't changed in quite a long time. It > seems like the combination of an extension built with WIN32_ONLY_COMPILER and a core built without that flag

Re: [HACKERS] PostgreSQL 9.4 InterlockedCompareExchange appearing in mingw64-w32 causing issue with PostGIS win32 load

2014-05-22 Thread Paragon Corporation
> Hm. s_lock.h does define TAS() in terms of InterlockedCompareExchange() if WIN32_ONLY_COMPILER is defined ... but that code hasn't changed in quite a long time. It > seems like the combination of an extension built with WIN32_ONLY_COMPILER and a core built without that flag should never have

Re: [HACKERS] PostgreSQL 9.4 InterlockedCompareExchange appearing in mingw64-w32 causing issue with PostGIS win32 load

2014-05-22 Thread Tom Lane
"Paragon Corporation" writes: > Not sure if people know this, but PostGIS windows builds are built with > mingw64-w32 and mingw64-w64 chains and usually used with EDB VC++ built > PostgreSQL. > This is mostly because there is too much unix stuff ingrained in PostGIS > toolchain making it difficul

[HACKERS] PostgreSQL 9.4 InterlockedCompareExchange appearing in mingw64-w32 causing issue with PostGIS win32 load

2014-05-21 Thread Paragon Corporation
Not sure if people know this, but PostGIS windows builds are built with mingw64-w32 and mingw64-w64 chains and usually used with EDB VC++ built PostgreSQL. This is mostly because there is too much unix stuff ingrained in PostGIS toolchain making it difficult to compile in VC++. Anyrate this has w