You can not select more than 25 topics Topics must start with a letter or number, can include dashes ('-') and can be up to 35 characters long.


  1. General Information
  2. ~~~~~~~~~~~~~~~~~~~
  3. To compile this you need a couple things
  4. - A working POSIX system with working POSIX gcc, g++, make (GNU),
  5. ar, sh, awk and sed in the path
  6. - GNU Make 3.74 or so, -- normal UNIX make will NOT work
  7. * Note 3.77 is broken.
  8. - A working ANSI C++ compiler, this is not g++ 2.7.*
  9. g++ 2.8 works OK and newer egcs work well also. Nobody has tried it
  10. on other compilers :< You will need a properly working STL as well.
  11. - A C library with the usual POSIX functions and a BSD socket layer.
  12. If your OS conforms to the Single Unix Spec then you are fine:
  14. - Refer to the Build-Depends information in debian/control for
  15. additional requirements (some of which are Debian-specific)
  16. ** NOTICE **
  17. The C++ global constructors do not link correctly when using non-shared
  18. libraries. This is probably the correct behavior of the linker, but I have
  19. not yet had time to devise a work around for it. The correct thing to
  20. do is add a reference to debSystem in apt-pkg/,
  21. assert(&debSystem == 0) would be fine for instance.
  22. Guidelines
  23. ~~~~~~~~~~
  24. I am not interested in making 'ultra portable code'. I will accept patches
  25. to make the code that already exists conform more to SUS or POSIX, but
  26. I don't really care if your not-SUS OS doesn't work. It is simply too
  27. much work to maintain patches for dysfunctional OSs. I highly suggest you
  28. contact your vendor and express intrest in a conforming C library.
  29. That said, there are lots of finicky problems that must be dealt with even
  30. between the supported OS's. Primarily the path I choose to take is to put
  31. a shim header file in build/include that transparently adds the required
  32. functionality. Patches to make autoconf detect these cases and generate the
  33. required shims are OK.
  34. Current shims:
  35. * C99 integer types 'inttypes.h'
  36. * sys/statvfs.h to convert from BSD/old-glibc statfs to SUS statvfs
  37. * rfc2553 hostname resolution (methods/rfc*), shims to normal gethostbyname.
  38. The more adventurous could steal the KAME IPv6 enabled resolvers for those
  39. OS's with IPv6 support but no rfc2553 (why?)
  40. * define _XOPEN_EXTENDED_SOURCE to bring in h_errno on HP-UX
  41. * socklen_t shim in netdb.h if the OS does not have socklen_t
  42. The only completely non-shimmed OS is Linux with glibc2.1, glibc2.0 requires
  43. the first three shims.
  44. Platform Notes
  45. ~~~~~~~~~~~~~~
  46. Debian GNU Linux 2.1 'slink'
  47. Debian GNU Linux 'potato'
  48. Debian GNU Linux 'woody'
  49. * All Archs
  50. - Works flawlessly
  51. - You will want to have debiandoc-sgml and docbook2man installed to get
  52. best results.
  53. - No IPv6 Support in glibc's < 2.1.
  54. Sun Solaris
  55. SunOS cab101 5.7 Generic_106541-04 sun4u sparc
  56. SunOS csu201 5.8 Generic_108528-04 sun4u sparc
  57. - Works fine
  58. - Note, no IPv6 Support, OS lacks RFC 2553 hostname resolution
  59. OpenBSD
  60. OpenBSD gsb086 2.5 CMPUT#0 i386 unknown
  61. OpenBSD csu101 2.7 CMPUT#1 i386 unknown
  62. - OS needs 'ranlib' to generate the symbol table after 'ar'.. (not using
  63. GNU ar with the gnu tool chain :<)
  64. - '2.5' does not have RFC 2553 hostname resolution, but '2.7' does
  65. - Testing on '2.7' suggests the OS has a bug in its handling of
  66. ftruncate on files that have been written via mmap. It fills the page
  67. that crosses the truncation boundary with 0's.
  68. HP-UX
  69. HP-UX nyquist B.10.20 C 9000/780 2016574337 32-user license
  70. - Evil OS, does not conform very well to SUS
  71. 1) snprintf exists but is not prototyped, ignore spurious warnings
  72. 2) No socklen_t
  73. 3) Requires -D_XOPEN_SOURCE_EXTENDED for h_errno
  74. configure should fix the last two (see above)
  75. - Note, no IPv6 Support, OS lacks RFC 2553 hostname resolution