1 |
On Tuesday, April 05, 2011 22:39:48 Christopher Friedt wrote: |
2 |
> BSD userland politics aside, I wonder what the typical steps would be |
3 |
> to 'port' gentoo over to a bionic-based libc. Something like the |
4 |
> following? |
5 |
> |
6 |
> 1) manually build a bionic cross-toolchain |
7 |
> 2) do some basic verification with the cross-toolchain (static exe, |
8 |
> exe that uses .so, .so, etc) |
9 |
> 3) build a native toolchain with the cross-toolchain, record build |
10 |
> steps / patches along the way |
11 |
> 4) manually bootstrap gentoo natively, record build steps / patches |
12 |
> along the way |
13 |
> 5) set up overlays: portage, crossdev, bionic, gcc, etc |
14 |
|
15 |
put together an ebuild for bionic, add support to crossdev to mark *-bionic |
16 |
targets to use the bionic ebuild, and that's about it. |
17 |
|
18 |
you could add your own KEYWORD, but doesnt seem like it'd be worth it. |
19 |
|
20 |
as for the rest, considering the fundamental limitations they've added to |
21 |
bionic (limited libpthreads/libm/etc...), i dont think a "full" blown port |
22 |
makes much sense. bionic is a toy libc meant for one thing -- get a java vm |
23 |
running on top of it. if you want a "real" embedded Linux system, uClibc |
24 |
makes a hell of a lot more sense. |
25 |
|
26 |
so feel free to put together a bionic ebuild to get into the tree, and a |
27 |
crossdev/toolchain.eclass patch should be trivial. |
28 |
-mike |