we have our own C library that we wrote by porting parts of the BSD C library on top the Linux kernel. but it conforms to the ARM EABI and you can trivially see that our own system libraries refer to these kind of symbols dynamically too.
On Fri, Mar 28, 2008 at 12:19 PM, David Given <[EMAIL PROTECTED]> wrote: > Digit wrote: > > ah sorry, I wasn't clear enough that I'm interested in the cases where > you > > have some of the __aeabi_ symbols in your shared library that do not get > > properly linked at runtime. > > I can't help you much with System.loadLibrary() right now :-( > > Ah, I see! > > I'll see if I can construct some C code that generates the four > offending RTL references on Monday (when I get my compiler back): > > >> __aeabi_f2uiz > >> __aeabi_lasr > >> __aeabi_llsl > >> __aeabi_llsr > > I'm a little surprised, TBH; these are all specified in the ABI. What > libc are you using? > > -- > ┌─── ｄｇ＠ｃｏｗｌａｒｋ．ｃｏｍ ───── http://www.cowlark.com ───── > │ "I have always wished for my computer to be as easy to use as my > │ telephone; my wish has come true because I can no longer figure out > │ how to use my telephone." --- Bjarne Stroustrup > > --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
