Gentoo Archives: gentoo-soc

From: heroxbd <heroxbd@×××××.com>
To: gentoo-soc@l.g.o
Cc: redlizard@×××××××××.nl, abcd@g.o, gmt@×××××.us
Subject: [gentoo-soc] Gentoo on Android: Summary for 2013.6.20-21
Date: Fri, 21 Jun 2013 09:04:22
Message-Id: 87sj0bltsb.fsf@proton.in.awa.tohoku.ac.jp
In Reply to: [gentoo-soc] Gentoo on Android: Summary for 2013.6.7-19 by heroxbd
1 Dear Guy and Gals,
2
3 Gentoo on Android is about running Gentoo natively on Android
4 devices[1], mentored by Luca.
5
6 heroxbd <heroxbd@×××××.com> writes:
7
8 > Plan for 6.20 and 6.21:
9 >
10 > a. clear out the requirement of cross compile on Prefix and roll out
11 > a GLEP draft. We are already gaining momentum on a
12 > specification in Prefix community.
13 >
14 > b. reflect more on gcc spec hack of toolchain, discussed today on
15 > IRC gentoo-prefix with redlizard and Mr. (surprise!)
16 > ABCD. Construct a toy system if time permitted.
17 >
18 > We have accumulated many kinds of wrappers that injects magic
19 > command line oppotions in Gentoo Prefix, and Prefix/libc adds
20 > even more. Things are getting more complex. By centering all
21 > hacks into gcc specs would make an elegant solution, with a
22 > by-product of merging {gcc,binutils}-config between Gentoo Prefix
23 > and vanilla.
24 >
25 > An example of hacking gcc spec from LFS:
26 >
27 > http://www.linuxfromscratch.org/lfs/view/development/chapter06/adjusting.html
28
29 Unfortunately, I have no advancement during these two days.
30
31 I'd like to push this plan into next week.
32
33 a. Greg is working on crossdev on Prefix promptly[2], I'll try to
34 synchronize with him and make a version of Prefix-enabled crossdev
35 ready to be included upstream.
36
37 b. Get a proof of concept of gcc spec hack and roll out a Prefix/libc on
38 armhf based on it.
39
40 That's all.
41
42 Benda
43
44 1. http://www.awa.tohoku.ac.jp/~benda/projects/android.html
45
46 2. https://bugs.gentoo.org/show_bug.cgi?id=384167

Replies

Subject Author
[gentoo-soc] Re: Gentoo on Android: Summary for 2013.6.20-21 heroxbd <heroxbd@×××××.com>