-
Notifications
You must be signed in to change notification settings - Fork 6.8k
[v0.9.3] Amalgamation for Android broken #4783
Comments
you need to update submodules. Try a fresh clone |
I cloned fresh and retried, same error as before. @piiswrong any ideas? Is this working for you? |
USE_OPENCV was accidentally turned on in amalgamation/Makefile. Should be fixed by 01ae4df |
@piiswrong just tested, still breaking:
|
try make -DANDROID=1? @howard0su USE_SSE is not turned off properly for JS and android. Moving it to make file doesn't work |
should be fixed by #4797 |
@d4wud Hi, I met this trouble too. Do you succeed now? |
@piiswrong thanks for working on this. I'm still having the problem posted above with Any ideas? |
Try adding |
I tried adding that to the CFLAGS in Makefile with no affect. |
@piiswrong Also no affect adding it to |
Are you sure you are using a fresh clone of latest code? could you post the content of your mxnet_predict-all.cc? |
I did a fresh clone. On the most recent commit there are all kinds of new problems. When I set head to your fix #4797 I am still seeing the |
I'm out of ideas... If anyone can reproduce this please try to debug or provide more information |
You can try debugging it by removing the parts of mxnet_predict-all.cc that's causing problem. |
@d4wud I cloned the latest version, but I can't even generate mxnet_predict-all.cc now.
When I run "make ANDROID=1", I met two errors. /home/rokim/android-toolchain/bin/arm-linux-androideabi-g++ -std=c++11 -Wall -O3 -msse2 -Wno-unknown-pragmas -funroll-loops -Iinclude -fPIC -MD -MF nnvm.d \
-I `pwd`/../ -I `pwd`/../include \
-D__MIN__=0 -c nnvm.cc
arm-linux-androideabi-g++: error: unrecognized command line option '-msse2' The second:
I commented execinfo.h in /home/rokim/mxnet/dmlc-core/include/dmlc/./logging.h but the first error still exists. But I backed up the mxnet I used yesterday, on which I can still reproduce the error as yours, with the same mxnet_predict-all.cc:
|
@piiswrong this is what I'm seeing as well. Any idea how to proceed? |
Seems to be a mac specific problem. I'll look into it |
Made a fix 7c197d6 I tested it works on Mac 10.11.6 |
I did a fresh clone and make in amalgamation with Mac 10.12, and get the compile error in iOS project: I set USE_CUDA = 0 in config.mk while making mxnet. |
Could anyone attach the generated |
Hello Thread, Some things have indeed been fixed, but I'm still not able to amalgamate. New crash on 0f6d583:
I've attached my |
I found the generated I manually set
|
@d4wud Try to add DEFS in
|
I am attempting amalgamation on the most recent commit 39a2c0c and progressing beyond where I was getting before. Unfortunately I'm not getting an error message, just simply a failure after a warning:
This is on a Mac. On Linux it is breaking as well but with a different error:
@piiswrong any ideas? @PhanTask I tried your recommended changes but still no success. |
Are you using FreeBSD? Seems like a freebsd specific problem. For mac, there should have been an error before the warning |
@piiswrong no we're on Ubuntu 16.04.1 LTS. On Mac I only see warnings. I've attached the entire output of make. |
How are you compiling it? You need -std=c++11. What's your compiler version? |
As you can see here: ARM-based arm-linux-androideabi- |
@d4wud Hi, I met the same issue. You can try adding " #define _GLIBCXX_USE_C99 1 " into the generated "mxnet_predict-all.cc"(or the proper position in the "amalgamation.py") and make again. |
But I am not sure if this is the best solution, as there is no need to add such definition in the v0.8.0 setup. |
OK @leo-scorpio I'll give it a shot. Thanks! @piiswrong here is my GCC version:
|
@leo-scorpio |
@d4wud I met the same problem but I solved it by recreating NDK toolchain. You can try to recreate Standalone Toolchain with libc++ headers and libraries since the GNU STL library(libstdc++, by default) seems to not fully support c++11 features(such as function stod stoi stof to_string). |
@d4wud Adding param '--stl=libc++' when running |
@PhanTask I gave it a shot, but now something's breaking in the standalone NDK.
Any ideas what I'm doing wrong that would break something that fundamental as the link to |
@d4wud I didn't met this error. It seems that there are many possible causes, you can google it for more solutions. Or maybe you can try those(I don't know if they works):
|
@PhanTask |
@PhanTask |
@nihilityworld Try to add |
@nihilityworld Also, I didn't add libc++.so or libc++_shared.so path in LDFLAGS manually, and didn't met your error and warning when running make ANDROID=1. So it is strange that everyone seems to met different errors and have different solutions...Good luck... |
@PhanTask Can you send me your 'libmxnet_predict.so' file? My e-mail address is [email protected]. Thanks! |
@nihilityworld OK, I'm outside now, I will send it to you later. |
@nihilityworld Sent it to you already, with libc++_shared.so. Please check. |
@PhanTask I have tried the library you send to me, but it break and I get the error: I have tried mxnet/tests/python/mxnet_predict_example.py with the params and symbol file android used and can get right result. |
Hello guys, have you resolved the issues and built the android library successfully? I am still encountering the issues and post it here but seems there's no response. Really looking forwards to help. |
@PhanTask |
@PhanTask @PetroWu @piiswrong @d4wud |
I achieve to compile mxnet for android with this ugly method: #6889 |
I have achieved to compile mxnet amalgamation for android successfully, and put the steps at #7146 |
@PhanTask what your mxnet_predict.so version?
i tried so many times~ |
@novioleo hi, i met with same error with you, compied for arm64, do you have any clue for this? thanks in advance! |
@zhenglaizhang i need to add a line to "dmlc-minimum0.cc": if you encounter the similar problem in the next compile progress,you should try to add relevant .cc file to dmlc-minimum0.cc or mxnet_predict0.cc. |
@novioleo yeah, thanks for the info, i succeeded in building the jni so. |
Amalgamation for Android still breaking in the recent release:
Commenting out that
#include <execinfo.h>
creates the further error:It looks like the
USE_OPENCV = 0
is being ignored?The text was updated successfully, but these errors were encountered: