jasonKercher

Can confirm for Linux

> Is there a particular reason as to why the `execve` syscall is not used on arm64? It does exist and run completely fine on my Pinebook Pro. I considered...

@flysand7 Thanks dude. I just copied the stat structure out of `core/os/os_linux.odin`. So this change should probably be back-ported. Looks like I jumped

Haha. I fat fingered the close button while typing in that reply. Looks like I jumped the gun not making CI pass first anyway. > I'm currently working on binding...

Please don't merge yet. I want to go the buildah/podman route and get everything working across architectures. Should I just close?

> Any updates? =] I don't have as much free time as you it would seem (full-time job + 4 kids). Note how the first commit on this was in...

@flysand7 Will do! I just changed some things in sys/linux. I wanted to ask you about your `Sig_Set` definition. I thought `sigset_t` was a `u64` as it's just a bit...

Should be good to go. This passes [these tests](https://github.com/jasonKercher/os2test) on amd64 and arm64 with the aid of Puklaj's fork fix (#3476 ). I made a [local CI-like runner bash script...

If that is a libc function, you can foreign link to it. Otherwise, if you just need access to the environment, this will get it for you: ```odin #no_bounds_check env:...

Just to be clear, this method will not see modifications to the environment if done via libc. I believe `setenv`/`putenv` (whatever its called) will copy the entire thing to a...