<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:wfw="http://wellformedweb.org/CommentAPI/"
	xmlns:dc="http://purl.org/dc/elements/1.1/"
	xmlns:atom="http://www.w3.org/2005/Atom"
	xmlns:sy="http://purl.org/rss/1.0/modules/syndication/"
	xmlns:slash="http://purl.org/rss/1.0/modules/slash/"
	>

<channel>
	<title>bobpeers -&#62; blog &#187; compile</title>
	<atom:link href="http://blog.bobpeers.com/tag/compile/feed/" rel="self" type="application/rss+xml" />
	<link>http://blog.bobpeers.com</link>
	<description>Better late than never</description>
	<lastBuildDate>Mon, 14 Jun 2010 12:19:58 +0000</lastBuildDate>
	<language>en</language>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.0.1</generator>
		<item>
		<title>Compiling Google Andriod Progress</title>
		<link>http://blog.bobpeers.com/2009/02/27/compiling-google-andriod-progress/</link>
		<comments>http://blog.bobpeers.com/2009/02/27/compiling-google-andriod-progress/#comments</comments>
		<pubDate>Fri, 27 Feb 2009 16:54:50 +0000</pubDate>
		<dc:creator>Bob Peers</dc:creator>
				<category><![CDATA[Computing]]></category>
		<category><![CDATA[Linux]]></category>
		<category><![CDATA[android]]></category>
		<category><![CDATA[compile]]></category>
		<category><![CDATA[eee701]]></category>
		<category><![CDATA[virtualbox]]></category>

		<guid isPermaLink="false">http://blog.bobpeers.com/2009/02/27/compiling-google-andriod-progress/</guid>
		<description><![CDATA[It&#8217;s been pretty up and down but I&#8217;ve successfully compiled Google Andriod for an eee701. The problem is that after converting the installer.img into a VDI file and booting in Virtualbox I&#8217;m stuck at the boot menu. I&#8217;ve actually been compiling the source in a Virtual environment, a Fedora 10 virtual machine running on Windows [...]]]></description>
			<content:encoded><![CDATA[<p>It&#8217;s been pretty up and down but I&#8217;ve successfully compiled Google Andriod for an eee701. The problem is that after converting the installer.img into a VDI file and booting in Virtualbox I&#8217;m stuck at the boot menu.</p>
<p>I&#8217;ve actually been compiling the source in a Virtual environment, a Fedora 10 virtual machine running on Windows XP Professional.</p>
<p>In brief here&#8217;s the procedure so far on Fedora 10.</p>
<ol>
<li>Install the <a href="http://java.sun.com/javase/downloads/index.jsp">Sun Java SE Development Kit (JDK)</a></li>
<li>Edit your ~/.bashrc file and add the following lines.
<pre>export JAVA_HOME='/usr/java/jdk1.6.0_12'
PATH=.:$JAVA_HOME/bin:$JAVA_HOME/jre/bin:$PATH
</pre>
</li>
<li>Install gperf.
<pre># yum install gperf</pre>
</li>
<li>Make sure you have a ~/bin directory in your home directory, and check to be sure that this bin directory is in your path:
<pre>$ cd ~
$ mkdir bin
$ echo $PATH
</pre>
</li>
<li>Download the repo script and make sure it is executable:
<pre>$ curl http://android.git.kernel.org/repo >~/bin/repo
$ chmod a+x ~/bin/repo
</pre>
</li>
<li>Create an empty directory to hold your working files:
<pre>$ mkdir mydroid
$ cd mydroid
</pre>
</li>
<li>Get the cupcake branch
<pre>$ repo init -u git://android.git.kernel.org/platform/manifest.git -b cupcake</pre>
</li>
<li>To pull down files to your working directory from the repositories as specified in the default manifest, run
<pre>$ repo sync</pre>
</li>
<li>I tried compiling with
<pre>$ TARGET_ARCH=x86 TARGET_PRODUCT=eee_701 DISABLE_DEXPREOPT=true make -j2 installer.img</pre>
<p>but this fails with the error:</p>
<pre>du: cannot access `out/target/product/eee_701/data': No such file or directory
</pre>
<p>After making this data directory and running again the compiling is successful.</p>
<pre>File edit complete. Wrote 2 images.
Done with bootable installer image -[ out/target/product/eee_701/installer.img ]
</pre>
</li>
<li>Change to the output directory
<pre>$ cd out/target/product/eee_701/</pre>
</li>
<li>Convert the installer.img to a Virtualbox VDI file
<pre>$ VBoxManage  convertfromraw -static -format VDI ./installer.img  ./installer.vdi</pre>
</li>
<li>Create a new virtual machine in Virtualbox and use this vdi as the hard drive.</li>
<li>Unfortunately this is where I get stuck. At first I received errors like:
<pre>$  Booting `recovery`
cmdline (hd0,1)/cmdline
Error 15: File not found
</pre>
<p>or</p>
<pre>Booting `std_boot`
cmdline (hd0,2)/cmdline
Error 22: No such partition
</pre>
<p>Exactly as described <a href="http://groups.google.com/group/android-porting/msg/932537f8e19dccd0">here</a><br />
These problems were fixed by changing hd(0,2) to hd(0,0) but then it seems to boot only to be presented with this error. The same can be found in <a href="http://groups.google.com/group/android-porting/msg/74c62cb3d1023969">this post.</a></p>
<pre>init: Unable to open persistent property directory /data/property errno: 2
sh: can’t access tty: Waiting for device /dev/block/sdb2
</pre>
</li>
</ol>
<p>I can&#8217;t get past this error and the solutions on android-porting pages are sometimes hard to follow. Never the less I&#8217;ll keep trying especially that I&#8217;m so close.</p>
<p>Note that this was using the stock Andriod kernel. I also tried compiling the 2.6.27 kernel  but it fails with the following error.</p>
<pre>drivers/rtc/alarm.c:16:27: error: asm/mach/time.h: No such file or directory
drivers/rtc/alarm.c: In function ‘alarm_suspend’:
drivers/rtc/alarm.c:357: error: implicit declaration of function ‘save_time_delta’
make[2]: *** [drivers/rtc/alarm.o] Error 1
make[1]: *** [drivers/rtc] Error 2
make: *** [drivers] Error 2
</pre>
<p>Reading <a href="http://groups.google.com/group/android-porting/msg/de3d9c658a076f86">this post</a> I see that this is a known issue and there is a patch but I haven&#8217;t tried applying the patch yet.</p>
<p>If you do decide to compile your own kernel it&#8217;s pretty easy.</p>
<pre>$ cd ~/mydroid/vendor/asus/eee_701/
$ make menuconfig
</pre>
<p>Save the config file then.</p>
<pre>$ make bzImage</pre>
<p>Then copy the kernel to vendor/asus/eee_701</p>
<pre>$ cp arch/x86/boot/bzImage ../vendor/asus/eee_701/kernel</pre>
]]></content:encoded>
			<wfw:commentRss>http://blog.bobpeers.com/2009/02/27/compiling-google-andriod-progress/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Compiling Google Andriod for x86</title>
		<link>http://blog.bobpeers.com/2009/02/22/compiling-google-andriod-for-x86/</link>
		<comments>http://blog.bobpeers.com/2009/02/22/compiling-google-andriod-for-x86/#comments</comments>
		<pubDate>Sun, 22 Feb 2009 11:34:13 +0000</pubDate>
		<dc:creator>Bob Peers</dc:creator>
				<category><![CDATA[Computing]]></category>
		<category><![CDATA[Linux]]></category>
		<category><![CDATA[andriod]]></category>
		<category><![CDATA[compile]]></category>
		<category><![CDATA[google]]></category>

		<guid isPermaLink="false">http://blog.bobpeers.com/2009/02/22/compiling-google-andriod-for-x86/</guid>
		<description><![CDATA[After downloading and running the Google Andriod vdi for Virtualbox I decided to try and compile the source myself. I&#8217;m following the directions on the andriod-porting Google group including trying to enable networking that didn&#8217;t work in the vdi file I downloaded. I&#8217;ve just finished downloading the cupcake source tree from git that takes quite [...]]]></description>
			<content:encoded><![CDATA[<p>After downloading and running the Google Andriod vdi for Virtualbox I decided to try and compile the source myself. I&#8217;m following the directions on the <a href="http://www.mail-archive.com/android-porting@googlegroups.com/msg01386.html">andriod-porting Google group</a> including trying to enable networking that didn&#8217;t work in the vdi file I downloaded.</p>
<p>I&#8217;ve just finished downloading the cupcake source tree from git that takes quite a while as I&#8217;m not able to get more than about  1 to 2 Mbit/s when downloading. I&#8217;ve also modified the kernel config to include the &#8216;AMD PCnet32 PCI support&#8217; that is one of the network devices supported by Virtualbox.</p>
<p>Next step is to compile but that&#8217;s for another post.</p>
]]></content:encoded>
			<wfw:commentRss>http://blog.bobpeers.com/2009/02/22/compiling-google-andriod-for-x86/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
	</channel>
</rss>
