[openssl-dev] Usage of assembler code on ARM architectures

[Stefan.Neis at t-online.de]

        Hi,

Thanks for the answers to my questions - here come some more.

> Apple assembler uses a little bit different syntax and you can't
> assemble current modules as they are.

... as I found out myself just after asking the original question, but
of course, the following is good to know:

> There is perlasm/arm-xlate.pl that enables assembly for 64-bit
> iOS, and it's being modified to cover even 32-bit iOS.

Is that something that can/will be backported to 1.0.2- (or even 1.0.1-)
branch, once it's working?

> More specifically. Android has two distinct ARM targets, in sense that if
> you build JNI-enabled application, then you'd have to provide two ARM
> shared libraries, right?

Here, you lost me. So far, I'm building only one shared library for ARM,
using the no_asm variant of OpenSSL. And so far, there weren't complaints
about unsupported devices, so what do you mean by "two distinct ARM
targets"?

              Regards,
                            Stefan