Error in vscode: "`gcc.exe' failed in phase `C pre-processor'. (Exit code: 1)"

[jneira]

• Opening haskell-ide-engine/install folder with the lastest hie-bios branch
• The error is shown as a editor alert at initialization and in each file saving
• hie doesnt respond at hover, etc
• hie handles the project correctly in master
• logs: https://gist.github.com/jneira/7cba45d34cb818f5c42b0a971444668f

GhcException on cradle initialisation: "`gcc.exe' failed in phase `C pre-processor'. (Exit code: 1)"

• The posible fix could involve handle that exception in runActionWithContext (thanks for point it out @mpickering)

[fendor]

To add more context to this issue and how to reproduce it:
@jneira found that it happens on our install script project when you have never built it before.

Steps to reproduce:

git clone https://github.com/mpickering/haskell-ide-engine hie
cd hie/install
code .

or, if project is already cloned

cd <path-to-haskell-ide-engine>/install
rm -rf .stack-work/ dist-newstyle/ dist/
code .

where code . is just an arbitrary lsp-client.

In the project hie-install, the cradle Cabal-Helper-v2 will be selected due to the presence of cabal.project.
Simply opening any haskell source file in the project will lead to the described error message.
Error is specifically that a cabal_macros.h can not be found, which is not generated when c-h initialises the project context.
Workaround: use stack build and cabal build respectively to generate this file.

EDIT: adding a hie.yaml works for me as expected even when the project has never been built before.

[lukel97]

My own logs that run into this

[jneira]

Thanks for summarize the bug @fendor.

[fendor]

What @bubba is observing may or may not be a different issue :(

[jneira]

adding a hie.yaml works for me as expected even when the project has never been built before.

i think it is caused by using hie.yaml's which triggers a cabal repl or stack repl and those commands generate the cabal_macros.h file. That observation could help us to fix the issue.

What @bubba is observing may or may not be a different issue :(

To check it we should execute the ghc command with the args shown in the log, after deleting dist-newstyle and call cabal v2-build --dry-run.

[jneira]

• There is an open issue in cabal about: Add feature to generate cabal_macros.h haskell/cabal#2209
• In short: it seems cabal_macros.h should be generated with cabal v2-configureor cabal v2-build --only-configure but it is not

[fendor]

Closed in favour of haskell#1519