Building tip

[markgross]

This is a response to a post on the Android Developer list as I hit
this issue while bringing up the android build on a new dev box.
see:
http://groups.google.com/group/android-developers/browse_thread/thread/11e297f006023dad/bb06fa99907c548e?lnk=gst&q=make+failed#bb06fa99907c548e

The failure is some dx commands fail in strange way's when your system
has a mixture of gnu jjave tools installed along with sun's java.

Its actually a message from linux kernel OOM killer gunning down the
build.

I've seen this happen when building on an OEM preloaded Ubuntu system
that came with the gnu java tools pre-installed. The fix I've found
was to purge the gnu java stuff, reboot, and try again.

--mgross

[Fred Grott]

A question I was under the impression that updating the Java Alternative setting to point to Sun Java would work ..am I wrong?

Fred Grott
Developer

MobileBytes Site: http://mobilebytes.wikidot.com/
Xspot Project Page: http://mobilebytes.wikidot.com/xspot
Xspot Demo Videos: http://www.youtube.com/user/memine44
Blog Site: http://www.jroller.com/shareme
You can also find me on these IMs:
Gtalk:fred.grott
skype:fred.grott
Or you can find me at:

[markgross]

Damn. I posted too soon. I'm still getting the OOM killer going off
when building.

I thought I found the pattern and fixed it, but I was mistaken.

I'm still investigating :(

--mgross

On Jan 24, 11:59 am, markgross <mark.gr...@intel.com> wrote:
> This is a response to a post on the Android Developer list as I hit
> this issue while bringing up the android build on a new dev box.

> see:http://groups.google.com/group/android-developers/browse_thread/threa...

[markgross]

Yes, this is what I thought was causing the problems. I have one
system that I think I've fixed but last night it OOM'ed in the same
way. I'm not sure what I'm missing yet.

On Jan 24, 12:09 pm, Fred Grott <fred.gr...@gmail.com> wrote:
> A question I was under the impression that updating the Java Alternative
> setting to point to Sun Java would work ..am I wrong?
>

> *Fred Grott
> Developer* *MobileBytes Site: *http://mobilebytes.wikidot.com/
> *Xspot Project Page:
> *http://mobilebytes.wikidot.com/xspot<http://mobilebytes.wikidot.com/xspot%20>
> *Xspot Demo Videos: *http://www.youtube.com/user/memine44
> *Blog Site: *http://www.jroller.com/shareme
> *You can also find me on these IMs:*
> Gtalk:fred.grott

> skype:fred.grott
> Or you can find me at:

> [image: linkdin] <http://www.linkedin.com/in/shareme>[image:
> twitter]<http://twitter.com/sharemefg>[image:
> perssonas] <http://perssonas.com/person?who=B4N7WnNM77VXpN>[image:
> friendfeed] <http://friendfeed.com/shareme>[image:
> mahalo]<http://www.mahalo.com/member/Shareme>[image:
> del.icio.us] <http://delicious.com/shareme>[image:
> digg]<http://digg.com/users/shareme>[image:
> identica] <http://identi.ca/shareme>[image:
> facebook]<http://www.facebook.com/home.php#/profile.php?id=592318318&ref=profile>[image:
> seesmic] <http://www.seesmic.com/shareme>[image:
> vimeo]<http://www.vimeo.com/user411149>[image:
> slideshare] <http://www.slideshare.net/shareme>[image:
> geeks]<http://geeks.pirillo.com/profile/FredGrott>

>
> On Sat, Jan 24, 2009 at 1:59 PM, markgross <mark.gr...@intel.com> wrote:
>
> > This is a response to a post on the Android Developer list as I hit
> > this issue while bringing up the android build on a new dev box.
> > see:
>

> >http://groups.google.com/group/android-developers/browse_thread/threa...

[markgross]

gah! I'm a moron. The OEM installed Ubuntu systems where setup
without swap!

I'm pretty sure its just a case of needed more than one 1gig of ram to
build without swap.

--mgross

[Aaron]

You need at least 1.5 gb of ram and at least 10 gb of hard drive
space.

I have tried building w/out at least 1.5 gb of ram and it will always
get stuck indefinitely at a single step.

For me, it takes me relatively 2 hours to build.