macos release seems broken

[2mol]

Hi folks!

I was trying to troubleshoot HIE for somebody who reported issues getting it to work (for vscode) at haskell/vscode-haskell#126

Downloading the compiled release (yay for having that option now btw) will not work, seemingly some places have @bubba s path compiled in (/Users/luke/Source/haskell-ide-engine/.stack-work/install/x86_64-osx/...). See attached 4-Haskell HIE (pboy).log

I ran into some other smaller issues as well, I think polishing those up could make the installation experience accessible to a lot more people. I volunteer to work on documentation if we can agree on what to improve.

• it wasn't obvious to me how I can peek into the logs between hie and vscode. What's the recommended way? Found the logs nicely accessible in a dropdown under the output pane of vscode. Maybe we could put this in the Readme under the troubleshooting section at the bottom?
• it seems the hie executable is used instead of hie-wrapper, despite my impression that the latter would be used preferentially. On that note: Why have the hie executable there in the first place?
• I saw a complaint in the logs about hlint.yaml not being found, it's unclear if that was a warning or an error.

[alanz]

cc @bubba

[Rhywun]

I tried to install v0.4.0.1 over v0.2.2.0 using the instructions under "Installation with stack" and something broke on this recommended instruction (after using brew to upgrade stack):

stack install cabal-install

Got "ExitFailure 2" trying to install GHC 8.6.2 but no indication of where to look for a log to explain it, so I gave up. Also, I broke HIE on my machine. I may try to start from scratch but will follow along here to see if anything develops.

Update - I am trying a clean install and made it past installing cabal-install but the same failure occurred after running make build-all in the HIE source directory:

$ make build-all Downloading nightly-2018-12-01 build plan ... Downloaded nightly-2018-12-01 build plan. Preparing to install GHC to an isolated location. This will not interfere with any system-level installation. Preparing to download ghc-8.6.2 ... ghc-8.6.2: download has begun ghc-8.6.2: 12.97 MiB / 221.33 MiB ( 5.86%) downloaded... -etc.- ghc-8.6.2: 221.33 MiB / 221.33 MiB (100.00%) downloaded... Downloaded ghc-8.6.2. Unpacking GHC into /Users/me/.stack/programs/x86_64-osx/ghc-8.6.2.temp/ ... Configuring GHC ... Installing GHC ... Received ExitFailure 2 when running Raw command: /usr/bin/make install Run from: /Users/me/.stack/programs/x86_64-osx/ghc-8.6.2.temp/ghc-8.6.2/

Preparing to install GHC to an isolated location.
This will not interfere with any system-level installation.
Preparing to download ghc-8.6.2 ...
Already downloaded.
Unpacking GHC into /Users/pat/.stack/programs/x86_64-osx/ghc-8.6.2.temp/ ...
Configuring GHC ...
Installing GHC ...
Received ExitFailure 2 when running
Raw command: /usr/bin/make install
Run from: /Users/me/.stack/programs/x86_64-osx/ghc-8.6.2.temp/ghc-8.6.2/

git submodule sync
Synchronizing submodule url for 'submodules/HaRe'
Synchronizing submodule url for 'submodules/brittany'
Synchronizing submodule url for 'submodules/cabal-helper'
Synchronizing submodule url for 'submodules/ghc-mod'
git submodule update --init
stack install cabal-install
Preparing to install GHC to an isolated location.
This will not interfere with any system-level installation.
Already downloaded.
Installing GHC ...
Received ExitFailure 2 when running
Raw command: /usr/bin/make install
Run from: /Users/me/.stack/programs/x86_64-osx/ghc-8.6.2.temp/ghc-8.6.2/

make: *** [cabal] Error 1

Again I don't know where to find a log file that might explain what went wrong.

[2mol]

Hi @Rhywun! Let's split this into a separate issue since the cause will be different from the one affecting the precompiled binary release. I'll then try to redo my installation step by step and see if I can help your case!

[Rhywun]

@2mol

Done, thanks

[lukel97]

Update so far: Since the hie binary relies on the libexec and data-dir paths generated by cabal, we'll probably need an install script or something for the binaries to replace these paths. cabal-helper relies on libexec for cabal-helper-wrapper and hlint has some share files, but cabal-helper-wrapper has gone away in recent versions of cabal-helper so we might not need it.