On Wed, Feb 14, 2018 at 3:36 PM, Rob Landley wrote:
> I grabbed the current ndk (-r16b), make_standalone_toolchain.py'd an --arch
> x86_64 --api 26 toolchain, and then built defconfig toybox with it, and at
> link
> time it failed to find:
>
> '__android_log_write'
> 'facilitynames'
> 'getgrgi
I grabbed the current ndk (-r16b), make_standalone_toolchain.py'd an --arch
x86_64 --api 26 toolchain, and then built defconfig toybox with it, and at link
time it failed to find:
'__android_log_write'
'facilitynames'
'getgrgid_r'
'iconv'
'iconv_open'
'prioritynames'
'sethostname'
'stderr'
BarryK of Puppylinux's origins has been having a problem I think may be
worth sharing.
(http://bkhome.org/news/201802/experimenting-with-busybox-runit.html)
It's basically because:
"Neither System V init, daemontools, runit or perp provides any hooks to
wait for a service to go up or down. ru
they're unrelated. (the distinction between native system properties
and Java system properties -- both of which are relevant on Android --
causes a deal of confusion.)
On Wed, Feb 14, 2018 at 3:00 PM, scsijon wrote:
>
> May I point out that getprop and setprop are windows, Netware and Mac based
May I point out that getprop and setprop are windows, Netware and Mac
based in the origins of the desktop world, and are used nowadays by the
like of gnome, java, adobe, steam (games), SAS and a few ... other
mainline packages.
I'm not sure that android has control rights as they seem to imp
On Wed, Feb 14, 2018 at 8:06 AM, Rob Landley wrote:
> I'm working on release notes and I noticed this is the android toybox repo:
>
> Author: Tom Cherry
> Date: Thu Jan 4 10:13:59 2018 -0800
>
> Reland: Stop building getprop
>
> We've replaced this with our own C++ version to su
I'm working on release notes and I noticed this is the android toybox repo:
Author: Tom Cherry
Date: Thu Jan 4 10:13:59 2018 -0800
Reland: Stop building getprop
We've replaced this with our own C++ version to support the new
property info parsing.
Bug: 36001741
