Arguments empty when executing external processess

[nomeata]

When executing an external process, the argument actually passed to the execve sys call is "", no matter what I have in the code:

$ cat Test.hs 
import System.Process
main = rawSystem "echo" ["first_argument"]
/tmp $ ghcjs -O Test.hs 
[1 of 1] Compiling Main             ( Test.hs, Test.js_o )
Linking Test.jsexe (Main)
/tmp $ node Test.jsexe/all.js

/tmp $ 

Affects Cabal: haskell/cabal#4742 (comment)

This is ghcjs, ghc-8.0 branch, bootstrapped a week ago, and node v6.11.2.

[luite]

I saw this problem for the first time last week with a Cabal setup script.

I'm pretty sure that this used to work, but I haven't had time to investigate yet. Are you using linux?

[nomeata]

Yes, Debian unstable.

[nomeata]

As an additional data point: I have also seen it on Travis, with

• Ubuntu Trusty,
• Node 7.4
• ghcjs from http://ghcjs.luite.com/master-20160628.tar.gz

The common theme is a recent version of node? Did you yourself upgrade node last week?

[cocreature]

I have been experiencing the same problem on Archlinux with node v8.4.0 but weirdly enough only with the ghcjs that I’ve bootstrapped manually. ghcjsHEAD from nixpkgs as well as a version bootstrapped via stack from http://ghcjs.tolysz.org/ghc-8.0-2017-02-05-lts-7.19-9007019.tar.gz seem to work just fine for me on the same system. While nix ships its own version of node, stack should be using the globally installed version on my system which seems to suggest that maybe node is not the problem here.

[luite]

Okay it's more widespread than I initially thought then. I was trying to build something on a fresh macOS install with a new node.js and thought it might be just macOS.

I'll check linux with a newer node.js

[luite]

this should be fixed in ghcjs/shims@85395dc

[nomeata]

That seems to work, thanks!