On 22/07/2016 18:28, Jafar Al-Gharaibeh wrote: > You are doing a native build, which is something I could do,
This is an example of cross-compilation instead of native build: https://github.com/marco-pratesi/android/blob/master/quagga/quagga-0.99.22.1/quagga-NOTES-0.99.22.1.txt > but it since I got binaries cross compiled that can be run on Android, > I was wondering if there is away around the run-as-user issue. Sincerely, I have not understood which toolchain you have used to build Quagga for Android. I do not know Terminal IDE very well, but, if my memory does not fail, it provides a native GCC compiler, that builds against the Bionic Libc. Did you build through Terminal IDE and the GCC bundled with it? > [...] I did try running as root (and compiled Quagga with user root > configured) but that didn't work and kept giving me the error I posted > earlier. I didn't see any of your patches changing this aspect (user) so > I'm wondering how did you get around this issue? I have never hit the error you reported; maybe you can try to cross-compile Quagga according to the notes linked above, using the Android NDK, and then check if the error occurs again. > What shell did you use? mksh and bash under the Android Terminal Emulator, but it was not relevant anyway. > and what Android version ? Android 4.x with x > 0. On Android 4.0, segmentation fault occurred, and I do not understand why... after a lot of unuseful investigation, I gave up. >> Maybe you can build (cross-compile) a glibc+gcc toolchain for Android >> (I succeeded in doing this) > > Terminal IDE comes with these so I didn't have to worry about this. I > didn't have to do a native build after all anyway. Does Terminal IDE come with a Glibc+GCC toolchain? I suppose that it is a Bionic+GCC toolchain. Marco Pratesi _______________________________________________ Quagga-dev mailing list [email protected] https://lists.quagga.net/mailman/listinfo/quagga-dev
