We do build against OpenSSL 3.0.X internally, so it should be fine for you. I believe you're seeing a linker error rather than a compilation error as, although the function has been removed, they have provided a compatibility macro detailed here: htt...
There is a circular reference between some of our libraries which can most easily be addressed by repeating the libraries at least twice on your link line (the example makefile should demonstrate that). If you are comfortable with using -Wl,--start-g...
Sorry to hear this, the porting kit should come with a document which describes how you either edit the src.conf file to point to a toolchain and then run genmake.pl to update the makefiles provided, or it tells you what you need to compile/link, whi...
We share your frustration. We have observed almost exactly the same experience ourselves and our best speculation is that Visual Studio debugger is adding its own breakpoints for whatever purpose but doesn't necessarily make them visible to us (the e...
This is the sort of behaviour (integers returning zero) you would see if tampering is detected. It was a design decision not to raise exceptions in the event of tampering as it could yield clues to someone attempting static analysis of the code.
To d...
