Android: cannot locate symbol "pow" referenced by "libpython2.7.so"

[Andreas Heckwolf]

Hello,

after doing a more accidental than intentional "buildozer android update" yesterday, my app causes a runtime error. It fails to load the libpython2.7.so since it seems to refer to "pow". Please see logcat output attached. I am on OSX using python 2.7.10 and Buildozer 0.30dev, kivy 1.9, python-for-android installed from here https://github.com/kivy/python-for-android.

Any help would be appreciated.

Cheers,

Andreas

D/dalvikvm(19287): Trying to load lib /data/app-lib/com.menturagroup.saola-5/libpython2.7.so 0x41e9a9c0

E/dalvikvm(19287): dlopen("/data/app-lib/com.menturagroup.saola-5/libpython2.7.so") failed: dlopen failed: cannot locate symbol "pow" referenced by "libpython2.7.so"...

E/AndroidRuntime(19287): Process: com.menturagroup.saola:python, PID: 19287

E/AndroidRuntime(19287): java.lang.UnsatisfiedLinkError: dlopen failed: cannot locate symbol "pow" referenced by "libpython2.7.so"...

E/AndroidRuntime(19287): at org.renpy.android.PythonActivity.run(PythonActivity.java:254)

W/ActivityManager(  867):   Force finishing activity com.menturagroup.saola/org.renpy.android.PythonActivity

D/CrashAnrDetector(  867): processName: com.menturagroup.saola:python

I/ActivityManager(  867): Process com.menturagroup.saola:python (pid 19287) (adj 15) has died.(77,286)

I/WindowState(  867): WIN DEATH: Window{430c9df8 u0 com.menturagroup.saola/org.renpy.android.PythonActivity}

W/WindowManager(  867): Force-removing child win Window{42f733f0 u0 SurfaceView} from container Window{430c9df8 u0 com.menturagroup.saola/org.renpy.android.PythonActivity}

[Rahul Ghose]

I am facing the exact same issue. Is there any way to add linking lines to buildozer config?

I think this could be solved by adding the "-lm" line somewhere during build.

[Alexander Taylor]

python-for-android should already link with libm.so. Could you try targeting a newer android API, I have a vague memory this could be related.

[Sean Zhai]

Could you give some details on the solution please? 

I think that I might be seeing the same problem now on Kivy 1.9.1.

Thank you!