You are completely right, the eee_701 target product is already configured to build as 32 bit. The problem I had with grub had other reasons that I could fix now. But after this the kernel complained that my system didn't have i686 cpu as expected but an i586. Now playing with the kernel config I wondered if there is an easy way to only compile the kernel part of the android system and still get an updated installer.img at the end? (sorry for these stupid questions, I'm quite green in these things:-).
By the way, if I get a working configuration for the Geode GX1, what would be the appropriate steps to follow? Put together a product repo like it exists now for the eee 701? I have been a android application developer of the first hour and now I would like to have a cute little machine running android in my kitchen...:-) On Dec 20, 7:22 pm, "David Turner" <[email protected]> wrote: > I believe it should already be built as 32-bit. In case of doubt, check > build/core/combo/linux-x86.mk which contains all compiler/link flags > definitions for linux x86 (also used on x86_64 machines) > > On Sat, Dec 20, 2008 at 11:07 AM, squix <[email protected]> wrote: > > > How can I make sure that android is built for 32bit on my 64bit > > machine? I guess my previous problem to run the installer on a Geode > > GX1 machine came from the fact that the installer has been built for > > 64 bit and not 32. I tried to send CFLAGS=-m32 LDFLAGS=-m32 to the > > build command together with the target arch and so. But will this > > work? > > > Thanks, > > Dani --~--~---------~--~----~------------~-------~--~----~ unsubscribe: [email protected] website: http://groups.google.com/group/android-porting -~----------~----~----~----~------~----~------~--~---
