Well, I would be happy to assist you in keeping NO_FP_API alive and supply you with adequate diffs and resources. However, I would first need to know what exactly is not working for you and where and on which platform exactly it breaks for you because actually it is *working* for us.
Please note that the Amiga platform is substantially different to the usual Unix and Windows environments OpenSSL is build for. One important reason why we need the NO_FP_API support is, that AmigaOS comes with a variety of different c-library implementations which all have their own (thus incompatible) FP implementations. Thus, we need to have a possibility to easily compile OpenSSL without any FP depending function prototype so that our publicly released shared library can be used by applications being compile by different compilers and thus c-libraries implementation of FP. So please tell me *exactly* what you require to get the NO_FP_API support into a state that it is still acceptable for you. And please tell how and on which platform I can reproduce the problems you are seeing. best regards, jens Am 04.09.2014 um 03:02 schrieb Salz, Rich <rs...@akamai.com>: > I am sorry that I was not clear. > > I am saying that if there are people who depend and want no-stdio and > NO_FP_API to be kept in the OpenSSL source, then they need to feed their > patches, just to make those things work, back to OpenSSL. > > My mind is not made up. I am asking for people who want us to keep this, to > contribute code and effort so that we can do so. Right now it's a broken > build that nobody else can use. > > Does that make more sense? -- Jens Maus, Dresden/Germany http://jens-maus.de/ (Please note a real name change effective since 5.9.2013. Former name: Jens Langner) *** Content is authentic only with digital signature ***
smime.p7s
Description: S/MIME cryptographic signature
