Julia on iOS and Android


#21

Why can’t it read missing x lib, instead of error #2? :stuck_out_tongue: It’s about to finish now!

I’ll try to run the tests individually, you mention you have added some tests, is there any other command to run those or will they run with make tests?


#22

I built yosterday succesfully and was able to use julia, then I melled up my PATH and I am starting again, because I had to reset Termux.

Installing with:

apt install julia-devprev

And then running Julia I get:

CANNOT LINK EKECUTABLE "julia": library "libopenblas.so" not found Aborted

If I do next:

apt install openblas

Then I get:

Illegal instruction

@its-pointless should I open an issue at your repo to track this?


#23

Yes its probably best handled there since its likely purely a non-julia issue since you could build it yourself and its very likely an arch specific issue with how i compiled julia. Also its probably worth pointing out that there is a failsafe method to start termux that just loads busybox so you don’t have to reinstall termux if something like that happens to a bad path etc.


#24

Thanks! Could you please enable github issues in the repo of your julia fork?

Now I am getting this error, I don’t know what am I missing, this didn’t happen yesterday, I’ll continue to try and build it deterministically.


#25

could be corrupted image?
make clean will fix?
could be if you have julia installed from my repo it messes with it since at some point its loading the wrong libraries?
what ever is occuring i will be updating the branch so it installs and adding documentation explaining how the android linker, LD_LIBRARY_PATH etc can mangle things because android linker does not behave like a normal linker does. Which requires workarounds particularly if you doing something weird like compiling julia on it…

But first i have to finish testing gcc-8 so it doesn’t break anything if you install it.


#26

okay time fill in some infomation with regards to complinig on device. Arm is the hard one so lets go through the issues.
First the ram requirements for compiling is higher than it is for running it. Android also has a habit of killing processes that use lots of cpu and slowly require more and more ram… the device i was using to compile it died and tried 3 other devices and they fail. It needs ram.

secondly last time i checked arm still required libunwind so if you are getting bus errors during compile it could be its not installed or maybe libuv needs it can’t recall.

the android linker is deliberately designed to be stupid so you have to tell it the order to search libraries via LD_LIBRARY_PATH. To use a compiled in place version you have to add the julia libs LD_LIBRARY_PATH before system LD_LIBRARY_PATH. this means you can’t use dynamically linked lib version of libuv that julia uses at the same time as the termux libuv.so since you need to have the LD_LIBRARY_PATH first pick up julia libs then termux system libs. Solution was to simply use statically linked julia libuv.


#27

juliabox.com runs on iOS, i reccomend iPhone but have used it on iPhone aswell. You can run code, install packages and it is cloud based, so all your code can be downloaded on another device.


#28

JuliaBox does not run on iOS; JuliaBox is hosted on, I’d imagine, Linux servers (or maybe a *BSD?). However, JuliaBox is accessible from iOS, since JuliaBox’s interface is through a web browser. That is a key distinction; you can’t write code that works in a cross-platform manner that works the same on iOS as it would work on a desktop system. That is to say, things like filesystem operations, device access (cameras via VideoIO, Vulkan-accelerated graphics if any exist, etc.) would not work on JuliaBox accessed from iOS, while these things would work on a regular desktop running native Julia.