Closed trev-dev closed 1 year ago
Look into osproc
and poUseShell
, it's likely that koch.nim
ends up using this somehow.
I can't seem to grep poUseShell, but there seems to be many process related functions in osproc
. My script already patches hard coded instances in osproc
, let's see what I can find.
Looks like upstream has moved on without me! Closing.
This is definitely an edge case, but I'm out of ideas and need to ask questions.
I am trying to build nim and nimble to Guix. The current package (and the one I am working on) currently can only seem to build the nim compiler.
Choosenim would be a nice option but it seems to fail at finding dependencies as well.
Like Nix, Guix builds packages in a contained environment. I have patched all of the shebangs, and swapped out hard-coded references to
/bin/sh
to the canonical path.I have tried symlinking bash to /bin/sh in the build environment, which it simply will not let me do :)
I have tried exporting my $SHELL as the canonical path to /bin/sh. the end result is the same: we compile nim, then fail to compile koch with nim:
If it's at all meaningful to whomever may view this, I can show you what the build script is doing so far:
Could anyone shed some light on which aspect of
bin/nim c koch
is trying to call /bin/sh directly?