1. 09 12月, 2005 1 次提交
    • B
      Disble some Win32-specific code in win32-client-only builds: · 4ebd4224
      Bruce Momjian 提交于
      I have the problem, when building by MS-VC6.
      An error occurs in the 8.1.0 present source codes.
      
      nmake -f win32.mak
      ..\..\port\getaddrinfo.c(244) : error C2065: 'WSA_NOT_ENOUGH_MEMORY'
      ..\..\port\getaddrinfo.c(342) : error C2065: 'WSATYPE_NOT_FOUND'
      
      This is used by winsock2.h. However, Construction of a windows base is
      winsock.h.
      Then, Since MinGW has special environment, this is right. but, it is not
      found in VC6.
      Furthermore, in getaddrinfo.c, IPV6-API is used by
      LoadLibraryA("ws2_32");
      Referring to of dll the external memory generates this violation by VC6
      specification.
      
      I considered whether the whole should have been converted into winsock2.
      However, Now, DLL of MinGW creation operates wonderfully as it is.
      That's right, it has pliability by replacement of simple DLL.
      Then, I propose the system using winsock(non IPV6) in construction of
      VC6.
      
      Hiroshi Saito
      4ebd4224
  2. 08 12月, 2005 5 次提交
  3. 07 12月, 2005 19 次提交
  4. 06 12月, 2005 6 次提交
  5. 05 12月, 2005 3 次提交
    • T
    • T
      Fix a rather sizable number of problems in our homegrown snprintf, such as · 3311c766
      Tom Lane 提交于
      incorrect implementation of argument reordering, arbitrary limit of output
      size for sprintf and fprintf, willingness to access more bytes than "%.Ns"
      specification allows, wrong formatting of LONGLONG_MIN, various field-padding
      bugs and omissions.  I believe it now accurately implements a subset of
      the Single Unix Spec requirements (remaining unimplemented features are
      documented, too).  Bruce Momjian and Tom Lane.
      3311c766
    • B
      Update: · 99552287
      Bruce Momjian 提交于
      < 	  Win32 API, and we have to make sure MinGW handles it.
      > 	  Win32 API, and we have to make sure MinGW handles it.  Another
      > 	  option is to wait for the MinGW project to fix it, or use the
      > 	  code from the LibGW32C project as a guide.
      99552287
  6. 04 12月, 2005 6 次提交