emscripten & android ndk on NetBSD

[r0ller <r0ller%freemail.hu@localhost>]

Hi All,

This is my first mail to this list and hopefully I found the right user group with my topics -let me know if not.

1) The first topic would be asking for a kind of review (if anyone is interested) of what I posted about building emscripten on NetBSD in the google group of emscripten:

https://groups.google.com/d/msg/emscripten-discuss/2z1NZrX3sA8/jNy4ACiIBwAJ

Actually, they offered their support for NetBSD in the buildscript once I sort out a few problems/questions they listed in their answer:

https://groups.google.com/d/msg/emscripten-discuss/2z1NZrX3sA8/9sYySK32BgAJ

However, as I'm not a NetBSD expert, I thought I'd first let my changes in the buildscript checked by someone more knowledgeable. So that'd be one task while the next task would be to discuss their questions like the one concerning vanilla llvm build. Just as a side note, till now my emscripten build works fine without any hickups. Unfortunately, I haven't had the time since my post to try if a vanilla llvm would pose any problems on NetBSD or why building nodejs failed back then.

2) I also tried building android ndk but the python buildscript failed and I have currently no time for getting really into it so I just tried the linux installation making use of the NetBSD linux compatibility layer. The only thing I had to change was the check for the host so that in case of NetBSD, the script evaluates it to "linux":) I almost managed to build my project that way but in the end when the linker tries to write the shared library object I'm building, it fails with the error message "function not implemented". I made a ktrace and kdump showed that the reason was "unimplemented fallocate" for the linux syscall. Is it planned to have that implemented? Anyway, just for the record: for the time being I created a named pipe with the name of the targeted shared library and when the build hangs waiting for someone to read the pipe, I just cat the named pipe into a file in another terminal:) It seemed to spit out the .so that way and the file command recognizes it as an ARM shared library but I haven't tried it out yet if it really works on the phone. I'll let you know later:)

Thanks for any help in advance!

Best regards,
r0ller