I faced a suffer couple days ago, 500 GB Hard disk on Lenovo IdeaCentre B320 All in-One Desktop PC getting almost full within 12 months usage. There are options, moving up some file to a back up storage of replacing by New Hard Disk ... which is suffering, since I need to resetting a lot of things, due to this loved PC I used for learning android building, B2G building, tweaking, little programming. Well a friend told me he has a 2 TB hard disk and he did not used, he is a film editor, working for a TV company. Okay ... I decided to replace e new hard disk ... 2 TB is interesting
On previous hard disk, a gentoo amd64 multilib well set up, juiced by stable gnome 2.32 desktop environment. I have NO enough time to set a gentoo on new hard disk, thus I decided to pick up lovely ubuntu 12.04 x86_64, fashioned by unity desktop environment. I don't like UNITY, thus give Cinnamon in option. During the installation, which is pretty quick and straight forward with "Just Work"...TM, oh No .... an 00:19.0 Ethernet controller: Intel Corporation 82579V Gigabit, give me hazle. Internet Connection randomly dropped ... very anoying. Updated the kernel from 184.108.40.206 to 220.127.116.11, the problem persist. I don't wish to compile own kernel at ubuntu :-)). With help of wifi connection (Atheros AR9285), I decided to download sysrescue CD 3.6.0 due to my old Sysrescue 1.5.2 also did not pick up Intel 82579V ethernet. After copying distfiles and some /etc/portage/configuration into New Hard Disk live in the IdeaCentre B320 ... I said "welcome back gentoo". Well this Desktop PC mostly for learning a little Android Developing and I rather boring with two standard panel of Gnome 2, but Gnome:3 is marked as UNSTABLE on gentoo portage and I decided to poke Xfce4 on this i3 dual core Intel processor with 2 x 8 GB RAM. Believed, this desktop can easily pick up KDE4 or Gnome:3. I wish NOT to give RAM space to Desktop Juice.
After safely moving needed repo, gitconfig, gpg, /home/user/bin file from old Hard disk, along with AOKP JB 4.2.2 Source Tree at 27 GB size, now have to start test. Gentoo is IMHO, the most FIT distro for developing, with selected profile "default/linux/amd64/13.0/desktop", almost all required packages for android development are well compiled, for sure unless 32 libs, just merge emul-linux-x86-baselibs and the Hero Package " JDK " . As you are aware, Google recommended sun-JDK for Android building, but LibreOffice use open-JDK or well known as IcedTea. At very personal reason, I don't want have TWO package installed, if I were can have ONLY ONE
Long debate arise on the internet among Android Enthusiast, regarding JDK, I used sun-JDK at previous gentoo box, Now it is good time to test IcedTea (Open JDK) for building an android rom. By default IcedTea-Bin package on gentoo dropped at /opt folder (as well as sun-jdk), with easy java-config -s command, gentoo user can easily set JVM to be used. Since I have only one JVM, thus automatically system picked IcedTea as JVM, look like I need to set USER to use this IcedTea JVM with java-config command. but Android still CAN NOT SEE. Finally I need to edit .bashrc file on /home/user/ add export PATH=/opt/icedtea-bin-18.104.22.168/bin:$PATH, exit terminal and re-open terminal. Give android build a try ..... : work flawlessly by commanding make clean :-)) Now test with real build
19:36:42 [/droid/aokp_jb]BUILDING WORKING FLAWLESSLY .........
x1123@gentoo >> . build/envsetup.sh
You're building on Linux
Lunch menu... pick a combo:
Which would you like? [full-eng] 32
Checking build tools versions...
You are attempting to build with an unsupported version of java.
Your version is: java version "1.6.0_27".
The correct version is: Java SE 1.6.
Please follow the machine setup instructions at
I built from AOKP source tree for GT-I9100 device (Samsung Galaxy II International Edition), flashing the built rom to device and booting properly. Thus I can confirm that open-JDK, well known as IcedTea is FIT to build Android ROM without any different with sun-JDK. Sure this is NOOB opinion ... OH Yes ... we see a warning from compiler, but the build went well