https://bugs.openldap.org/show_bug.cgi?id=9387
Issue ID: 9387 Summary: Support C++ Linkage Product: LMDB Version: unspecified Hardware: All OS: All Status: UNCONFIRMED Severity: normal Priority: --- Component: liblmdb Assignee: bugs@openldap.org Reporter: kriszyp@gmail.com Target Milestone: ---
Created attachment 777 --> https://bugs.openldap.org/attachment.cgi?id=777&action=edit Add directive for supporting C++ linking
The chacha8.h and module.h header files won't link properly (at least for me) with a C++ compiler/linker. I think they just need the linkage directives.
https://bugs.openldap.org/show_bug.cgi?id=9387
--- Comment #1 from Howard Chu hyc@openldap.org --- (In reply to kriszyp@gmail.com from comment #0)
Created attachment 777 [details] Add directive for supporting C++ linking
The chacha8.h and module.h header files won't link properly (at least for me) with a C++ compiler/linker. I think they just need the linkage directives.
Neither of those files are release artifacts. They're simply provided as examples of how the API works. If you're using them in other code you're doing something wrong.
https://bugs.openldap.org/show_bug.cgi?id=9387
kriszyp@gmail.com kriszyp@gmail.com changed:
What |Removed |Added ---------------------------------------------------------------------------- Resolution|--- |WONTFIX Status|UNCONFIRMED |RESOLVED
https://bugs.openldap.org/show_bug.cgi?id=9387
--- Comment #2 from kriszyp@gmail.com kriszyp@gmail.com --- BTW, is crypto.c considered to be a release artifact?
https://bugs.openldap.org/show_bug.cgi?id=9387
--- Comment #3 from Howard Chu hyc@openldap.org --- (In reply to kriszyp@gmail.com from comment #2)
BTW, is crypto.c considered to be a release artifact?
No. It's ridiculously hacky, using OpenSSL 1.1 internal structs that no application programmer should be using. It's proof of concept, nothing more.
-
openldap-its＠openldap.org