Re: [patch #10393] Fix shared library support on Android

[Roumen Petrov]

Bruno Haible wrote:
> Roumen Petrov wrote:
> > Android and Microsoft windows libraries must not use hard coded paths! 
> > Nevertheless what is supported by linker or loader.
>
> Why do you mention Microsoft Windows? The commit 
> 47c71f61df9ace4956cc943f291480315174726b
> has no effect on Microsoft Windows.
>
> > When I read commit I agree that is correct do not have RUNPATH!
> > The problem is that commit message is not so clear. Actually commit uses rpath 
> > flag!
> > NO! NO! NO!
>
> Why do you want that executables never have RUNPATH on Android? Just saying
> "NO! NO! NO!" is not a justification, and your arguments in [2] were not
> sensible either.
>
> If you want a certain binary that you build to have no RUNPATH, use the
> Android SDK, not Termux and not libtool. Or use libtool outside of Termux
> and don't provide a -R option. It's that easy.
> [SNIP]

Android and Microsoft windows must not encode any paths.
When I build PKIX-SSH and OpenSSL binaries I must ensure that those libraries 
and executable could run in any Android profile.
The packages are "SecureBox Pro" or SecureBox as add-on to "TermOne Plus".
PKIX-SSH binaries use ldns as resolver library. This library uses libtool.

Also to ensure that binaries runs on support API levels elf-cleaner is should be run to 
"strip" certain sections.


Roumen