Gautham

This is likely related to #22 -- at build time `zsh` does some extra checks to find out the signals provided by the host system, which needs to be patched...

Does it work if you use a Python executable from this release? https://github.com/ahgamut/superconfigure/releases/tag/z0.0.47 If so, it's likely related to some API difference between OpenSSL 1.1.1 and OpenSSL 3 -- we're...

I've reset to OpenSSL v1.1.1 for now, so I expect the next release to work. > I'd love to try to help, but don't even know where to start looking....

`cosmocc` generating an APE works quite well for projects that don't make too many checks about the host system: for example `lang/lua` can be built by setting `CC=cosmocc`. However, some...

The process used in this repo precedes `cosmocc`, and is also more flexible: we can handle arch-specific differences in a straightforward manner for each step of the build process.

> Is there any superconfigure subproject currently delegating all this to `cosmocc`? No, every project in this repo builds x86_64 and aarch64 separately, and combines via `apelink`. > In case...

Updated to nano-8.4 in https://github.com/ahgamut/superconfigure/commit/0c5fe461d5d1984a5a15d19840b4a8c9e737e0de You can download the testing build in the `artifact.zip` from [here](https://github.com/ahgamut/superconfigure/actions/runs/15282214857).

What `TERM` variable does `busybox-w32` use by default?

Okay @stianhoiland I patched the `nano` build to force `TERM=vt100` as a possible workaround for the issue when on Windows. Testing binaries available [here](https://github.com/ahgamut/superconfigure/actions/runs/15284770683). If your shell uses a different...

> Playing around with TERM=linux ./nano and TERM=rxvt ./nano and color works again, yay, but there is some weirdness when nano exits and tries to restore the terminal from raw...