Lutz Jaenicke via RT wrote:
We will probably not apply your change to the 0.9.6 line of
development, because it's a rather big change, and we try to avoid
that within the same line of development (for now, 0.9.x is a line of
development, so 0.9.7 is a different one, as is 0.9.8 (in development
right now, and where most if the bleeding edge hacking is done)).  We
will definitely take a closer look at your patch for 0.9.7 and 0.9.8.
Anymore news about this issue? Meaning: are there anymore missing
prototypes in the 0.9.7 and 0.9.8 trees, respectively?
I have tagged this ticket with the 0.9.7 keyword to be kept in mind.
If no more prototypes are missing in 0.9.7, this ticket should be
closed.
Hi, thanks for checking back on this. I'm just using whatever is in
FreeBSD, which currently is still at version 0.9.6g, so I can't easily
test 0.9.7 or 0.9.8.

However, my particular problem is very simple to duplicate. Just do this:

  $ echo "#include <openssl/ssl.h>" > xx.c
  $ cc -Wstrict-prototypes xx.c
  In file included from /usr/include/openssl/ssl.h:116,
                   from xx.c:1:
  /usr/include/openssl/comp.h:15: warning: function declaration isn't a prototype
  /usr/include/openssl/comp.h:16: warning: function declaration isn't a prototype
  /usr/include/openssl/comp.h:17: warning: function declaration isn't a prototype
  /usr/include/openssl/comp.h:18: warning: function declaration isn't a prototype
  /usr/include/openssl/comp.h:19: warning: function declaration isn't a prototype
  /usr/include/openssl/comp.h:20: warning: function declaration isn't a prototype

  ...etc etc...

Cheers,
-Archie

__________________________________________________________________________
Archie Cobbs     *     Packet Design     *     http://www.packetdesign.com
______________________________________________________________________
OpenSSL Project                                 http://www.openssl.org
Development Mailing List                       [EMAIL PROTECTED]
Automated List Manager                           [EMAIL PROTECTED]

Reply via email to