1 |
On Sun, May 8, 2011 at 12:52 AM, Steev Klimaszewski |
2 |
<steev@××××××××××.com> wrote: |
3 |
> |
4 |
> > What overlay? I feel like I either missed part of this conversion, or there |
5 |
> > is an overlay that I don't know about. |
6 |
> > |
7 |
> My guess would be, the overlay he is doing this work in, so as to make |
8 |
> it public, once it actually works and people can use it, rather than |
9 |
> posting it in an unworkable state and having a million emails asking |
10 |
> why this or that isn't working. |
11 |
|
12 |
Good guess :) |
13 |
|
14 |
My main goal was to get this overlay up to speed with my last project |
15 |
that involved running jamvm atop bionic. The only difference here is |
16 |
that the other project was done with the Android build system while |
17 |
this one is using portage. |
18 |
|
19 |
Busybox works right now in my chroot environment (rpc, nfs, and a |
20 |
couple of other things are disabled for now). Library search paths |
21 |
were set to /lib and /usr/lib by default, so I don't need to set |
22 |
LD_LIBRARY_PATH anymore. Resolv is working. Need to add some things |
23 |
like crypt(3), getpwent(3), etc. |
24 |
|
25 |
The libc itself has several 'stubs' that print a 'fixme' message to |
26 |
stderr whenever invoked, and return NULL / -1 / errno=ENOSYS. |
27 |
|
28 |
The end result [current staus] will more or less be the following: |
29 |
|
30 |
cross-i686-pc-linux-bionic/{binutils,gcc,bionic,bionic-kernel-headers} |
31 |
[working aside from stubs] |
32 |
|
33 |
bionic (libc, libm, libthread_db, libstdc++) [libc has some stubs] |
34 |
icu4c [needs a c++ compiler] |
35 |
zlib [working] |
36 |
libxml2 [working, needs to be rebuilt and linked with icu4c] |
37 |
libxslt [depends on working libxml2 w/ icu4c] |
38 |
file (libmagic) [working] |
39 |
classpath [soon...] |
40 |
jamvm [soon...] |
41 |
|
42 |
This setup (all the way to jamvm) is actually working quite well on 2 |
43 |
architectures right now (i686 & arm) when built using the Android |
44 |
build system, so I'll be happy when it's working using portage, |
45 |
because manual building / scripting from autotools to plain make is |
46 |
getting painful when I'm just adding a new library to the build. |
47 |
|
48 |
Cheers, |
49 |
|
50 |
C |