Fwd from android-framework mailinglist...rktb suggested me to ask for help from this list.
Hi list, We tried to use our own GNU tool chains (arm-eabi-, 4.2.1) to build Android framework, which includes some specific optimizations for the micro-architecture made by my employer, Marvell. But we met some problems. 1. Seems Google integrated an unwind_backtrace feature which is not a part of ARM EABI spec, but ours did not. I got some files can not find the unwind_backtrace symbols. 2. On some fields in symbol table, the new generated elf files can not be parsed by Google's prelink tools. Some fields are always 0xffffffff. As I cannot find the code from Android open source project, I just wonder if Google will open source the tool chains or provide the patch list they integrated. And if we have some optimizations in GNU tool chains, what is the way to push these features into Android pre-built toolchains. Thanks a lot, -stanley --~--~---------~--~----~------------~-------~--~----~ unsubscribe: [email protected] website: http://groups.google.com/group/android-porting -~----------~----~----~----~------~----~------~--~---
