tobil4sk

I've tested with some older ndks (in particular, I was successful with r15 and r17). I had to make some modifications to hxcpp, but I was able to get them...

> But what actually happened is we forgot about it, and no one seems to have complained. Note, this was on the 8.3.0 branch until now, which might mean fewer...

This patch seems to avoid the error, but I'm not sure if it's correct: ```diff diff --git a/src/jit.c b/src/jit.c index 7571090..b971f85 100644 --- a/src/jit.c +++ b/src/jit.c @@ -1238,7 +1238,7 @@...

Perhaps a better patch would be: ```diff diff --git a/src/jit.c b/src/jit.c index 535ab69..c55c749 100644 --- a/src/jit.c +++ b/src/jit.c @@ -3760,6 +3760,11 @@ int hl_jit_function( jit_ctx *ctx, hl_module *m, hl_function *f...

The hl-legacy32 flag is now [respected again](https://github.com/HaxeFoundation/haxe/pull/11903), and this is tested thanks to #783

> I was able to add a workaround by declaring the char[] as an abstract [cpp.ConstCharStar](https://api.haxe.org/cpp/ConstCharStar.html) exists for this type of thing, and it is an abstract with the toString...

Reverted so this doesn't change the default value of `RELOCATABLE`, since that will have implications on `nekotools boot`. Also cleaned up the RPATH usage, so that during building there is...

> Do the tests still pass if RELOCATABLE is set to OFF? Yes, I ran the tests locally with `RELOCATABLE=OFF` without issues. During testing, with `RELOCATABLE=OFF` the build rpath is...

Yes, that's correct: x86-64

I was previously debugging by adding printf statements, however, I have now run a proper debugger on the program and removed the print statements to avoid their potential side effects....