I am using GHC version 8.6.5, and cabal-install version 2.4.0.0 on Ubuntu 20.04.4 LTS.
If I simply do “cabal v2-run”, it seems to work fine:
ppelleti@midnight-star:~/prg/hs/font-convert$ cabal v2-run
Resolving dependencies...
Up to date
Usage: font-convert src dest
However, my program needs arguments to work, so I tried passing the arguments to v2-run
, after a --
. This resulted in Cabal building some sort of “fake-package-0” that it didn’t build when I wasn’t passing arguments.
ppelleti@midnight-star:~/prg/hs/font-convert$ cabal v2-run -- ~/misc/unscii/unscii-8-mcr.hex unscii-8-mcr.png
Resolving dependencies...
Build profile: -w ghc-8.6.5 -O1
In order, the following will be built (use -v for more details):
- fake-package-0 (exe:script) (configuration changed)
Configuring executable 'script' for fake-package-0..
Preprocessing executable 'script' for fake-package-0..
Building executable 'script' for fake-package-0..
[1 of 1] Compiling Main ( Main.hs, /home/ppelleti/prg/hs/font-convert/dist-newstyle/build/x86_64-linux/ghc-8.6.5/fake-package-0/x/script/build/script/script-tmp/Main.o )
^C
Unfortunately, this “Compiling Main” step never terminated. I looked at top
and GHC was using 100% of my CPU. Hitting Control-C returned me to my prompt, but did not terminate the GHC that was using 100% CPU. Using plain kill
on the GHC PID didn’t stop it either. I had to kill -9
to get rid of it.
Any idea what’s going on? I’m curious what “fake-package-0” is all about, and I’m especially curious why it sucks up all the CPU and doesn’t terminate.