Hi Deva, Thanks for sharing that.
I will first try to load this new image on the simulator (in eclipse). Also, on the file you pointed me to, do you know the possible values for TARGET_PRODUCT? Should it be something like arm? Or more like the phone model? Talking about the risks, if I push a image which is not working into my phone, is there a way to push a new one to try to fix that? Or will that "break" the phone? Thanks, JM 2010/9/13 Deva R <r.deva...@gmail.com>: > unless modified explicitly, out/target/product/generic build binaries > will work for emulators only (qemu platforms)., > > we need to build for devices by creating target specific build files > (usually arm binaries) like, > http://git.omapzoom.org/?p=device/ti/zoom2.git;a=blob;f=buildspec.mk.default;hb=froyo > (and copy it to ./mydroid/buildspec.mk before build) > > > -- > Regards, > Deva > www.bittoggler.com > > > On Mon, Sep 13, 2010 at 7:08 AM, Jean-Marc Spaggiari > <jean-m...@spaggiari.org> wrote: >> Hi Deva, >> >> I found stubs-32.h in the package libc6-dev-i386 wich I forgot to install. >> >> Look like also I had an issue with sun-java5-jdk. I had the 6 >> installed because the 5 is not available on debian testing. So I got >> the version 5 from the stable branch. >> >> I installed libiconv too based on what is described on omappedia >> >> Now, look like it's compiling correctly. >> >> Here are the last lines of the output. >> >> target Strip: sensors.trout >> (out/target/product/generic/obj/lib/sensors.trout.so) >> Generated: (out/target/product/generic/android-info.txt) >> Target system fs image: >> out/target/product/generic/obj/PACKAGING/systemimage_unopt_intermediates/system.img >> Install system fs image: out/target/product/generic/system.img >> Target ram disk: out/target/product/generic/ramdisk.img >> Target userdata fs image: out/target/product/generic/userdata.img >> Installed file list: out/target/product/generic/installed-files.txt >> >> So now I will have to figure how to use the image in Eclipse or into >> my Nexus One. >> >> Thanks, >> >> JM >> >> 2010/9/12 Deva R <r.deva...@gmail.com>: >>>>So look like __WORDSIZE value is 32 and should be 64. >>> probably you installed 32bit ubuntu release?? >>> >>> coming to core problem, >>> in general, android binaries should have 32-bit code, and you can >>> force generation of 32-bit code in 64-bit machines by installing >>> libiconv, ia32-libs. >>> >>> Pls refer below links on building android on 64-bit host machine >>> http://source.android.com/source/download.html -> Ubuntu Linux (64-bit x86) >>> http://www.omappedia.org/wiki/Android_Getting_Started#ARM_Cross_Compiler >>> http://www.codesourcery.com/sgpp/lite/arm/portal/kbentry62 >>> >>> -- >>> Regards, >>> Deva >>> www.bittoggler.com >>> >>> On Mon, Sep 13, 2010 at 1:32 AM, Jean-Marc Spaggiari >>> <jean-m...@spaggiari.org> wrote: >>>> Hi, >>>> >>>> I tried to build Android under a64-bit linux debian and it was not working. >>>> >>>> All those steps are working fine: >>>> - Setting up your machine >>>> - Installing Repo >>>> - Initializing a Repo client >>>> - Getting the files >>>> >>>> Make is failling with the following output: >>>> /usr/include/gnu/stubs.h:7:27: error: gnu/stubs-32.h: Aucun fichier ou >>>> dossier de ce type >>>> make: *** [out/host/linux-x86/obj/EXECUTABLES/acp_intermediates/acp.o] >>>> Erreur 1 >>>> >>>> Here is the content of stubs.h: >>>> #if __WORDSIZE == 32 >>>> # include <gnu/stubs-32.h> >>>> #elif __WORDSIZE == 64 >>>> # include <gnu/stubs-64.h> >>>> #else >>>> # error "unexpected value for __WORDSIZE macro" >>>> #endif >>>> >>>> So look like __WORDSIZE value is 32 and should be 64. >>>> >>>> stubs-32.h does not exist on the system >>>> stubs-64.h exist on the system. >>>> >>>> Just let me know if you want me to test anything. >>>> >>>> Regards, >>>> >>>> Jean-Marc >>>> >>>> -- >>>> unsubscribe: android-porting+unsubscr...@googlegroups.com >>>> website: http://groups.google.com/group/android-porting >>>> >>> >> > -- unsubscribe: android-porting+unsubscr...@googlegroups.com website: http://groups.google.com/group/android-porting
