On Thu, Apr 01, 2004, Frank wrote:
> Just grabed the lastest snap shot of openssl Got a compile problem that
> probably needs to be addressed. In file x509_vfy.h the prototype for
> X509_policy_check() uses a reserved word explicit
>
> int X509_policy_check(X509_POLICY_TREE **ptree, int *expli
OOPS, sorry, it is a C++ reserved word even though it is
not a C reserved word, and I guess it would be a Good Idea
for OpenSSL to be callable from C++ as it used to be...
Charles B Cranston wrote:
We cannot find "explicit" as a reserved word in a (fairly old)
ANSI C book. Is this the GNU compile
We cannot find "explicit" as a reserved word in a (fairly old)
ANSI C book. Is this the GNU compiler or a vendor compiler?
Could this be a vendor-specific extension? Is there a compiler
command line switch to remove vendor-specific extensions?
Would the GNU compiler work better anyway?
Just grab
Just grabed the lastest snap shot of openssl Got a compile problem that
probably needs to be addressed. In file x509_vfy.h the prototype for
X509_policy_check() uses a reserved word explicit
int X509_policy_check(X509_POLICY_TREE **ptree, int *explicit,
Thanks,.
Frank
___
