Digit wrote: > it definitely looks like there is something wrong with your toolchain. > the libgcc runtime functions should be prefixed with __aeabi_ and not > __armeabi_
Sorry, that was a typo (I didn't have access to the toolchain and was working from memory). The symbols are indeed prefixed with __aeabi. I'm using the recommended CodeSourcery arm-none-linux-gnueabi toolchain. [...] > as for the static libc, you cannot use it in shared libraries. even if > there wasn't relocation issues, this would break many things, (e.g. > pthread initialization). Hmm. This is a bit awkward, as there are multiple libc variants with different coverage, and I don't know which one Android has (and it may change in the future anyway). Perhaps I should avoid libc completely where possible and do direct syscalls instead? It's awfully ugly. Unless there's a set of Official Header files somewhere that I've missed, which I could compile against... -- David Given [EMAIL PROTECTED] --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Android Developers" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [EMAIL PROTECTED] Announcing the new M5 SDK! http://android-developers.blogspot.com/2008/02/android-sdk-m5-rc14-now-available.html For more options, visit this group at http://groups.google.com/group/android-developers?hl=en -~----------~----~----~----~------~----~------~--~---
