as a temporary workaround we could create a top-level wrapper script, say `ghc-stage1.sh` that will call Stage1 GHC with the right arguments, just like Hadrian itself does during the build.

That sound fine, thanks.   Same for ghc-stage2.sh?

My difficulty is that as of today I simply do not know how to invoke my freshly built GHC!

Simon

From: Andrey Mokhov <andrey.mokhov@newcastle.ac.uk>
Sent: 15 April 2019 12:53
To: Simon Peyton Jones <simonpj@microsoft.com>
Cc: ghc-devs@haskell.org
Subject: RE: Hadrian

Hi Simon,

Apologies it’s taking so long. It’s not obvious how to fix this properly, and as a temporary workaround we could create a top-level wrapper script, say `ghc-stage1.sh` that will call Stage1 GHC with the right arguments, just like Hadrian itself does during the build.

Will this work for you?

Cheers,
Andrey

From: Simon Peyton Jones [mailto:simonpj@microsoft.com]
Sent: 15 April 2019 12:28
To: Andrey Mokhov <andrey.mokhov@newcastle.ac.uk>
Cc: ghc-devs@haskell.org
Subject: Hadrian

Andrey and other Hadrian heros

Just to say that I am 100% stalled on using Hadrian because the in-tree binary uses the wrong library files.  I reported this a few weeks ago, but it still seems unchanged

Simon

Bash$ ~/code/HEAD/_build/stage0/bin/ghc --version

The Glorious Glasgow Haskell Compilation System, version 8.9.0.20190414

simonpj@MSRC-3645512:~/tmp$ ~/code/HEAD/_build/stage0/bin/ghc -c T16566.hs

T16566.hs:1:8: error:

    Bad interface file: /opt/ghc/8.6.4/lib/ghc-8.6.4/base-4.12.0.0/Prelude.hi

        mismatched interface file versions (wanted "809020190414", got "8064")

  |

1 | module T16566 where

  |        ^^^^^^