And you're sure you installed libFnord.so in /system/lib? If it can't dlopen it, it could be because of binary incompatibility. It could also be filesystem permissions. Don't forget that each app runs as its own userid. The error with dlopen means that it isn't even getting to dlsym, which is where it looks up the JNI methods.
-joe On Thu, Mar 27, 2008 at 12:02 PM, David Given <[EMAIL PROTECTED]> wrote: > > Joe Onorato wrote: > [...] > > Ususally, adb logcat will show you the symbols that are missing. Are > > you seeing a case where it doesn't? > > I'm never seeing a case where it *does*. > > All I see in the logs is: > > D/dalvikvm( 597): LOADING path /system/lib/libFnord.so 0x4006c4f8 > I/dalvikvm( 597): Unable to dlopen(/system/lib/libFnord.so): Cannot > find library > > The 'Cannot find library' string looks like it *might* have come from > dlerror(), but the message itself looks rather unlikely. It's quite > possible that the cut-down libc's version of dlerror() is just returning > a constant string for all errors rather than the actual error. > > -- > 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 -~----------~----~----~----~------~----~------~--~---
