Michael Neumann

I license past and future contributions under the dual MIT/Apache-2.0 license, allowing licensees to chose either at their option.

When I last tried to compile Savi on FreeBSD (a week ago), I run into issues. So maybe CI is having issues as well....

Dunno if Pony uses some optimizations related to the number of scheduler threads, which is fixed to the number of CPUs. Allowing to dynamically create new scheduler threads might be...

@jemc, I was just using `-X` option. Will try with `SAVI_SYS_ROOT`. You might get away with the path patching by installing `savi` into the sysroot and using `chroot`.

It seems I missed linking in `libatomic`. The `__atomic_compare_exchange` is undefined for DragonFly's version of libsavi_runtime, where for FreeBSD's version, that symbol does not appear: ``` > llvm-nm libsavi_runtime-x86_64-unknown-dragonfly.bc |...

@jemc I got some more success by linking against libatomic on DragonFly. It has one symbol undefined: 00000000002467e0 D __progname This is required by DragonFly's libc. Any hints on that?

this seems to be a BSDism and is a non-portable alternative to argv[0]. I assume, the DragonFly compiler will add a `__progname` definition, and this is somehow missing when cross-compiling.

there is no `libcsu` on DragonFly. But `__progname` is defined in `crt1.o`: ``` > llvm-nm -U /dfly-sysroot/usr/lib/crt1.o 0000000000000000 D __progname 000000000000008c T _start 0000000000000000 r abitag 000000000000001c r crt_noinit_tag 0000000000000000...

> binary > I'm unsure about this... I haven't dealt with `chroot` much before, but wouldn't this require the `savi` binary itself to be compiled for that target system (and...

@jemc it fails locally too, not just in github actions. IIRC, I was once changing related code to limit `git clone`s to run max 2 in parallel. I guess that's...