Open capn-freako opened 4 years ago
When attempting the alternative Haskell Platform based installation, from either the Git MINGW64, or Cygwin, I'm getting this strange error:
Failed to install network-2.8.0.1
Build log ( C:\Users\capnf\AppData\Roaming\cabal\logs\ghc-8.6.5\network-2.8.0.1-41igyNI75uzGO9xrEXCykL.log ):
Configuring network-2.8.0.1...
cabal.exe: The package has a './configure' script. If you are on Windows, This
requires a Unix compatibility toolchain such as MinGW+MSYS or Cygwin. If you
are not on Windows, ensure that an 'sh' command is discoverable in your path.
I have the following line in my cabal
config file:
extra-prog-path: C:\Program Files\Haskell Platform\8.6.5\msys\usr\bin,
C:\Users\capnf\AppData\Roaming\cabal\bin
And there is a sh.exe
file in the C:\Program Files\Haskell Platform\8.6.5\msys\usr\bin
directory.
Hm, I'm not sure what to suggest. I've never built gitit on Windows. These are build failures for dependent libraries, not pandoc itself. Probably there's something wrong with your build setup, but since I don't develop on Windows, I couldn't tell you what.
Okay, I was able to get the Haskell Platform approach to work, by doing the following:
Change my ~\AppData\Roaming\cabal\config
file from this:
extra-prog-path: C:\HaskellPlatform\8.6.5\msys\usr\bin,
C:\Users\capnf\AppData\Roaming\cabal\bin
to this:
extra-prog-path: C:\HaskellPlatform\8.6.5\msys\usr\bin
extra-prog-path: C:\Users\capnf\AppData\Roaming\cabal\bin
I just encountered this same error after adding Windows to the CI: https://github.com/jgm/gitit/runs/4490058242?check_suite_focus=true
We now work around this by setting the portable
flag on sendfile, which may affect performance.
I'm following the suggested installation instructions, under Windows 10, by entering the following commands at a Git MINGW64 terminal prompt:
git clone https://github.com/jgm/gitit
pushd gitit
stack install
and getting this:
I tried running the
stack install
command in a Cygwin command shell, instead, and got:Attempting the
stack install
command from a Windows command prompt yields a similar result.Scanning all 3 transcripts for errors (They all produce many warnings.) yields:
MINGW64:
{Omitted 2 more like the above, from the same file.}
Cygwin:
(Contains only the last error reported above.)
CMD:
Same as above, but with additional diagnostic information:
Oh, I just noticed this, at the very start of my console output: