1. 13 4月, 2005 1 次提交
  2. 11 4月, 2005 1 次提交
  3. 30 3月, 2005 1 次提交
  4. 03 11月, 2004 1 次提交
  5. 16 5月, 2004 1 次提交
  6. 20 4月, 2004 1 次提交
  7. 27 12月, 2003 1 次提交
  8. 28 11月, 2003 1 次提交
  9. 30 4月, 2003 1 次提交
  10. 21 3月, 2003 1 次提交
  11. 14 11月, 2002 1 次提交
  12. 13 11月, 2002 1 次提交
  13. 09 10月, 2002 1 次提交
  14. 28 6月, 2002 1 次提交
  15. 18 12月, 2001 1 次提交
  16. 15 11月, 2001 1 次提交
  17. 26 10月, 2001 1 次提交
  18. 01 8月, 2001 1 次提交
  19. 31 7月, 2001 1 次提交
  20. 09 3月, 2001 1 次提交
  21. 22 2月, 2001 1 次提交
  22. 20 2月, 2001 1 次提交
    • R
      Make all configuration macros available for application by making · cf1b7d96
      Richard Levitte 提交于
      sure they are available in opensslconf.h, by giving them names starting
      with "OPENSSL_" to avoid conflicts with other packages and by making
      sure e_os2.h will cover all platform-specific cases together with
      opensslconf.h.
      
      I've checked fairly well that nothing breaks with this (apart from
      external software that will adapt if they have used something like
      NO_KRB5), but I can't guarantee it completely, so a review of this
      change would be a good thing.
      cf1b7d96
  23. 25 9月, 2000 1 次提交
  24. 07 9月, 2000 1 次提交
  25. 13 6月, 2000 1 次提交
  26. 02 6月, 2000 1 次提交
    • R
      There have been a number of complaints from a number of sources that names · 26a3a48d
      Richard Levitte 提交于
      like Malloc, Realloc and especially Free conflict with already existing names
      on some operating systems or other packages.  That is reason enough to change
      the names of the OpenSSL memory allocation macros to something that has a
      better chance of being unique, like prepending them with OPENSSL_.
      
      This change includes all the name changes needed throughout all C files.
      26a3a48d
  27. 05 3月, 2000 1 次提交
  28. 24 1月, 2000 1 次提交
    • D
      · dd9d233e
      Dr. Stephen Henson 提交于
      Tidy up CRYPTO_EX_DATA structures.
      dd9d233e
  29. 21 5月, 1999 3 次提交
    • B
      It was a very bad idea to use #include "../e_os.h" -- when this occurs · 7e701817
      Bodo Möller 提交于
      in cryptlib.h (which is often included as "../cryptlib.h"), then the
      question remains relative to which directory this is to be interpreted.
      gcc went one further directory up, as intended; but makedepend thinks
      differently, and so probably do some C compilers.  So the ../ must go away;
      thus e_os.h goes back into include/openssl (but I now use
      #include "openssl/e_os.h" instead of <openssl/e_os.h> to make the point) --
      and we have another huge bunch of dependency changes.  Argh.
      7e701817
    • B
      Add a kludge :-( · d6847aed
      Bodo Möller 提交于
      There were problems with putting e_os.h just into the top directory,
      because the test programs are compiled within test/ in the "standard"
      case in in their original directories in the makefile.one case;
      and in the latter symlinks may not be available.
      d6847aed
    • B
      Don't install e_os.h in include/openssl, use it only as a local · 17e3dd1c
      Bodo Möller 提交于
      include file.
      17e3dd1c
  30. 15 5月, 1999 1 次提交
  31. 30 4月, 1999 2 次提交
  32. 29 4月, 1999 2 次提交
  33. 27 4月, 1999 2 次提交
  34. 25 4月, 1999 2 次提交