Re: Bootstrapping pkgsrc on Android, was: Can anybody come with a creative solution to the "/bin/sh: bad interpreter" problem?

[Ottavio Caruso <ottavio2006-netbsd%yahoo.com@localhost>]

On Thursday, 2 February 2017,  <coypu%sdf.org@localhost> wrote:
> easiest - chroot.

Maybe, but see below [1]

 

> you can also attempt to set up a useful /bin by linking
> the right stuff.
> e.g. bind mount /system/bin to /bin.

I've tried 

$ mount -o bind ../usr/bin /bin

mount: No such file or directory

I believe /bin must be created first and I have no root access.

[1]

I did mention in one of my earlier posts that I had installed Proot 

https://github.com/proot-me/PRoot/blob/master/doc/proot/manual.txt

and used this script:

https://raw.githubusercontent.com/termux/termux-packages/master/packages/proot/termux-chroot

Then:

$ export SU=$BASH

$ ./bootstrap --unpriviled

This will not choke on finding a suitable shell, but it runs for about 4 hours and then exits while trying to find specific files starting with Android.*

In other words, when run as  fake root, it appears to expect Android specific files.

This seems to validate what Jonathan Perkin suggested earlier, that is, creating a new port for Android, which is beyond my skills and time available.

I can try to run the script again and post a log, if anybody is interested. 

-- 
Ottavio Caruso