1. 28 9月, 2019 1 次提交
  2. 18 10月, 2017 1 次提交
  3. 09 10月, 2017 1 次提交
  4. 15 9月, 2017 1 次提交
  5. 14 9月, 2017 1 次提交
  6. 03 11月, 2016 1 次提交
  7. 24 5月, 2016 1 次提交
  8. 18 5月, 2016 1 次提交
  9. 23 3月, 2016 3 次提交
  10. 19 2月, 2016 1 次提交
  11. 04 2月, 2016 2 次提交
  12. 27 1月, 2016 1 次提交
    • R
      Remove /* foo.c */ comments · 34980760
      Rich Salz 提交于
      This was done by the following
              find . -name '*.[ch]' | /tmp/pl
      where /tmp/pl is the following three-line script:
              print unless $. == 1 && m@/\* .*\.[ch] \*/@;
              close ARGV if eof; # Close file to reset $.
      
      And then some hand-editing of other files.
      Reviewed-by: NViktor Dukhovni <viktor@openssl.org>
      34980760
  13. 18 12月, 2015 1 次提交
  14. 10 11月, 2015 1 次提交
  15. 14 5月, 2015 1 次提交
  16. 01 5月, 2015 1 次提交
  17. 31 1月, 2015 1 次提交
  18. 22 1月, 2015 1 次提交
  19. 06 9月, 2013 1 次提交
  20. 02 1月, 2006 1 次提交
  21. 31 12月, 2005 1 次提交
  22. 10 6月, 2005 2 次提交
  23. 06 6月, 2005 1 次提交
  24. 08 1月, 2003 1 次提交
  25. 15 7月, 2002 1 次提交
    • R
      There's an ongoing project to bring some kind of path selection · cbecb3ac
      Richard Levitte 提交于
      mechanism to the ENGINE framework.  This means there there are going
      to be new functionality for the DSO part, and ultimately some way of
      merging two file specifications together.
      
      This commit places the merging code into the repository.  It's
      currently not used anywhere, and hasn't been tested at all.  It may be
      full of errors, including syntactical ones.  Those will be fixed as
      promptly as possible.
      cbecb3ac
  26. 16 11月, 2001 1 次提交
  27. 05 7月, 2001 1 次提交
  28. 26 4月, 2001 1 次提交
  29. 07 11月, 2000 1 次提交
  30. 27 10月, 2000 3 次提交
    • R
      On HP-UX, at least when shl_* are used, the libraries have the · 551e5990
      Richard Levitte 提交于
      extension .sl instead of .so.
      551e5990
    • R
      For the operating systems where it matters, it is sometimes good to · d9efa361
      Richard Levitte 提交于
      translate library names by only adding ".so" to them without
      prepending them with "lib".  Add the flag DSO_FLAG_NAME_TRANSLATION_EXT_ONLY
      for that purpose.
      d9efa361
    • G
      This changes the behaviour of the DSO mechanism for determining an · 51c8dc37
      Geoff Thorpe 提交于
      appropriate filename translation on the host system. Apart from this point,
      users should also note that there's a slight change in the API functions
      too. The DSO now contains its own to-be-converted filename
      ("dso->filename"), and at the time the DSO loads the "dso->loaded_filename"
      value is set to the translated form. As such, this also provides an impicit
      way of determining if the DSO is currently loaded or not. Except, perhaps,
      VMS .... :-)
      
      The various DSO_METHODs have been updated for this mechanism except VMS
      which is deliberately broken for now, Richard is going to look at how to
      fit it in (the source comments in there explain "the issue").
      
      Basically, the new callback scheme allows the filename conversion to
      (a) be turned off altogether through the use of the
          DSO_FLAG_NO_NAME_TRANSLATION flag,
      (b) be handled in the default way using the default DSO_METHOD's converter
      (c) overriden per-DSO by setting the override callback
      (d) a mix of (b) and (c) - eg. implement an override callback that;
          (i) checks if we're win32 "if(strstr(dso->meth->name, "win32"))..."
              and if so, convert "blah" into "blah32.dll" (the default is
      	otherwise to make it "blah.dll").
          (ii) default to the normal behaviour - eg. we're not on win32, so
               finish with (return dso->meth->dso_name_converter(dso,NULL)).
      (e) be retried a number of times by writing a new DSO_METHOD where the
          "dso_load()" handler will call the converter repeatedly. Then the
          custom converter could use state information in the DSO to suggest
          different conversions or paths each time it is invoked.
      51c8dc37
  31. 22 10月, 2000 1 次提交
  32. 09 10月, 2000 1 次提交
  33. 16 6月, 2000 1 次提交
    • G
      Currently the DSO_METHOD interface has one entry point to bind all · e9a68cfb
      Geoff Thorpe 提交于
      "symbols" including functions (of all prototypes( and variables. Whilst
      casting any function type to another violates ANSI C (I believe), it is
      a necessary evil in shared-library APIs. However, it is quite
      conceivable that functions in general and data symbols could very well
      be represented differently to each other on some systems, as Bodo said;
      
      > Since the function/object distinction is a lot more likely to be
      > important on real-life platforms supporting DSO *and* it can be quite
      > easily done *and* it will silence compilers that don't like
      > assignments from void pointers to function pointer variables, why
      > not do it?
      
      I agree. So this change splits the "dso_bind" handler in DSO_METHOD
      into "dso_bind_var" and "dso_bind_func". Similarly the exported
      function DSO_bind() has been split in two. I've also put together
      changes for the various DSO_METHOD implementations, but so far only
      DSO_dlfcn() has been tested. BTW: The prototype for dso_bind had been
      a bit strange so I've taken the opportunity to change its shape (in
      both variations).
      
      Also, the README has been updated - particularly with a note about
      using customised native name-translation for shared libraries (and that
      you can't do it yet).
      e9a68cfb
  34. 25 4月, 2000 1 次提交
    • G
      This case in the "dso_unload" handlers should not be reported as an error - · ebbaebf7
      Geoff Thorpe 提交于
      if a DSO_load(NULL,...) operation fails, it will have to call DSO_free() on
      the DSO structure it created and that will filter through to this "unload"
      call.
      
      If the stack size is "< 1", then the library never actually loaded. To keep
      things clean higher up, I'll treat this as a vacuous case without an error.
      It makes the error stack easier to follow real world cases, and the error
      this ignores was only useful for catching bugs in internal code, not
      mismatched calls from applications (which should be handled in the generic
      DSO layer).
      ebbaebf7