Alison Winters

Your syntax error in interactive mode might be similar to the errors I experienced in trying to get various shells to run under Windows. Specifically inside Windows console when you...

It's really annoying that POSIX doesn't define a function to search `PATH`, it seems every shell just reimplements it for itself, and then libc has its own way again for...

Maybe we could "polyfill" this one for UNIX: https://docs.microsoft.com/en-us/windows/win32/api/processenv/nf-processenv-searchpatha It could perhaps be used to handle finding things in the APE's ZIP filesystem too.

Try running `wsl -l -v` and check what version your WSL install is. For some reason I haven't had time to figure out, Cosmo doesn't work on WSL1 (see #76).

Tried again with a debug version of `package.com`: ``` $ build/bootstrap/package.com -o o//libc/stubs/stubs.a.pkg o//libc/stubs/abort.o o//libc/stubs/assertfail.o o//libc/stubs/cxapurevirtual.o o//libc/stubs/debugbreak.o o//libc/stubs/gcov.o o//libc/stubs/instrumentation.o o//libc/stubs/ld.o o//libc/stubs/panic.o o//libc/stubs/retpoline.o o//libc/stubs/stackchkguard.o o//libc/stubs/stackguard.o o//libc/stubs/typeinfo.o o//libc/stubs/ubsan.o o//libc/stubs/xnu.o error:tool/build/lib/persist.c:119:package.com: check failed...

Thanks for the new `package.com`, that got the build a lot further for me. I don't have time right now to get the build fully done, but I'm happy to...

Another data point on the `gcc 9 EXITED WITH 5` error... I gave Windows-based compile a shot with LLVM as well (just needed to add `-target x86_64-pc-linux-gnu` to `TARGET_ARCH` definition),...

Okay, I have tried to create a load test which will recreate these `EXITED WITH 5` errors. I started with a tiny fake C compiler, compiled with the `csc.exe` that...

Just to log my status on this, I have been noodling around with various different things on Windows in my spare time. Obviously WSL is the easy solution, but I'd...

Unfortunately the past few months I haven't really had the time to look at this project, but I did find the LLVM approach more promising than cross9 gcc back in...